Ever since the latest update, whenever I boot my computer, after the splash screen, the screen goes black. My only solution so far is to enter tty2 (ctrl+alt+f2) and reboot from there. Then I choose the second snapshot from the bootloader.
I tried resetting my layers, even though I haven’t made any and I tried ujust update through tty on the newest snapshot. No luck so far.
I’m using Bazzite in desktop mode with KDE. Any ideas?
This is currently a known issue. For some reason SDDM is trying to start too fast and the gpu is still occupied.
There is a temporary fix being worked on for it.
Ah, good to know it’s already in the works. Thank you for letting me know!
Thank god I’ve found this thread. I’ve been trying to update Bazzite for hours, I thought I was doing something wrong.
Just curious how do you know this is being worked on? Where is this info shared? I’d like to keep an eye on it to know if it’s safe to update.
In the meantime I’m trying to prevent auto updates but I can’t find a way. Any tips? Thank you.
We saw this issue when testing Aurora F43 betas and made a bug report for Fedora
But I think Kyle made a temp fix for it in Bazzite (propably not in stable yet)
When this issue was known before, why wasn’t stable held at F42 until the workaround is made? Just wondering about the release process.
Its really hardware specific it seems
My FW Laptop 13 (AMD 7040) is hit by this, but my Framework Desktop (also AMD but different chipset) is not.
I was wondering this too, especially since automatic updates are the default, and with the goal of being “zero maintenance” for users.
Realistically though, this is Fedora under the hood, and there may be some issues when major upgrades happen. Some Fedora users wait a few weeks before upgrading (as does Bluefin/Aurora). The big advantage of Universal Blue is the rollback feature, so if something goes wrong, you can just pick the previous deployment from the grub menu, and that makes recovery easier.
Also, in this case, a fix was submitted in pretty short time!
Experiencing this issue myself. Another quick “fix” is to simply tty2 and then restart the sddm service manually…