Bug 2411883

Summary:	symbol lookup error: /usr/bin/kwin_wayland: undefined symbol: _ZN21KGlobalAccelInterface10KeyPressedEI\n
Product:	[Fedora] Fedora	Reporter:	Art Haas <ahaas>
Component:	kwin	Assignee:	marcdeop
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	42	CC:	headless, jgrulich, kde-sig, marcdeop, suraj.ghimire7, than
Target Milestone:	---	Keywords:	Desktop
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Art Haas 2025-11-02 17:34:57 UTC

After applying the available upgrades on October 31 to my Fedora 42 system running KDE, the system would not display the login screen after reboot. I could log in to a terminal via ctrl-alt-f2, and I saw the message shown in the bug summary in the 'journalctl -b' output.

Reproducible: Always

Steps to Reproduce:
1.Reboot
2.
3.
Actual Results:
No login screen.

Expected Results:
Login screen appears.

Additional Information:
The KDE spin of Fedora 42 is running on a Dell Latitude E5530 laptop and has worked wonderfully for years and multiple Fedora versions. A big thank you to everyone who has and continues to work on Fedora. I also have the XFCE spin running on some older Dell Optiplex desktops and the GNOME Fedora spin running on an HP 420Z workstation.

Comment 1 headless 2025-11-03 18:26:38 UTC

Seeing the same symptopms on two systems (Dell like above and Thinkpad C13 Yoga).
Only "user" option is to choose Gnome on login screen.
After succesfull Gnome login, running kwin in terminal gives the same:
$ kwin
kwin: symbol lookup error: kwin: undefined symbol: _ZN21KGlobalAccelInterface10keyPressedEi

The only threads i found online are:
https://discussion.fedoraproject.org/t/sddm-failure-after-system-update/171613/3
(the f42 fix from https://bodhi.fedoraproject.org/updates/FEDORA-2025-ebed8db9ab did not install, as in comment)

and (inaccurate?)
https://github.com/clearlinux-pkgs/kglobalaccel/blob/main/symbols

dnf repoquery --installed | grep kglobal
kf5-kglobalaccel-0:5.116.0-3.fc42.x86_64
kf5-kglobalaccel-libs-0:5.116.0-3.fc42.x86_64
kf6-kglobalaccel-0:6.19.0-1.fc42.x86_64
kglobalacceld-0:6.5.1-1.fc42.x86_64

dnf repoquery --installed | grep kwin
kf5-kwindowsystem-0:5.116.0-3.fc42.x86_64
kf6-kwindowsystem-0:6.19.0-2.fc42.x86_64
kwin-0:6.4.5-1.fc42.x86_64
kwin-common-0:6.4.5-1.fc42.x86_64
kwin-libs-0:6.4.5-1.fc42.x86_64

Comment 2 headless 2025-11-04 15:18:25 UTC

as mentioned in thread https://discussion.fedoraproject.org/t/sddm-failure-after-system-update/171613/14
the fixes from 
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1cae83c73e

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

followed by https://bodhi.fedoraproject.org/updates/FEDORA-2025-ebed8db9ab

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

fixed plasma for me. yay!

Comment 3 Art Haas 2025-11-04 18:42:33 UTC

Running the first 'dnf upgrade' command pulled down a variety of updates which did the trick. The second 'dnf upgrade' command didn't match anything.

My laptop is once again working normally. Thanks to all who contributed to fixing the issue.