Shut down stuck
Hello, recently moved from AtlasOS to Bazzite.
Have been getting the issue of not being able to shutdown my pc, When doing shutdown (either by command "Sudo shutdown" or "sudo poweroff") or using the option on the taskbar, It gets stuck on a black screen with the Motherboard and bazzite logo and the throbber, pressing esc I get the logs seens on the images.
I suspect it has something to do with harddrives, maybe or I did something wrong installing bazzite. Any help is appreciated.
33 Replies
Hello and I am sorry you are having issues. Did you perform a clean install on your drive? Have you performed all of the OS updates? It looks like disabling FAST START could be a solution.
https://docs.bazzite.gg/General/issues_and_resolutions/
Issues & Resolutions - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
Hi, thanks for the assist.
It could be that, when I first installed bazzite I unplugged all sata hard drives (just incase I would wipe data accidentally)
Back then the PC would shut down fine, I now have all hard drives plugged in and formated them from NFTS to BTRFS.
So could be one of them still having that fast start. is there a way from the logs to check which hard drive it is? I got a 2n1 tablet running windows. I could plug the harddrive to it to remove that or better yet if it can be removed from Bazzite itself
Are you dual booting with Windows? I may have made an assumption here.
nope, only bazzite
Nvidia card?
yes, a Zotac 3090
I originally installed a Zotac 1070Ti, yesterday changed it to 3090 so the issue was there with both
I found this thread that talks about an issue with X11 and Nvidia cards. Sounds like a few people agree that this combo can cause issues. https://universal-blue.discourse.group/t/issues-with-pc-shutting-down/2214/7
Universal Blue
Issues with PC shutting down
Hello, The issue seems to be related to X11, so I downgraded " And I have no issue at all now, beside the update notification for plasma updates 🙂 More info about the bug : https://bugs.kde.org/show_bug.cgi?id=488187#c7 Edit : Actually I just need to downgrade to 6.0.5
Not trying to be that guy, but I just mentioned in another thread that switching to AMD solved a lot of Linux issues for me. I have been on Nvidia forever, but Linux, SteamOS, Bazzite and distro hoping made me settle on a RX 9060 XT 16GB and my other HTPC has a RX 6600 now.
Maybe try the open source nVidia drivers?
I think you on the money with something weird happening with the drives. See the "Failed unmounting sysroot.mount" in your screenshot. I don't think this is nvidia related, since Bazzite doesn't ship with X11 anymore plus that's the thread from a reported issue 1 year ago.
Try disconnect all the other drives again (if you manually added them in the fstab file comment them out first before doing this) and see if you have the shutdown problem or not, then connect them again one as a time and see if one of them is causing the issue.
sorry, have been busy to do troubleshooting but will try today to unplug all SATA drives and see if the problem continues, then pulg one by one to see which one is the problem...hopefully it is a sata disk and not the ones screwed to the mobo
BTW what is that " fstab file comment them out" thing?
Sorry, I am very noob. I did mounted them but I used GPT to do so
the /etc/fstab file. it has entries for storage device mount points. Might be worth running
cat /etc/fstab in the terminal and seeing what's in it. A misconfiguration in there can also cause boot and shutdown issuesMaster@bazzite:~$ cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Mon Jun 2 05:59:56 2025
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
# Updated by bootc-fstab-edit.service
UUID=e255134b-674f-4471-ba3d-405ff0c979bd / btrfs subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,ro 0 0
UUID=e7c3a160-c2a5-47e5-a8e6-5332421239c5 /boot ext4 defaults 1 2
UUID=CDAA-3EBE /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=e255134b-674f-4471-ba3d-405ff0c979bd /home btrfs subvol=home,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
UUID=e255134b-674f-4471-ba3d-405ff0c979bd /var btrfs subvol=var,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2 0 0
UUID=dedfde92-b612-4fa7-aadb-8d426bac9261 /mnt/SSDSATA btrfs defaults,compress=zstd 0 0comment out this line "UUID=dedfde92-b612-4fa7-aadb-8d426bac9261 /mnt/SSDSATA btrfs defaults,compress=zstd 0 0" then run
systemctl daemon-reload and mount -a if you see no error messages everything should be fine
Then do your disconnect experimentsorry again but how do I comment out the line in the terminal?
run
kate /etc/fstab (assuming that you on KDE), then you don't have to edit it in the terminal. When you save it will ask for your bazzite passwordah thanks, on it
Master@bazzite:~$ kate /etc/fstab
Master@bazzite:~$ systemctl daemon-reload
Master@bazzite:~$ mount -a
mount: /var/mnt/SSDSATA: must be superuser to use mount.
dmesg(1) may have more information after failed mount system call.sounds like that line is not commented out, did you add a "#" before the line?
no, used //
trying with # instead
// is what I used on windows
OK, no error after mount -a now
sweet. shutdown and disconnect the other drives and lets see if thats the issue
you might find that this mount point is what was actually causing the issue though
Nope, still getting the same message, all Sata disks are unplugged
The only 2 harddrive that are present are the 2 nvme ssd
May I f up somewhere installing bazzite?
unsure what to try next
Does bazzite has a "reinstall" option or is all wipe all and try again the only option?
Yeah there isn't a "return to factory settings" option unfortunately. So if you want a clean install it's a re-install
Just adding that after the most recent update I’m also experiencing this issue with only bazzite installed and an AMD 7800xt
I haven't find a fix yet, ended up just never shutting down the pc. Even with commands it still gets stuck. So I use sleep mode and put a jacket on it so the ram lights don't bother me at night.
I see the same thing happening since like two/three days ago.
Happens both on my desktop (full AMD system) and my deck. Both run the bazzite-gnome variant, but obviously the deck runs the -deck version of it.
Seems to happen only after updating, at least that is my suspicion.
Will see if I can get some more info on what is happening.
(Not sure if it is the same issue as OP, but the title fits.)
same issue here, it started randomly on a previously working installation. black mobo screen and then stops
Don't know if this will help others, but recently I've started closing all applications manually before shutting down and this has resolved the issue for me. It's annoying, but an effective workaround until there's a fix out. Making sure things like firefox, steam, and discord are all completely closed has been working for me the past few days
tried it and didnt work on my case, altho notices when turning on the pc I got the option to boot up from ostree 0 and ostree 1, not sure what that is or if it matter. it only lasts for about 2 seconds didnt had time to photo it.
issue still persists, would be great to have some info on whats (not) happening and why. really annoying bug
issue persists for me as well, experienced it on two fresh installs. one system NVIDIA and one entirely AMD. created a github issue here https://github.com/ublue-os/bazzite/issues/2940
dont really know what to try
GitHub
Desktop occasionally gets stuck on motherboard splash screen during...
Describe the bug Every so often when shutting down my Bazzite desktop setup the splash screen for my motherboard with the Bazzite logo at the bottom will appear and the shutdown process will appear...
Any progress? I have the same issue and it's driving me insane. On top of that, suspend does not work. If I try to suspend my system it will just instantly wake back up.