Bazzite boots to desktop, flickers a few times, then black screens with usable cursor
Bazzite 42 ostree 0 has this issue after I removed a second monitor from my setup, going down to a single monitor
Running bazzite KDE no gaming mode Nvidia
2080 super gpu
Ryzen 5 5600
Rog strix b450-f gaming II
When I boot the login screen works fine but when I try to log in the desktop shows as normal with the audio symbol on task bar crossed out as if audio device unavailable and the task bar is unable to be interacted with. The desktop flickers black a few times before finally goes fully black with only cursor on screen able to be moved. Attempting to alt tab gives the message "no active windows" cannot use the windows key to pull up task bar. Ostree1 works fine but does not have software discovery for some reason, so no software updates (also I would prefer to not have to quickly change which ostree I'm booting too every boot)
It is not a display port issue as my Windows copy works fine, it's not a cable issue as I tried switching cables, integrated graphics is off. Attempting to boot into rescue mode instead boots to emergency mode with all checks passing except for sysroot " [FAILED] Failed to mount sysroot.mount - /sysroot. "
Solution:Jump to solution
Symptoms (part one) :
computer booted into emergency mode every boot
Solution :...
85 Replies
I would prefer to not have to completely reinstall everything so if there is a way to repair my image or make ostree1 my main image and fix software discovery not showing up that would be ideal
Correction, now both ostrees boot to emergency mode immediately -_-
The weird behavior after login I don't have much insight into.
But, from what you've provided around booting it sounds like it might be related to this. https://discord.com/channels/1072614816579063828/1392630488241410191
It could be something else, but I also had that
Failed to mount sysroot.mount and was able to get booted after following the summary laid out by IrkedQuirk. Seems it's a bug that is happening w/ the kernel and btrfs or something. If what IrkedQuirk laid out matches your issue , you likely should follow the summary he laid out here https://discord.com/channels/1072614816579063828/1392630488241410191/1392682408544829470, or https://discord.com/channels/1072614816579063828/1087140957096517672/1393371220958904521 here.
Also, when you get back up and running Discovery has been replaced. Bazaar is the new flatpak store. Bazaar has been built from the ground up as a flatpak only store, meaning it matches Bazzites needs to a tee. Plus it performs better than Discovery.
https://universal-blue.discourse.group/t/bazzite-july-2025-update-bazaar-z13-kernel-6-15-steam-hardware-survey/9501#p-25920-bazaar-3
This announcement goes into detail about Bazaar.Thank you, going to try that in the morning.
👍 Best of luck. Keep in mind if you use secureboot you may or may not need to disable to get into gparted live also be sure to update if you get going again. Supposedly there are some fixes that have been on stable for a few days now I think.
Tried this and it no longer boots into emergency mode but now is back to booting to black screen a few seconds later
You are able to log in now? So you log in then it flashes a bit and then blank screen?
Correct
hmmmm
I'm uploading an example video from post to boot
(ignore zoomzike in the background, my s/o was watching that to sleep and I can't mute audio from my gallery. And no I didn't dox myself, that's not my real last name)
It's at least an improvement from forced emergency mode
Definitely looks like plasma is crashing, I assume you can either open a terminal, or get to a tty. If you have a hotkey for a terminal try opening it, I'm probably wrong but i think the default is ctrl+alt+t
Ok I managed to get open the terminal
Were you messing around with the Wallpaper Engine plugin right before this started by chance? That would be the easiest solution :OMEGALUL:
ujust logs-this-boot will spit out the logs for the current bootI was not unfortunately. I don't use wallpaper engine anymore and have never had it on my Linux copy
What am I looking for in the logs? Do you want me to like copy paste them here?
Oh there's a big block of red for acpi error
Would that be it?
Hmm hard to say, probably anything related to plasmashell. Maybe we can find what we want with
journalctl -b0 | grep plasmashellI see three messages that might help, gimme a sec to write them out
One for
Entry is not valid "applications:org.kde.discover.desktop" 0x55768ec8b7a0
Another for
Process 2513 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Another for
segfault at 555900000079 ip 00007f34777a2f14 sp 00007fff81db8bd0 error 4 in 153eda6700b74551cfb7431d830610cc36df7f4f74188e4482775e90bc5d3.file[196f14,7f347760c000+4aa00] likely on CPU 8 (core 2, socket 0)
I'm sorry I shouldn't have let you type all that out lmao. Do you have the flatpak discord?
All good lol, I do yes but not sure how to get to it from terminal
flatpak run com.discordapp.Discorday, there we are
:Yippee_Shake:
The entry around the plasmashell termination is interesting.
But the context is what we want.
lets see
ok, want me to copy paste a full run cycle? because it looks like most of these are repeat attempts before crashing
you can, just wrap it with three ` to do a code block to make it easy to read.
kk
thats the first one
gimme a sec to find one that has the CPU message
because not all of them have it
it was the next one down lol
(side note thank you so much for helping me through this)
yeah thats the plasmashell trying to restart
Would you want to try updating? I doubt it will fix what is happening, but I can tell from the
applications:org.kde.discover.desktop that you are still on an old build.sure
ujust updaterunning, give me a sec
Is that what I should be using to update? Because up until now I was running system topgrade because I thought that was the system updater ^^'
I think that works no problem, ujust update is just a script made by the devs to call topgrade. So you are likely doing the same thing.
ah ok
ok to double check and make absolute sure I'm running this right, once this finishes I type R to reboot?
Yep!
Yeah plasma still crashes
Alright, what does
systemctl status --user plasma.plasmashell.service say? It should say whether the service is running or not, then it should have some relevant logs toward the bottom.
thats all it says
Hmm. I'm curious if its a local config that is messed up.
error 4 in 153eda6700b745551cfb7431d830610cc36df7f4f74188e4482775e90bc5d3.file[196f14,7f347760c000+4aa000] Sounds like it might be related to a config or file its calling.
let me try something out, I wonder if we make a new user if it will not crash.alrighty
alright, if you want to indulge me, you can try setting up a new user.
useradd testuser
sudo passwd testuser
enter a password for the user
systemctl logout, and testuser should be there for you to login.
Once you login, you can use systemctl logout to get out of the testuser
I'm just curious if the problem is in /var/home/ or if it is beyond that. Because that might be the end of my ideas.Does not crash on the other user
:Yippee_Shake:
ok so it is in /var/home
now we just have to locate it
the hard part
haha
Is it possible to like
Reset plasma to "factory" settings?
I'm no expert but I think the way to do that is the delete the plasma configs on the effected user so that plasma regenerates the configs on login. But I want to do a little sanity checking before I have you backing up and removing files.
kk
thank you so much
Ok, there are a couple default files that live in ~/.config/kdedefaults so I think first thing I would try is to overwrite the kdeglobals file.
sudo cp /var/home/testuser/.config/kdedefaults/kdeglobals /var/home/*youruser*/.config
Make sure you triple check that before you run it since its run as sudo.what would I be looking at to check it?
like is there a way to backup before I do that?
oh you mean my username lol
yep, plus typos
if you want to backup your original kdeglobals file then use
sudo cp /var/home/*youruser*/.config/kdeglobals /var/home/*youruser*/.config/kdeglobals.backupok, done
is there a keybind to refresh the desktop, like how windows has?
to see if itll start now
are you on youruser or the testuser?
mine
systemctl restart --user plasma.plasmashell.service:huh:
my reaction exactly lol
i miiiight need to end up making a new admin user and ditching this one lol
that might be the easiest answer
It might.
curious, if you use
start instead of restart if that makes a diff. I don't think it will but idk might be worth a shotsame message but with start instead of restart
:wah:
Yeah i think making a new user would be the easiest solution now. You can copy over the majority of the data from the current user to the new user. Just have to careful around ~/.config and ~/.local the problem file is no doubt in one of those folders.
kk
going to work on that now
:GlorpSalut:
Ayo same
I have given up though and just going to install from scratch 😔
ARE YOU SERIOUS RIGHT NOW??? I MADE A NEW USER WITH MY DESIRED NAME AND THEN JUST ON A WHIM DECIDED TO RELOG INTO MY ORIGINAL USER AND IT WORKS NOW VJJSHCJ
Ok so I can only assume that replacing the defaults fixed it but for some reason restarting via terminal doesn't work
lfmao
I would not entirely trust that, I had a similar thing and it then broke next restart
Or if the monitor turned off and then on
fascinating
I'm going to delete the new user and try restarting to see if it still breaks
If not then I'm going to consider my issue solved and write the summary
Ok yeah it still works
I just read all of that, your fix was to reset Plasma defaults? I'm running into this now after the debacle with Emergency Mode...
essentially, yeah
:dispair:
Some borked update that was huh
Yeah...
Solution
Symptoms (part one) :
computer booted into emergency mode every boot
Solution :
followed instructions in https://discord.com/channels/1072614816579063828/1392630488241410191/1392682408544829470
Symptoms (part two) :
Computer booted to desktop only for Desktop to blackscreen with usable cursor, (Plasma crashing)
Issue was user specific and was not present on making a new user
Solution :
Replace plasma config file to defaults by running
after a restart, plasma runs as normal. recommend running system update afterwards to update to newest bazzite version
huh.. did not work for me :(
maybe edit the cp command, so that
testuser is *youruser* since the kdedefaults dir exists on the original user. We only made a new user to confirm it was a config in /var/homestill getting a plasma crash
Right thank you
also I guess we can drop the
sudo since we don't need escalation because we are entirely within one usereverything in my
kdedefaults just reverts after a reboot and i still get a crashare you replacing the files in kdedefaults? I would imagine that is expected behavior, since those are the default settings. So it overwrites them on a relog. You want to do the reverse you want the kdedefaults file to overwrite the one in ~/.config
except they aren't KDE's defaults, it's my global theme i selected in Plasma Settings ages ago
i'm not sure what to replace them with, exactly
yours isn't
?
it is not
it says Ant-Dark in multiple places
Maybe that is a kvantum problem? I'm not sure why it is overwriting those files with what you have set
i deleted all of those files and those with matching names in .config, KDE is now fully reverted
but after a reboot, at least not crashing
i can work with this at least; no idea why my defaults got changed that way
👍
yeah thats odd. I can only think that kvantum was overwriting them.
Ahaha, so turns out, I get this error even on fresh installs
Wild
I'm having the very same issue of black screen after login, the cp to defaults solution works for me. Prior doing that I have been rolling back and rebasing to old version with no luck. I have tried rebasing to the past 4 versions with no luck. but after doing the cp defaults method works. Thank you.
The issue started to me after waking up the system from sleep. which I really find it weird.