Package: drkonqi
Version: 6.7.2-1
Severity: important
Tags: newcomer

Dear Maintainer,

drkonqi's coredump handling triggers an infinite crash loop when the
user session is not a Plasma session (e.g. plain GNOME/Wayland). This
is related to, but distinct from, Bug#1102945 (unmet condition check
spam) — in this case drkonqi-coredump-launcher actively crashes and
gets respawned repeatedly, causing severe system load rather than
just log spam.

* What led up to the situation:

  plasma-workspace (and its dependency drkonqi) was installed as a
  dependency of an unrelated KDE application, while the primary
  desktop session in use is GNOME on Wayland (gdm3 + gnome-shell,
  mutter 50.3). drkonqi-coredump-launcher.socket is enabled
  unconditionally for all users regardless of desktop environment
  (systemctl --user is-enabled drkonqi-coredump-launcher.socket
  reports "enabled").

* What exactly did you do (or not do) that was effective (or
  ineffective):

  An unrelated application (obs, PID 22301) segfaulted. This
  triggered systemd-coredump@.service, which in turn activated
  drkonqi-coredump-processor@.service and then
  drkonqi-coredump-launcher@<n>.service via the user socket.

  drkonqi-coredump-launcher immediately aborts with SIGABRT
  (QMessageLogger::fatal), apparently because it cannot find a
  working Qt platform plugin for the active GNOME/Wayland session
  (available plugins logged: minimal, xcb, eglfs, vnc, linuxfb,
  wayland-brcm, wayland-egl, wayland, minimalegl, offscreen,
  vkkhrdisplay — none initializes successfully in this context).

  Because drkonqi-coredump-launcher itself crashes, systemd-coredump
  captures *that* crash too, which appears to re-trigger the same
  socket-activation path. The result is a rapid loop:
  drkonqi-coredump-launcher is spawned, crashes with SIGABRT, is
  respawned, crashes again — observed at roughly one crash every
  ~500ms, producing 30+ core dumps (~850KB each) within 18 seconds
  from a single initial application crash.

* What was the outcome of this action:

  Desktop responsiveness degrades severely during the loop (D-Bus
  and disk I/O saturation from repeated core writes to
  /var/lib/systemd/coredump/), giving the impression that the GNOME
  session itself has crashed, even though gnome-shell remains
  running throughout (confirmed via journalctl timestamps showing
  continuous gnome-shell operation across the incident window).

* What outcome did you expect instead:

  drkonqi-coredump-launcher should not be socket-activated at all
  in a non-Plasma session, or should fail gracefully (log and exit
  once) rather than being respawned in a crash loop when no
  compatible Qt platform plugin / KDE session is available.

We believe that the bug you reported is fixed in the latest version of
drkonqi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1143811@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurélien COUDERC <coucouf@debian.org> (supplier of updated drkonqi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 10 Aug 2026 17:48:10 +0200
Source: drkonqi
Architecture: source
Version: 6.7.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Aurélien COUDERC <coucouf@debian.org>
Closes: 1143811
Changes:
 drkonqi (6.7.4-1) unstable; urgency=medium
 .
   [ Aurélien COUDERC ]
   * New upstream release (6.7.4).
     - Don't start launcher when not in a graphical session. (Closes: #1143811)
Checksums-Sha1:
 8d7387e51939367ed1b876fc4726adb8b3fbda55 2926 drkonqi_6.7.4-1.dsc
 4d11cce2db9b52fdc9de960d66309991434575c5 909580 drkonqi_6.7.4.orig.tar.xz
 d630caf46d5ecfd072c0d8a0f6bf22529db92262 488 drkonqi_6.7.4.orig.tar.xz.asc
 e2021f9f9301c1e2bad4951391ed54e79bba43f7 20968 drkonqi_6.7.4-1.debian.tar.xz
 b811f840bdfc99d4f13f17d3212843ca57862317 20986 drkonqi_6.7.4-1_amd64.buildinfo
Checksums-Sha256:
 efe83235406bb06f6c1fe324907ce2cdb97edbadb4c49f895ae182beee1ca95f 2926 drkonqi_6.7.4-1.dsc
 c7f9402b7a32e077b23d34d083926bc7a78f18b93184510def3fcc32532d6959 909580 drkonqi_6.7.4.orig.tar.xz
 862674cee19b35db38e465de29d0d79b43db158b27fd96530eba19b63d1ee2a2 488 drkonqi_6.7.4.orig.tar.xz.asc
 a9f8bcbb819d49cf14fb748858efdb4e713d0f00b966cfcce91ac276fdefc1b1 20968 drkonqi_6.7.4-1.debian.tar.xz
 38ad355a44a1e7e10a8868195973786030bb045d9c72e1d3a8ccdaf5a78c0818 20986 drkonqi_6.7.4-1_amd64.buildinfo
Files:
 19bae6d5f2f2723f7d61fa1bddbb25b1 2926 kde optional drkonqi_6.7.4-1.dsc
 cc4b7b53165f9b458743a3e732c7eebf 909580 kde optional drkonqi_6.7.4.orig.tar.xz
 1c348fd00d2a68b684d4514a05d9ef26 488 kde optional drkonqi_6.7.4.orig.tar.xz.asc
 8ea1a5f89129b35db8cbe4f0f04b9db9 20968 kde optional drkonqi_6.7.4-1.debian.tar.xz
 f68eced7cc6e3f7c1a9fc3f8086d179c 20986 kde optional drkonqi_6.7.4-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmp60kgTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJEbiD/9uFJTwYwoTzqUi0uCRHW2AZ8j6xMly
GWAPYHKRN/14wh/P0dQSJB1DtW54MyC0e/GChJHn/868ivFqz0iF+tHDH/6EAAIC
aCYRkvf87gAKc4HzhK0RWnz4cPxe7Ua/qEQ6qlwRiy/31Iy5U3YMKXE215croSUg
LNLJ4nxHaDBvfYJ4UB1eGcLI+UXzX+Y5gyvRaNrx7EHoA/lnzAIhsb4lZRTACFpt
h3wJeu5eI3lEMqkEYlM7bKiWKYvn2fcDKIJXO1yxzJjPNZ/lMSlT6s+JgFS4Q855
FD/OWSpCgAR0KH///VDp+OfO/JDeRwsGzJEzuieTmaduKVpdF3LfwdH0ITBLvUHA
xKBsCLBtaiNFIIII8ClxmYegFjdwfwo2WmzZGqq/nKwrjG6OlCY10fmFgjxkycoZ
0Y0wqfy7HgHyN7ZgIeBTHWbNm9cj9eTYp10Jhk7TkNwjUrDGsnf9k46HduNJqXIZ
X4diKhZvO7iWJAaCVsC72aC2e/pozuuLlZOeTc/H1lMMXWkvhDi62/R1xxh3sYBl
W/w13fgwy8t3cajK4ylaZTlqZ8dcXwUESF8HpoLOUf97xqH4+Uowj1XSRokEqeYJ
Ta1c1x5IZ0CXcGGDH+kg8Sx8LgPrSB6ZoEeZTUhk3RnGtf0eh6D6m6RAjMs0s6an
OA2iL9GaJoUM3A==
=NU1f
-----END PGP SIGNATURE-----