I get the same as you when I use list-unit-files. Apparently list-units only shows "active" units...perhaps drkonqi-coredump-processor only becomes active when invoked by systemd-coredump. I'm afraid I'm running into complexities of how systemd works that I'm not familiar with. The page https://github.com/KDE/drkonqi indicates that drkonqi-coredump-processor@.service should be enabled. It seems to be disabled on both our systems. It seems reasonable to me that a timeout might stop the service, but not disable it. It's unclear to me what your journalctl messages mean...the show a different service name ("...-pickup", which is not listed according to your list-unit-files / grep command). Is drkonqi-coredump-processor@.serviced intentionally disabled in Tumbleweed by default? Should it be? On 7/1/24 11:35 AM, Lassi Väätämöinen wrote:

On sunnuntaina 30. kesäkuuta 2024 19.30.25 UTC+3 Eric Schwarzenbach wrote:

...

nor do I find it with list-units. Web searches don't give me any sense that KDE has moved away from using it...has openSUSE for some reason?

The package drkonqi6 is definitely installed on my system. YEsterday it provided me with crash reports. I had some issues starting Plasma 6.1.1. now. But for me, DrKonqi is listed, but disable now. Maybe there was a timeout or some such:

...

sudo systemctl list-unit-files |grep core drkonqi-coredump-processor@.service disabled enabled systemd-coredump@.service static - systemd-coredump.socket static -

Journalctl seems to agree with my guess:

18:08:04 kaappi systemd[7925]: drkonqi-coredump-pickup.service: Service reached runtime time limit. Stopping. 18:08:04 kaappi systemd[7925]: drkonqi-coredump-pickup.service: Failed with result 'timeout'.