SUMMARY When the screen *BEGINS* the transition to lockscreen (idle), and I move my mouse to stop the transition, the screen remained black with only the mouse cursor showing/moving. Switching ttys, I tried to restart the plasmashell service (not sure that could be done from another tty), and it crashed. I used "loginctl" to lock all sessions and unlock that GUI one, where I could switch back to it, only to find plasmashell was still dead. With "konsole" still up, I again tried to restart plasmashell, but the same coredump was happening. I manually started plasmashell, circumventing the service, and it came back. Even with it being back, I STILL could not restart the plasmashell service without it coredumping. I'm currently still live on this system (no reboot yet) in case other testing would like to be done while in this state. STEPS TO REPRODUCE 1. Wait for screen lock to *start*, and move mouse to avoid it the moment the screen goes black (starting to lock). 2. Notice screen remains black and no unlocker is presented. Only the mouse cursor is displayed. 3. Switch tty and try to restart plasmashell service. //Fails 4. $ loginctl lock-sessions; loginctl list-sessions; loginctl unlock-session <#> 5. Switch back to GUI and notice plasmashell is still dead. 6. Try to restart plasmashell service in konsole and notice it coredumps again. 7. $ plasmashell --replace & //"--replace" not needed if "$ ps" doesn't show it running. 8. Notice plasmashell is now running after having started it manually from konsole. OBSERVED RESULT Crash EXPECTED RESULT Don't crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Dump: ***** Message: Process 698869 (plasmashell) of user 1000 dumped core. Stack trace of thread 698869: #0 0x00007f3817b6283c n/a (libc.so.6 + 0x8e83c) #1 0x00007f3817b12668 raise (libc.so.6 + 0x3e668) #2 0x00007f3817afa4b8 abort (libc.so.6 + 0x264b8) #3 0x00007f3817fd10c2 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0xa00c2) #4 0x00007f38185a8402 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x13f402) #5 0x00007f38185a8a99 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13fa99) #6 0x00007f38181ccc05 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x29bc05) #7 0x00007f38185a8b46 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13fb46) #8 0x00007f3818e4bb9e _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x175b9e) #9 0x0000556f3e29f3c6 n/a (plasmashell + 0x213c6) #10 0x00007f3817afbcd0 n/a (libc.so.6 + 0x27cd0) #11 0x00007f3817afbd8a __libc_start_main (libc.so.6 + 0x27d8a) #12 0x0000556f3e2a2515 n/a (plasmashell + 0x24515) Stack trace of thread 698870: #0 0x00007f3817bd6f6f __poll (libc.so.6 + 0x102f6f) #1 0x00007f3816c872b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x00007f3816c27162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x00007f381821bf7c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2eaf7c) #4 0x00007f38181cbe74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29ae74) #5 0x00007f38180284f6 _ZN7QThread4execEv (libQt5Core.so.5 + 0xf74f6) #6 0x00007f3818b07a9a n/a (libQt5DBus.so.5 + 0x18a9a) #7 0x00007f381802471a n/a (libQt5Core.so.5 + 0xf371a) #8 0x00007f3817b609eb n/a (libc.so.6 + 0x8c9eb) #9 0x00007f3817be47cc n/a (libc.so.6 + 0x1107cc) ELF object binary architecture: AMD x86-64 *****
Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Welp, I borked that royally... I was in the middle of my reply and thought I'd try to restart the dbus session service, and it wiped out EVERYTHING I had open (dunno if that's just to be expected?). Plasmashell and kwin, konsoles, chrome, ..., all closed down and I had to switch tty to kill that session. I'm not sure I'll keep this succinct, but in essence, I think I'll close as "NOT A BUG" since I had been screwing around with dbus while exploring systemd-nspawn containers, and the symbol trace output showed just that, which prompted me to try just restarting the debug session to see if I could then restart the plasmashell service as well. I had screwed up dbus once before while experimenting and just ended up restarting my machine when things went awry. No need to restart my machine this time, but restarting that dbus session was apparently a no-no, and I had to restart that session altogether. For completeness since asked: ***** Starting program: /usr/bin/plasmashell [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7ffff06706c0 (LWP 813826)] [New Thread 0x7fffefe6f6c0 (LWP 813827)] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [New Thread 0x7fffecbf56c0 (LWP 813828)] [New Thread 0x7fffd7c1e6c0 (LWP 813829)] [Thread 0x7fffd7c1e6c0 (LWP 813829) exited] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [New Thread 0x7fffd7c1e6c0 (LWP 813830)] Checking screens: available: (QScreen(0x5555556ce790, name="HDMI-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5555556ce790, name="HDMI-1")) Checking screens: available: (QScreen(0x5555556ce790, name="HDMI-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5555556ce790, name="HDMI-1")) kf.dbusaddons: DBus session bus not found. To circumvent this problem try the following command (with bash): export $(dbus-launch) [Thread 0x7fffd7c1e6c0 (LWP 813830) exited] [Thread 0x7fffecbf56c0 (LWP 813828) exited] [Thread 0x7ffff06706c0 (LWP 813826) exited] [Thread 0x7ffff0b69040 (LWP 813823) exited] [Thread 0x7fffefe6f6c0 (LWP 813827) exited] [New process 813823] [Inferior 1 (process 813823) exited with code 01] ***** As you can see with "DBus session bus not found", that aligns with my messing around with containers before. Not sure what I could do to restart the dbus session without every process just dropping off the face of the earth. And for a little bonus, the dbus session output after I restarted from the first screwup (note the "timeout"s: ***** ... Dec 15 15:11:00 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.34' (uid=1000 pid=1691 comm="/usr/lib/kdeconnectd") Dec 15 15:11:18 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.kde.KSplash' requested by ':1.20' (uid=1000 pid=1561 comm="/usr/bin/plasmashell --no-respawn") Dec 15 15:12:00 computerName plasma_waitforname[1740]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 15 15:12:00 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 15 15:12:18 computerName plasma_waitforname[1777]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 15 15:12:18 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1 Dec 15 15:24:41 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.36' (uid=1000 pid=1693 comm="/usr/bin/keepassxc") Dec 15 15:24:43 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.55' (uid=1000 pid=4055 comm="/opt/google/chrome/chrome --password> Dec 15 15:24:43 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Successfully activated service 'org.a11y.Bus' Dec 15 15:24:52 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating via systemd: service name='org.kde.krunner' unit='plasma-krunner.service' requested by ':1.18' (uid=1000 pid=1548 comm="/usr/bin/kglobalaccel5") Dec 15 15:24:52 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Successfully activated service 'org.kde.krunner' Dec 15 15:25:41 computerName plasma_waitforname[4195]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 15 15:25:41 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 15 17:21:03 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.45' (uid=1000 pid=1864 comm="/usr/bin/konsole") Dec 15 17:22:04 computerName plasma_waitforname[21545]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 15 17:22:04 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 16 13:24:51 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.470' (uid=1000 pid=139108 comm="notify-send hello host") Dec 16 13:25:53 computerName plasma_waitforname[139120]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 16 13:25:53 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 18 03:13:16 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.kde.KSplash' requested by ':1.20' (uid=1000 pid=1561 comm="/usr/bin/plasmashell --no-respawn") Dec 18 03:14:17 computerName plasma_waitforname[348686]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 18 03:14:17 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1 Dec 18 22:53:50 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.45' (uid=1000 pid=1864 comm="/usr/bin/konsole") Dec 18 22:54:51 computerName plasma_waitforname[464745]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 18 22:54:51 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 19 01:40:49 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.45' (uid=1000 pid=1864 comm="/usr/bin/konsole") Dec 19 01:41:49 computerName plasma_waitforname[480736]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 19 01:41:49 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 20 17:08:44 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.kde.KSplash' requested by ':1.2256' (uid=1000 pid=701124 comm="plasmashell --replace") Dec 20 17:09:45 computerName plasma_waitforname[701174]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 20 17:09:45 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1 Dec 21 12:23:47 computerName systemd[1353]: Stopping D-Bus User Message Bus... Dec 21 12:23:47 computerName systemd[1353]: Stopped D-Bus User Message Bus. Dec 21 12:23:47 computerName systemd[1353]: dbus.service: Consumed 10.556s CPU time, 6.4M memory peak, 0B memory swap peak. Dec 21 12:23:47 computerName systemd[1353]: Starting D-Bus User Message Bus... Dec 21 12:23:49 computerName systemd[1353]: Started D-Bus User Message Bus. Dec 21 12:25:36 computerName dbus-daemon[809498]: [session uid=1000 pid=809498] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.2' (uid=1000 pid=809679 comm="/usr/bi... ... ***** Although, I'm not sure about the accuracy for the timings in relation to my latest dbus/container screwup since something like "Dec 15 15:12:00 devx64 plasma_waitforname[1740]: org.kde.knotifications: WaitForName: Service was not registered within timeout" seems way to early since the login session began to be related to me screwing around with dbus/containers as I normally spend time setting up my environment first anytime I log in.