This pertains to this post I made earlier: https://www.kubuntuforums.net/forum/...-systemd-crash
I have filed multiple bugs with KDE and this is one of them. I am trying to enable collection of coredumps. Towards this goal, I have installed systemd-coredump. I have also modified /etc/systemd/coredump.conf and /etc/security/limits.conf. I have verified that core dumps are saved by opening an xterm, determining it's PID, executing "kill -SEGV <xterm PID>" and then executing "sudo coredumpctl list", observing
and then also observing the following inside ~/.cache/drkonqi/crashes/
Granted, this is not a core file, but I suspect it provides useful information that leads to a core file in /var/lib/systemd/coredump/.
HOWEVER, the problem is in enabling coredumps that are apparently explicitly disabled by existing configured system-level code. What do I mean? Look at the following statements extracted from "sudo journalctl -b 0 -r":
I do not understand why the unmet condition check "(ConditionPathExistsGlob=/home/<username>/.cache/drkonqi>" is present given the appearance of xterm info in ~/.cache/drkonqi/crashes/ . How do I fix this?
I also do not know where to find the system code requiring modification to remove the unment condition check "(ConditionUser=!@system)". Can you tell me where the code requiring modification resides? I assume this is either a configuration file or a shell script and it is not written in code requiring compilation.
I have filed multiple bugs with KDE and this is one of them. I am trying to enable collection of coredumps. Towards this goal, I have installed systemd-coredump. I have also modified /etc/systemd/coredump.conf and /etc/security/limits.conf. I have verified that core dumps are saved by opening an xterm, determining it's PID, executing "kill -SEGV <xterm PID>" and then executing "sudo coredumpctl list", observing
Code:
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
Code:
xterm.4a49651c1dd34c1ab5b67588c9b4e414.32388.1758821663000000.ini
HOWEVER, the problem is in enabling coredumps that are apparently explicitly disabled by existing configured system-level code. What do I mean? Look at the following statements extracted from "sudo journalctl -b 0 -r":
Code:
Sep 25 14:38:11 <hostname> systemd[44767]: drkonqi-sentry-postman.timer - Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/<username>/.cache/drkonqi> Sep 25 14:38:10 <hostname> systemd[44675]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
I do not understand why the unmet condition check "(ConditionPathExistsGlob=/home/<username>/.cache/drkonqi>" is present given the appearance of xterm info in ~/.cache/drkonqi/crashes/ . How do I fix this?
I also do not know where to find the system code requiring modification to remove the unment condition check "(ConditionUser=!@system)". Can you tell me where the code requiring modification resides? I assume this is either a configuration file or a shell script and it is not written in code requiring compilation.