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…
Hey, thanks! That’s way easier than what I was doing. I don’t know why didn’t I think of that.
So I have to ask how long does everyone wait on that black screen? I wait under a minute, and then the next screen comes up. There is an option in terminal with ujust to configure grub visibility: ujust configure-grub ACTION=“ ” ….have not really messed with that. I thought an update in the last month or two set the default for grub to hidden. This does not bother me, but I can see how some folks would not like seeing a black screen for a length of time before getting to luks, login screen, and not seeing the grub menu at all without knowing what is going on.
Oh, no, it’s not a matter of waiting. I get stuck on the black acreen and nothing happens no matter how long I wait. That’s why I resort to workarounds or rebasing to an older image.
Like @ddawdler said, the issue was being stuck with black screen indefinitely, you can only switch to TTY through ctrl+alt+F* key.
On my laptop the issue disappeared with the update one or two weeks ago. Until then I had to boot into an older image.
After starting tty, what do I do?
sudo systemctl restart sddm
?
This brings me back to the previous state.
When I manually try to start plasmashell from tty
I get
Could not load the Qt platform plugin “xcb” in “” even though it was found
Is this related?
Lately I’ve been using sudo service sddm restart but that causes a warning that another user is logged in when shutting down.
The fastest and simplest solution, apart from rebasing to an older image, is entering tty2 via pressing ctrl+alt+f2, logging in and running startplasma-wayland
Unfortunately, even on latest stable the issue persists with my hardware.
The weird thing is that when I updated to the latest stable release and rebooted everything worked fine but every boot since then has the same issue. I’m puzzled.
Interesting connection here: SDDM not starting if usb mouse connected
See a workaround I tried here: SDDM not starting if usb mouse connected - #4 by migs0229
My issue was resolved yesterday. I think I received a firmware update.
I’m not a 100% sure it was that but the issue is gone for me.
I’ll mark this as solved, so people can open new issues or follow other sources if they still have a problem.
Well, on my next boot the issue is back. I’m lost… I can’t reliably diagnose this thing.
I’m 99% sure it has something to do with my peripheral devices and my successful boot was due to moving / removing some external device.
I’ll do some more testing and I’ll update this post if any reliable information comes up.