After updating bazzite, I am hit with a black screen on desktop mode
Hi, I'm running KDE on a desktop with an RX580 and an 5700x. After I applied bazzite updates last night I no longer can switch to desktop mode. It results in a black screen and asks me for my username and password upon hitting ctrl+alt+F2.
Please advise on if this is repairable, thank you!
Solution:Jump to solution
For my instance, the correct resolution was to reimage the OS and build up from scratch. Closing thread. Thank you all for the support @Sean.exe @RecursiveFault@DD (ping when you reply) !
43 Replies
same here rn :/
I selected the previous version on GRUB (ostree:1) and it works, so I advise you to do the same for now...
I don't even know if I should try updating again
i just tried out bazzite-gnome-stable (no game mode) in virtualbox, and i am similarly greeted by a black screen with a singular flashing _ when trying to boot into the desktop mode
I went through all 4 options in the grub order, and none of them allowed me to switch to desktop mode. I think at this point I need to salvage what days I have and Reinstall.
no need to!
you can always use bazzite rollback helper
please don't tell me you went through reinstalling everything...
not yet
I won't have time to work on my computer for another 7-8 hours at least. I didn't know about rollback helper. I am very new to bazzite and fedora
I'll give that a shot later
I'm also having this issue with the latest update. Booting the previous version from grub still works fine, but the latest stable version goes to a black screen after the login screen. Only the cursor is visible and it doesn't move. The splash screen didn't load either. Mine is the desktop only image with an Intel chip and an Nvidia 4070 Super, so this may not be a specific hardware issue.
I ran ujust update and tried again, but the issue persisted. I'm going to sleep for now, but I hope this gets resolved soon.
I probably won't be able to help (not smart enough)
but
ujust log-last-boot would be helpful nonetherless
*Something like that (forgot the exact command)I'm attempting to use Bazzite-rollback-helper right now and am attempting to install 41.20250227 instead of 41.20250227.1
Just pin the last working deploment
I think my last boot was also into this version, but I can recreate the issue and then run the command.
Did not work.
Could you elaborate?
Sorry, I'm new to Linux.
Hmm,
rpm-ostree status --verbose
sudo ostree admin pin (the index)
pin 1 thenNow pinned
Stay on the old version until someone smarter is able to help
Sorry!
(the log will still help tho)
That's pretty much what I'm doing.
It looks like his rollback did work though. His version zero is older than his version one.
So stay on the version I just rolled back to until someone comes in here and checks the logs?
OH WAIT
SORRY
then just use the old/current version
If your rollback worked
Just remember to rebase to a newer version when the issue is fixed
But I rolled back and I still cannot get into desktop mode, this is the same issue.
I think I might roll back once more?
huh, what's the last version that worked for you
Sometime in early February is when I built this, so I'm assuming a build around that time
I'll roll back to Feb 1st and see if that fixes it for now
My pinned version that's working is 41.20250216.1, from the 17th.
41.20250201 still not working...
Again, desktop mode doesn't boot but gaming mode does.
At this point I'm tempted to reinstall, but I sorta want to try a bit more in the future.
reinstalling probably won't help
🤷♂️ It's not as likely to help as it is on some other operating systems, but it's not impossible that it would. As an atomic system Bazzite's boot images are very consistent, but I don't know enough about it to say that this couldn't be an issue with a corrupted file the fresh install would overwrite.
The fact that going back to an older version didn't fix this for you but it did for me makes me think our issues are actually different. If that old version you rolled back to used to work but no longer does than that lends to the idea it might be something corrupted or something outside the versioned boot image that's causing the problem. I'm not an expert, though. That's just the speculation of an off-duty IT guy well outside his wheelhouse.
As a former field service engineer, I never dabbled in the software itself sadly so I'm just here to tinker with Linux for fun. I enjoy hardware a lot more lol.
I think I need to make a backup of two things I customized and then I'm going to likely reimage tomorrow
I am going to roll back to January 20th for shits and giggles.
As I have little background in Linux, is there an equivalent for Bazzite to run a command like DISM or SFC scannow as seen on windows?
WTF. I just went and tried to recreate the issue so I could grab the log and this time it just worked. I'm in the desktop environment on 41.20250227.1. I tried it three times yesterday and it froze on a black screen each time, but this time it booted. Did they patch it? Now I'm second guessing if I was having that issue on 41.20250227. This better not be an inconsistent issue. Those are awful to troubleshoot.
Reboot again, it resulted in the issue occurring again after I rebooted a second time
Sure. I haven't had time to get into anything yet anyway.
It worked again. Boots stupid fast too.
Wtf
Let me force the newest update again.
Happy to hear someone has gotten out of this mess
Yeah, I'm glad it's working. I still don't really trust it to be stable, though. I don't know what changed. The fact the date is the 27th and that matches the version number means they did release a same day patch. I don't remember if I was having that issue in the prepatched version or not. For now, I'll keep that pin I made of the previous version in case this does turn out to be some inconsistent issue. Good luck @Rat. I'll keep watching this thread either way. I'm invested now, lol.
I just forced 27.1 once again... Let me see if that worked
Nope
Yeah, our problems are probably different. In both cases I suspect it's an issue with KDE starting up, though. If a fresh install doesn't work, you might try the gnome image, just in case.
Sadge
Yeah that might work
If it doesn't, it would at least rule out a KDE issue.
I'm reinstalling the same version, see if that'll help. If not I'm switching to gnome I guess
Reinstalling so far has resulted in it working correctly after 2 reboots. I need to attempt to apply updates and will check in later
Solution
For my instance, the correct resolution was to reimage the OS and build up from scratch. Closing thread. Thank you all for the support @Sean.exe @RecursiveFault@DD (ping when you reply) !
I hope I don’t have to reinstall the OS as well… :(
@δDD Did rolling back to an older version work for you?
yes
Than reinstalling probably won't help.
It still might though. For now I would just pin your working version and see if the next update fixes the problem. If not, open a new ticket and give the number of your working version as part of the context. That should help them narrow down the problem.
@δDD ⬆️
thank you
will do when possible