Bazzite 43 loads to a black screen on my Framework 13 laptop
My laptop had upgraded to 43. As the title mentions, when I boot into it, it boots into a blank screen with no ability to use Ctrl+Alt+T or anything. I don't see the login screen at all, just a black screen. All I can do is reboot. I did hear that KDE Wallpaper Engine was removed in 43 and thought to see if creating a new "~/.config/plasma-org.kde.plasma.desktop-appletsrc" would fix it as it has fixed KDE crashes in the past, but it did not help in the slightest. What options do I have? Screenshot of rpm-ostree status attached.
Edit: I did attempt a rebase just now through bazzite-rollback-helper. Rebasing to 42 works, rebasing to 43 does not.
41 Replies
I have the same problem with my Framework 13.
I looked at the logs from the last attempt to boot, but I'm not really sure what to look for.
https://paste.centos.org/view/d5b23a7a
Which mainboard are you using? I'm on the Ryzen 7 7840U
Like you, I've rebased back to 42. Bazzite-dx, specifically.
On 43 SDDM doesn't even appear, so I'm not suspicious of Plasma itself yet
Do you have any layered packages? Did you enable framework-fan-control?
I did, might try disabling that and rebasing back to 43
But if you didn't, seems unlikely to be the problem
I've got the same problem. This is kind of weird, as restarting SDDM from tty2 (
ctrl+alt+f2) fixes the issue (i'm not sure it matters, but I use FW13 AMD 7040 series)Good to know
And that's two of us with that mainboard series
I have the Ryzen AI 5 340
I did try "ujust disable-framework-automount" in case that was giving an issue, but nothin. I did contact Framework support, but haven't gotten a response yet.
So it's not the 7040 line specifically, but maybe still AMD related.
well i do have some ideas
Sorry, just saw your questions.
-No layered packages - rpm-ostree status screenshot above shows none for verification.
-framework-fan-control is enabled.
-I have tried both enable-framework-automount and disable-framework-automount with no success with either.
I also noticed that sometimes I can get 43 to show SDDM, but it's about a 20% success rate.
Both bazzite:stable and bazzite-dx:stable have this issue. I tried rebasing between them just in case it was -dx specific - it's not, unfortunately.
what happens if you log in to a tty & start KDE from there?
I'd say there's some issue with GPU initialization due to these log lines in my case
but I'm still searching for the root cause
I don't really have any idea what made the GPU busy at that time - I don't see any relevant info neither in journal nor dmesg
okay, this might be it - sunshine is having a race condition with SDDM
@Bilb @Ruven ✨ do you have sunshine enabled on your systems?
https://github.com/LizardByte/Sunshine/issues/3653
GitHub
Systemd user service causes race condition · Issue #3653 · Lizard...
Is there an existing issue for this? I have searched the existing issues Is your issue described in the documentation? I have read the documentation Is your issue present in the latest beta/pre-rel...
Not sunshine I think, but I do have an auto-dimming user service. I'll check in a bit
May be related, not had time to poke at it. My fiance's Intel PC is doing something similar. It doesn't fully boot anymore unless she uses the prior image
Finally had a chance to rebase to 43. I was able to open tty2 and use "startplasma-wayland" with no issues.
I do not have sunshine enabled
next idea
it says the card is busy
what if we made sure ut wasn't
by adding
systemd.unit=multi-user.target
this will just start just the the terminal login
no graphical anything
until you explicitly start plasmasystemd.unit=multi-user.target works as described, no graphical, but it acts no different than without it.
I tried sudo service sddm restart in tty and was able to get the login screen to come up. Could the issue be involved with sddm? Hmsudo service sddm restart works?Yes
have't seen that in years
systemctl start sddm would be the modern command
but i guess
fedora is backwards compatible
with the old wayeh it was from an old wiki page, so that explains that
if sddm loads then sddm is probably not a problem
i wonder
if sddm starts
what about kwin_wayland
I get a cursor…
so yeah
it does start
press win+w
that gives you a search box
Yep that works
where you can start apps
try launching konsole
from konsole start
plasmashellNeed sudo with it? Without, I get an error.
nope
plasmashell normally starts without sudo
so looks like we drilled down to the problem
I couldn’t get Discord to come up so I took a picture
oh
what error does discord give
My Discord is set to open in the background. I don’t know how to open it without a panel.
It does open, I just can’t see it lol
you just look for it in the search box
ruven@framework13:~$ plasmashell
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-egl, wayland, xcb.
Aborted (core dumped) plasmashell
ruven@framework13:~$
yeah seen this before i donno how to start plasmashell on KWin nowadays it seems
back in the day
just
plasmashell worked
imma need to learn it seems
kwin is the thing that shows the windows
plasmashell handles the rest
taskbar desktop etcI see this exact error as well in my
ujust logs-last-boot dump. I thought to check for it since restarting sddm works and gets me in.
Looks like there’s a thread about this on GitHub along with several other Framework laptops
https://github.com/ublue-os/bazzite/issues/3376
GitHub
SDDM display manager fails to start · Issue #3376 · ublue-os/bazzite
Describe the bug After booting the system, the screen remains completely black. No login screen appears. But i can launch plasma with tty. What did you expect to happen? I expected the system to co...
Im on a 6 year old amd only igpu laptop, same issue same solution
Chiming in, desktop PC with an Intel CPU and nVidia 1070 GPU had this same issue. Plasmashell gave the same error Ruven mentioned above. Had to use systemctl start sddm to make it work. System would re-break every reboot so had to rollback to prior update on Bazzite.
Solution
Latest update should fix this, upstream KDE bug
can confirm latest update fixed it
Works great, thank you for quickly fixing this!
https://universal-blue.discourse.group/t/black-screen-since-latest-update/10985/7
cc this post that I found
it appears I'm having a race condition myself with the gpu not being ready before sddm starts
right now rebasing to 42, but thankfully another "fix" is just to manually restart sddm after boot to get to graphical
Universal Blue
Black screen since latest update
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 don't think it's fixed it yet... :(