Systemd on a Debian Trixie system with KDE desktop environment keeps
emitting huge amount of logs in systemd-journal every 10 seconds.

systemd[2274]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for
a systemd-coredump crash was skipped because of an unmet condition check
(ConditionUser=!@system).
systemd[2274]: drkonqi-coredump-launcher.socket: Unit needs to be started
because active unit sockets.target upholds it, but not starting since we tried
this too often recently. Will retry later.

The logs generated in systemd-journal is shown in the following paste:
https://pb.greep.fr/?2592313fef1f9d0e#914kbwXzvxQX6FF3t7DGMDoYQLYqwRqgsv3i6uMUSvpN

This problem has been replicated on Debian Live DVD (KDE variant) and a
freshly installed Debian KDE VM.

This has made it very hard to administer a computer/server with debian and
KDE desktop environment installed.