Package: drkonqi Version: 6.7.2-1 Severity: important Tags: a11y 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 [email protected], which in turn activated [email protected] 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. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux (Debian sid, systemd init) Desktop session: GNOME 50.3 (mutter), Wayland, gdm3 GPU: AMD Radeon RX 7900 XTX (navi31, radeonsi, ACO) Versions of packages drkonqi depends on: plasma-workspace 4:6.7.2-5 plasma-workspace-data 4:6.7.2-5 -- Workaround currently in use: systemctl --user mask drkonqi-coredump-launcher.socket -- System Information: Debian Release: forky/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (100, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 7.1.3+deb14-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages drkonqi depends on: ii elfutils 0.195-1 ii kio6 6.26.0-1 ii kwallet6 6.26.0-1 ii libc6 2.42-17 ii libgcc-s1 16.1.0-3 ii libkf6configcore6 6.26.0-1 ii libkf6configgui6 6.26.0-1 ii libkf6coreaddons6 6.26.0-3 ii libkf6crash6 6.26.0-1 ii libkf6i18n6 6.26.0-1 ii libkf6idletime6 6.26.0-1 ii libkf6kiocore6 6.26.0-1 ii libkf6kiogui6 6.26.0-1 ii libkf6notifications6 6.26.0-1 ii libkf6service-bin 6.26.0-1 ii libkf6service6 6.26.0-1 ii libkf6statusnotifieritem6 6.26.0-1 ii libkf6syntaxhighlighting6 6.26.0-1 ii libkf6wallet6 6.26.0-1 ii libkf6widgetsaddons6 6.26.0-1 ii libkf6windowsystem6 6.26.0-1 ii libpolkit-qt6-1-1 0.201.1-1 ii libqt6core6t64 6.10.2+dfsg-15 ii libqt6dbus6 6.10.2+dfsg-15 ii libqt6gui6 6.10.2+dfsg-15 ii libqt6network6 6.10.2+dfsg-15 ii libqt6qml6 6.10.2+dfsg-6 ii libqt6widgets6 6.10.2+dfsg-15 ii libstdc++6 16.1.0-3 ii libsystemd0 261.2-1 ii plasma-version [plasma-version-base-6.7] 6.7.0 ii qml6-module-org-kde-kirigami 6.26.0-2 ii qml6-module-org-kde-kitemmodels 6.26.0-1 ii qml6-module-org-kde-syntaxhighlighting 6.26.0-1 Versions of packages drkonqi recommends: ii python3-psutil 7.1.0-1 ii python3-sentry-sdk 2.64.0-1 ii systemd-coredump 261.2-1 drkonqi suggests no packages. -- no debconf information
