Created attachment 146235 [details] coredumpctl gdb SUMMARY When trying to login to KDE Plasma desktop from the graphical login screen, it crashes See attached core dump ((kwin_wayland). On the same laptop, selecting KDE-X11 Desktop or Gnome Wayland works fine, so it is only KDE Plasma that no longer works/crashes. I did not have this problem before Jan. 28,2022. STEPS TO REPRODUCE 1. I rebooted my laptop (Dell Latitude 5590 running Fedora Core 34) after a "dnf update". 2. At the graphical login screen, I select KDE Plasma desktop. 3. I get a black screen, nothing happens. OBSERVED RESULT I get a black screen. EXPECTED RESULT I should be getting my KDE Plasma Desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Core 34 KDE Plasma Version: plasmashell 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 All these were installed via the "dnf" command and the Fedora "update" rpm channel. ADDITIONAL INFORMATION Today I rebooted my laptop (Dell Latitude 5590 running Fedora Core 34) after a "dnf update". At the graphical login screen, I selected KDE Plasma desktop, and put in my username and password, hit enter, then I get a black screen, nothing happens. I waited several minutes, still no desktop is shown. I have never had this problem before, KDE Plasma Desktop has worked very well for me previously. Prior to today's reboot, I did "dnf update" and rebooted the laptop on Jan 28, 2022 and everything worked fine on Jan 28. So it seems there is some rpm package that got installed AFTER Jan 28, 2022 that is causing this problem. For testing: I rebooted the laptop and at the graphical login screen I selected KDE-X11 desktop, it brings up the KDE-X11 desktop just fine. I also tried the GNOME Desktop and it also works fine, after that I tried the KDE Plasma desktop again but it still crashes. See attached core dump.
It seems to be related to KGlobalAccel and d-bus. #0 0x00007f7e8eb942a2 raise (libc.so.6 + 0x3d2a2) #1 0x00007f7e8eb7d950 abort (libc.so.6 + 0x26950) #2 0x00007f7e8e844b16 _dbus_abort.cold (libdbus-1.so.3 + 0x10b16) #3 0x00007f7e8e86b010 _dbus_warn_check_failed (libdbus-1.so.3 + 0x37010) #4 0x00007f7e9100c869 _ZN22QDBusConnectionPrivate19getNameOwnerNoCacheERK7QString (libQt5DBus.so.5 + 0x2e869) #5 0x00007f7e9100dd19 _ZN22QDBusConnectionPrivate13addSignalHookERK7QStringRKNS_10SignalHookE (libQt5DBus.so.5 + 0x2fd19) #6 0x00007f7e9100f821 _ZN9QtPrivate11QSlotObjectIM22QDBusConnectionPrivateFbRK7QStringRKNS1_10SignalHookEENS_4ListIJS4_S7_EEEbE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb (libQt5DBus.so.5 + 0x31821) if you've updated qt5 or libdbus-1, can you try rolling them back?
.
I have dbus-libs-1.12.20-3.fc34.x86_64, but it has not been updated since Jan. 28. 2022, but indeed qt5-qtwayland was updated Feb. 3, from version qt5-qtwayland-5.15.2-15 to version qt5-qtwayland-5.15.2-17. I tried to downgrade to version qt5-qtwayland-5.15.2-15 but that version no longer exists on the Fedora Update mirrors, so I downgraded to qt5-qtwayland-5.15.2-4.fc34.x86_64 and now when I login to KDE Plasma desktop from the graphical login screen it works just fine without any crash or any other problems. So it is the qt5-qtwayland-5.15.2-17 package that is causing my crash problem. Thank you very much for your help!