SDDM Failure after System Update

So I updated my system yesterday (still using Fedora 42), after which I was met with a black screen after the next boot. To be precise, the black screen appears after the splash screen. I was still able to switch to another tty to inspect the journal and discovered the following:

Nov 03 09:14:42 MRFedoraDesktop sddm-helper-start-wayland[1626]: "/usr/bin/kwin_wayland: symbol lookup error: /usr/bin/kwin_wayland: undefined symbol: _ZN21KGlobalAccelInterface10keyPressedEi\n"
Nov 03 09:14:42 MRFedoraDesktop sddm-helper[1602]: pam_unix(sddm-greeter:session): session closed for user sddm

I think sddm is unable to start because of an issue in kwin_wayland, however I have no idea how to proceed. DNF does not list any available updates, except for dolphin which cannot be updated due to a version conflict between PackageKit-Qt6 and PackageKit-Qt5, however I don’t think that these issues are related.

Does anyone have any suggestions? I would really like to avoid a full re-install, so I appreciate any help I can get.

2 Likes

You should be able to run your desktop session from the new TTY with startplasma-wayland while you wait for the bugfix

I think that (must confirm) removing rhgb from the kernel boot will also work.

I reckon this might be a separate issue from the rhgb one.

We didn’t initially see these “undefined symbol” logs on SDDM - they resemble the krunner issue that people started to see over the weekend when Plasma 6.5.1 was released into F43.

I suspect this SDDM issue is another manifestation of the 6.5.1 packaging issues we’ve been seeing.

1 Like

I’m interested in whether this kwin update will fix it.

If you want to pull it from testing, you can try the command that @anotheruser posted downthread.

1 Like

Removing rhgb from the boot arguments does not fix the issue, but unfortunately only causes the system to get completely unresponsive, as I cannot even switch to another TTY.

Starting plasma manually fails with Error: Can not contact kdeinit5!, most likely due to the same issue in kwin_wayland that causes SDDM to fail:

Nov 03 12:08:05 MRFedoraDesktop kwin_wayland_wrapper[2312]: /usr/bin/kwin_wayland: symbol lookup error: /usr/bin/kwin_wayland: undefined symbol: _ZN21KGlobalAccelInterface10keyPressedEi
Nov 03 12:08:05 MRFedoraDesktop kcminit_startup[2228]: qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
Nov 03 12:08:05 MRFedoraDesktop kcminit_startup[2228]: qt.qpa.wayland: Loading shell integration failed.
Nov 03 12:08:05 MRFedoraDesktop kcminit_startup[2228]: qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.wayland: Loading shell integration failed.
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Nov 03 12:08:05 MRFedoraDesktop kcminit_startup[2228]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Nov 03 12:08:05 MRFedoraDesktop systemd[1595]: Requested transaction contradicts existing jobs: Transaction for plasma-workspace.target/stop is destructive (plasma-workspace.target has 'start' job queued, but 'stop' is included in transaction).
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.xcb: could not connect to display :0
Nov 03 12:08:05 MRFedoraDesktop audit[2306]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2306 comm="ksplashqml" exe="/usr/bin/ksplashqml" sig=6 res=1
Nov 03 12:08:05 MRFedoraDesktop audit[2228]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2228 comm="kcminit_startup" exe="/usr/bin/kcminit" sig=6 res=1
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Nov 03 12:08:05 MRFedoraDesktop ksplashqml[2306]: 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, xcb, wayland-egl, wayland.
Nov 03 12:08:05 MRFedoraDesktop kcminit_startup[2228]: qt.qpa.xcb: could not connect to display :0
1 Like

Thanks for the heads-up. Will give it a try as soon as it lands in stable.

I think it’s somewhat more widespread problem:
i see issue: 2411883 – symbol lookup error: /usr/bin/kwin_wayland: undefined symbol: _ZN21KGlobalAccelInterface10KeyPressedEI\n

with the same _ZN21KGlobalAccelInterface10keyPressedEi missing symbol..
and latest version from testing ( Making sure you're not a bot! for F43) cannot be installed just like that.

that’s the advisory for F43!

here is the update for F42, which may have some dependency issues.

sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ebed8db9ab
2 Likes

I had this issue as well, complicated by the fact I couldn’t switch to another TTY (fortunately ssh was still functional).

First I resolved the dependency conflict by installing the update for PackageKit:

dnf install https://kojipkgs.fedoraproject.org//packages/PackageKit-Qt/1.1.4/2.fc42/x86_64/PackageKit-Qt6-1.1.4-2.fc42.x86_64.rpm

Afterwards I was able to install the update for kwin:

dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ebed8db9ab

And SDDM popped up after rebooting.

2 Likes

Just did a regular dnf update on my system, containing both of those packages, and can confirm that kwin and SDDM work again. Thanks everyone!

This thread seriously saved me from reinstalling Fedora. I thought I had messed up my install somehow. Thanks so much everyone!

If someone else also has tried to remove rhgb and now can’t open a tty-terminal: I solved this by editing in the Fedora boot menu as described here: Fedora 43 KDE sometimes boots to a black screen
I changed “quiet” to “rhgb quiet” and then I could boot far enough to open a TTY terminal and update my system now.

1 Like

This solution also worked for me. Was able to verify the problem was the same in journalctl searching for

_ZN21KGlobalAccelInterface10keyPressedEi

I’m curious how you figured out that these dnf commands would solve the issue? Hope you have time to elaborate.

Yes, the fix of
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1cae83c73e

sudo dnf upgrade --refresh --advisory=FEDORA-2025-1cae83c73e

followed by Making sure you're not a bot!

sudo dnf upgrade --refresh --advisory=FEDORA-2025-ebed8db9ab

fixed plasma for me.
along with updated plasma :slight_smile:
Thanks to ngompa and for mentioning his fix :+1:

I’m on F42 KDE. I had the SDDM blank screen too. I used ctrl + alt + F3 to get into tty3 and sudo dnf5 update –refresh. This allowed me to get SDDM going.

But now after typing the password in SDDM, I get a new blank screen. The mouse icon is visible and I can move it. If I reach a corner of the screen with the mouse, it activates one of the actions. But I can’t do anything else. I can reach tty3 and I check that everything is up to date. The updates listed above are in installed. What else can I try?

you can try booting plasma with
startplasma-wayland
from a new tty
while this new bug is fixed
and maybe report it to bugzilla.redhat.com
it is the second report here today

start plasma did not work (or maybe my steps). After SDDM log in and second blank screen, I entered tty. start plasma did a speaker sound, but then nothing.

The one thing that did work was switching to X11 on SDDM. At least now I can search the web not from my cellphone.

I will enter a bug report, but against what? kwin? plasma?

plasma-desktop ?? If you get it wrong someone there will assign the correct package.

First test if you can you use a wayland session when using a new user account.

Plasma server seems to be the culprit. ksmserver killed by SIGABRT I will start a bug report when I get home from work.

1 Like