Bug 506167

Summary: journalctl presents many "drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection." errors
Product: [Applications] drkonqi Reporter: Erwin Iosef <rblade457>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: kdedev, sitter
Priority: NOR    
Version First Reported In: 6.4.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: First encounter with "journalctl -xef"
Second encounter after reboot

Description Erwin Iosef 2025-06-25 14:40:46 UTC
Created attachment 182651 [details]
First encounter with "journalctl -xef"

I'm not sure if its related to upstream or why this happened but the journactl -xef log states too many errors with drkonqi, I have plasma installed through the "plasma" group in Arch, I don't exactly know what the problem is or even if there is one, but the massive crash errors looked concerning, perhaps somebody can look into the text and help.

This was in a testing version of Arch, using Arch's testing repositories.  I encountered these errors while using systemd 257.7, the new upstream release.

Start of each log is cropped from the top to remove device details.
Comment 1 Erwin Iosef 2025-06-25 14:41:16 UTC
Created attachment 182652 [details]
Second encounter after reboot
Comment 2 TraceyC 2025-06-26 00:39:48 UTC
Example from the first provided log


Jun 25 19:49:52 Arch-Test drkonqi-coredump-processor[754]: "/usr/bin/gmenudbusmenuproxy" 1647 "/var/lib/systemd/coredump/core.gmenudbusmenupr.1000.ff698db4ba95429a851cc057c16ab0b6.1647.1750309185000000.zst"
Jun 25 19:49:52 Arch-Test drkonqi-coredump-processor[754]: "/usr/bin/xembedsniproxy" 1721 "/var/lib/systemd/coredump/core.xembedsniproxy.1000.ff698db4ba95429a851cc057c16ab0b6.1721.1750309185000000.zst"
Jun 25 19:49:52 Arch-Test drkonqi-coredump-processor[754]: "/usr/bin/kded6" 1698 "/var/lib/systemd/coredump/core.kded6.1000.ff698db4ba95429a851cc057c16ab0b6.1698.1750309185000000.zst"
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test drkonqi-coredump-processor[754]: "/usr/bin/kaccess" 1686 "/var/lib/systemd/coredump/core.kaccess.1000.ff698db4ba95429a851cc057c16ab0b6.1686.1750309185000000.zst"
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Jun 25 19:49:52 Arch-Test systemd[487]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection.
Comment 3 TraceyC 2025-06-26 00:47:28 UTC
I don't have anything like this in my logs on either of my two systems running git-master on Solus
systemd, version: 254.24, release: 173
Comment 4 Erwin Iosef 2025-06-26 06:34:46 UTC
Is this log a real concern/possible bug, and since I'm using Arch, could it be from anything I misconfigured possibly or didn't install? I just enabled drkonqi services via the github page for it. Still I get the same list of errors. I don't want this to be a waste of the developers time since it's not a clear issue, so any way I could debug this or find out more?
Comment 5 Harald Sitter 2025-11-07 10:30:39 UTC
I believe what happens is that you have a lot of crashes in your history that we try to deal with on login. So many that we saturate the connection limit of the launcher service, hence the warning. We'll probably need to throttle picking up crashes.
Comment 6 Harald Sitter 2025-11-07 12:27:05 UTC
Which turns out is a bit complicated because we need to throttle both the reading from journald (so as to not excessively consume RAM) and the launching (so as to not use too many connections). Not a Friday task at it turns out :(