Skip to content

[DO NOT MERGE] Disable KDE drkonqi coredump handling#49

Open
zhovner wants to merge 1 commit intodevfrom
zhovner/kde-coredump-flood
Open

[DO NOT MERGE] Disable KDE drkonqi coredump handling#49
zhovner wants to merge 1 commit intodevfrom
zhovner/kde-coredump-flood

Conversation

@zhovner
Copy link
Copy Markdown
Member

@zhovner zhovner commented Apr 26, 2026

The drkonqi-coredump-launcher.socket has UpheldBy=sockets.target which causes systemd to retry it for users where ConditionUser=!@System fails (sddm, flipctl), flooding journal with thousands of messages per minute. Mask the full set of drkonqi coredump units to disable the feature entirely; coredumps are still captured by systemd-coredump.

The drkonqi-coredump-launcher.socket has UpheldBy=sockets.target which
causes systemd to retry it for users where ConditionUser=!@System fails
(sddm, flipctl), flooding journal with thousands of messages per minute.
Mask the full set of drkonqi coredump units to disable the feature
entirely; coredumps are still captured by systemd-coredump.
@zhovner zhovner requested a review from a team April 26, 2026 12:20
@zhovner zhovner changed the title Disable KDE drkonqi coredump handling [DO NOT MERGE] Disable KDE drkonqi coredump handling Apr 26, 2026
@zhovner
Copy link
Copy Markdown
Member Author

zhovner commented Apr 26, 2026

KDE fails to start

plasma-ksplash.service: start operation timed out. Terminating.
plasma-ksplash.service: Main process exited, code=killed, status=15/TERM
plasma-ksplash.service: Failed with result 'timeout'.
Failed to start plasma-ksplash.service - Splash screen shown during boot.

Comment thread debian-rk3576-ospack.yaml
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's easier to just override the unit file for drkonqi-coredump to remove the filter on !@System. It's probably not the best long term fix, but neither is removing the service altogether.

It would be great to better understand the rationale for why this condition was introduced in the first place though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants