https://bugs.kde.org/show_bug.cgi?id=509870
--- Comment #4 from [email protected] --- Within X11 I executed sudo apt install systemd-coredump I then logged out and logged back in using Wayland. I then verified that coredumpctl was installed by opening a small xterm, determining its PID, then executing kill -SEGV <xterm PID> and then executing sudo coredumpctl list This provided the following output: TIME PID UID GID SIG COREFILE EXE SIZE Thu 2025-09-25 12:34:23 CDT 32388 1000 1000 SIGSEGV present /usr/bin/xterm 332.1K So coredumpctl is installed and functional. I then put the system into sleep mode. I then woke the system from sleep mode. Much weird display behavior is observed while moving the mouse cursor over the display. I eventually log in. I then execute sudo coredumpctl list and am again provided with the following output: TIME PID UID GID SIG COREFILE EXE SIZE Thu 2025-09-25 12:34:23 CDT 32388 1000 1000 SIGSEGV present /usr/bin/xterm 332.1K Apparently either nothing has crashed, or something is masking the crashing executable from being detected as a crash or saved as a coredump. To support this assumption, I provide the following excerpt from the execution of sudo journalctl -b 0 -r Sep 25 12:35:53 Gargantuan systemd[32919]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). If you can tell me (1) where and how to modify software to disable this condition check, I assume that (2) I can later revert this change and regain normal system operation. After performing the modification implied in item (1), I will again attempt to generate the coredump in Wayland. -- You are receiving this mail because: You are watching all bug changes.
