[SOLVED (mostly)] Disable drkonqi-coredump-processor

Salkay · 2024-12-06 12:09:03

I have a regular job that checks for failed systemctl services.

# systemctl list-units --state=failed
$ systemctl --user list-units --state=failed

I find this useful because I have some custom services that occasionally fail, and I need to debug. However, I'm often spammed with entries from drkonqi

# systemctl list-units --state=failed
  UNIT                                           LOAD   ACTIVE SUB    DESCRIPTION                                                                          
● drkonqi-coredump-processor@69-432995-0.service loaded failed failed Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling
● drkonqi-coredump-processor@71-432999-0.service loaded failed failed Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling
● drkonqi-coredump-processor@78-436635-0.service loaded failed failed Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling
● drkonqi-coredump-processor@80-436638-0.service loaded failed failed Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling
● drkonqi-coredump-processor@81-436647-0.service loaded failed failed Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

5 loaded units listed.

I'm not entirely sure what these are doing.

# systemctl status drkonqi-coredump-processor@69-432995-0.service
× drkonqi-coredump-processor@69-432995-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling
     Loaded: loaded (/usr/lib/systemd/system/drkonqi-coredump-processor@.service; disabled; preset: disabled)
     Active: failed (Result: timeout) since Fri 2024-12-06 19:14:40 AEDT; 8min ago
   Duration: 5min 140ms
 Invocation: 243ccf5b0f8f447ba462c3a523db8880
    Process: 433008 ExecStart=/usr/lib/drkonqi-coredump-processor --boot-id dcb7ff54ee28460eb1bfcdeed1292491 --instance 69-432995-0 (code=killed, signal=TERM)
   Main PID: 433008 (code=killed, signal=TERM)
   Mem peak: 3.4M
        CPU: 82ms

Dec 06 19:09:40 salkay systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Dec 06 19:14:40 salkay systemd[1]: drkonqi-coredump-processor@69-432995-0.service: Service reached runtime time limit. Stopping.
Dec 06 19:14:40 salkay systemd[1]: drkonqi-coredump-processor@69-432995-0.service: Failed with result 'timeout'.

In any case, my understanding is the drkonqi isn't particularly useful for vanilla Arch/KDE packages, since debug symbols aren't installed by default. Is there a way to suppress these errors? I looked at globbing systemctl list-units, but my understanding is that you can't negatively select globs. Is there a systemd service I can disable? Since these are @ instances, I'm not entirely sure how to disable them globally. Someone suggested making the binary non-executable, but that wouldn't survive updates and feels a bit hacky.

Last edited by Salkay (2024-12-08 10:55:07)

V1del · 2024-12-06 17:10:23

systemctl mask drkonqi-coredump-process@

https://wiki.archlinux.org/title/Systemd#Using_units -- look at the masking units explanation at the end of the table.

As for the general use of drkonqi, it has integration with Debuginfod so it can actually download the symbols if necessary, so it still can be useful on a desktop session with GUI application crashes.

And if it's just about getting rid of them from the output of systemcctl...

systemctl list-units --status=failed | grep -v drkonqi

Last edited by V1del (2024-12-06 17:13:45)

Salkay · 2024-12-06 22:49:19

Thanks @V1del.

systemctl mask drkonqi-coredump-process@

I wasn't really sure if referring to @ instance-style services would work. For example I can't get the status. Masking is also weird.

# systemctl status drkonqi-coredump-process@
Failed to get properties: Unit name drkonqi-coredump-process@.service is neither a valid invocation ID nor unit name.
# systemctl mask drkonqi-coredump-process@ 
Unit drkonqi-coredump-process@.service does not exist, proceeding anyway.
Created symlink '/etc/systemd/system/drkonqi-coredump-process@.service' → '/dev/null'.

With other services, they correctly report their masked status.

# systemctl status NetworkManager
○ NetworkManager.service
     Loaded: masked (Reason: Unit NetworkManager.service is masked.)
     Active: inactive (dead)

OTOH

systemctl list-units --status=failed | grep -v drkonqi

Oh yeah duh... hahaha that would work perfectly. I was overthinking it!

seth · 2024-12-07 08:52:20

I wasn't really sure if referring to @ instance-style services would work.

Are you now?
The generic should™ still run into /dev/null now and "fail" to start any instances?

Oh yeah duh... hahaha that would work perfectly. I was overthinking it!

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Salkay · 2024-12-08 10:54:38

seth wrote:

I wasn't really sure if referring to @ instance-style services would work.
Are you now?

I was going to give it another day and see, but I'm still not entirely sure. I can't really make drkonqi coredump at will, so it's a bit hard to test. I'll just leave it masked for now and see if it happens again.

seth wrote:

Please always remember to mark resolved threads

Will do! The grep solution will work fine. Thanks again.

seth · 2024-12-08 14:19:34

kill -11 <some KDE process>

will cause it to segfault what should™ trigger Dr. Konqi

Arch Linux

#1 2024-12-06 12:09:03

[SOLVED (mostly)] Disable drkonqi-coredump-processor

#2 2024-12-06 17:10:23

Re: [SOLVED (mostly)] Disable drkonqi-coredump-processor

#3 2024-12-06 22:49:19

Re: [SOLVED (mostly)] Disable drkonqi-coredump-processor

#4 2024-12-07 08:52:20

Re: [SOLVED (mostly)] Disable drkonqi-coredump-processor

#5 2024-12-08 10:54:38

Re: [SOLVED (mostly)] Disable drkonqi-coredump-processor

#6 2024-12-08 14:19:34

Re: [SOLVED (mostly)] Disable drkonqi-coredump-processor

Board footer