@Kyle Gospo i see you built main:40 I'm building hwe:40 now
@Kyle Gospo i see you built main:40
I'm building hwe:40 now
I'm building hwe:40 now
B@j0rge i can rebuild bluefin's latests if you want after hwe is ready
Kwas running tests
Kchanges look good to me in a vm
Kso, all clear to rebuild the world
Bawesome news
Bhwe is green
Bi'm rebuilding bluefin/aurora latest
Bwe should probably consider rebuilding stable also, as I think it is also has the bad version of
rpm-ostree (stable==40, GTS==39)Bi've confirmed that bluefin/arurora stable do need the rebuild, so kicking that off
Ris this a downgrade or a commit on top of 2024.7?
Kon top
Kcan't downgrade
Rah sweet
J@bsherman do I need to rebuild gts?
Jassuming yes since the last build was the cronned one
Jthe fix in main appears to be 40 only though, I can't see anything in the upstream issue that says 39 is affected
BNot for rpm-ostree since it is 39
ZHi, is anyone else experiencing this issue? Requires an Xbox One controller over bluetooth. I experienced this on Aurora, but if the udev rules apply to Bazzite it might be an issue there as well.
https://github.com/ublue-os/config/issues/318
https://github.com/ublue-os/config/issues/318
GitHub
I recently ran into an issue using my Xbox One Wireless Controller on Aurora over Bluetooth, where no input would be passed to games after being connected. I can confirm this on both my laptop and ...
ZOops see conversation in #bazzite-dev, my bad
HNot finding this issue online, but upon booting into steam gaming mode on ROG Ally I’m stuck at “Logging in” indefinitely. Multiple reboots and shutdowns. Was working flawlessly the two days before this issue. Changed Wi-Fi connections but still won’t launch into SteamOS.
Next idea is to just reinstall Bazzite and start fresh.
Next idea is to just reinstall Bazzite and start fresh.
Ai would guess this is related https://discord.com/channels/1072614816579063828/1074438180847239279/1278747877295919186
ZDid you try disabling wifi temporarily?
ZSeems steam is down
MIt should be back
HAhhh yes reading helps
…….thank y’all!
…….thank y’all!J
Kkernels are signed with both keys
Kand the user can't seem to enroll the key with the ujust
Kunless you get another report I see no reason this isn't some kind of user error
Iis this the same user that I assistet yesterday? Because it is the exact same error message
Inope it can not be. the user yesterday was running bazzite
Kand different
Kerror: ../../grub-core/kern/efi/sb.c:182:bad shim signature.Kthis is actually a secure boot key problem
K@j0rge my guess, you were on stock kernel on gts
Khe's been using secure boot which would load minus akmods
Kjust rebased to an image with fsync
Kand is now, for the first time, dealing with enrolling our key
Kin a required manner
Jhmmm, I wonder if we could do "check to see if key is enrolled, if not, don't let them rebase" in rebase-helper?
Aif you sign grub he will be thrown to the mok manager
MThat could be added
KIs it possible, to set ptyxis icon to a generic name like console/terminal, without specifying a .svg?
Kso that your icon theme automatically applies an icon of it's theme?
KImanaged to do this for Flatpaks before ^^
NGood people, I was fiddling with what I shouldn't have, and in my user I removed myself as administrator and set myself up as a normal user, now even to return from the desktop to gaming it asks me for the root password, and at no time have I set a password to root, I have the passwd password but that is not it, a little help please, is there a default password or something like that for root? What can I do
Hno, we do not use default passwords. but you can fix it in emergency mode most likely
HUniversal Blue
Fedora already has a built-in mechanism (provided by systemd) for booting into rescue and emergency modes. However, those documents have limitations as by default, Fedora (and thus Universal Blue systems), do not set a root password during install. Thus, when the emergency or rescue mode is reached, the user is shown the error: Cannot open acc...
NThanks uff very complicated for me 
,if I format from 0, everything will be solved, right?
,if I format from 0, everything will be solved, right?HYou literally add
single to the boot arg in grub and fix it with usermod and reboot?