https://bugs.kde.org/show_bug.cgi?id=509870
--- Comment #6 from [email protected] --- (In reply to David Redondo from comment #1) > It seems plasmashell crashed. > Can you please check and if this is the case attach a backtrace of the > crash using the coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Hi, David. Please respond to my comment dated 2025-09-24 15:05:28 UTC. I see no evidence of a plasma crash. How am I supposed to provide you with core dump information when the apparent crash generated the following journalctl statement? "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)." Interpretation of this journalctl statement appears to indicate that if the crash occurs on a system process (and NOT a user process) that a core dump will not be generated. How do I get around this in order to provide you with a core dump? Thank you. Steve -- You are receiving this mail because: You are watching all bug changes.
