• Bug#1102651: drkonqi: tries to launch multiple times per second and fai

    From JuliusZet@21:1/5 to All on Wed Jul 23 17:20:01 2025
    Package: drkonqi
    Version: 6.3.4-1
    Followup-For: Bug #1102651

    Dear Maintainer,

    I did a fresh Trixie installation yesterday using the RC2 netinst iso and then installed the KDE-Plasma desktop environment with "apt install kde-plasma-desktop".

    After a reboot my journal gets flooded with the same messages, as other users already reported.

    I am looking at the commit that introduced the ConditionUser=!@system check that seems to be the reason for those journal messages: https://invent.kde.org/plasma/drkonqi/-/commit/7dca985d21d76a98b4d39196404060c928afb9f4

    To me the commit message sounds like running drkonqi as root is not supported.

    Executing
    "systemctl --global disable drkonqi-coredump-launcher.socket" as root and "systemctl --user enable drkonqi-coredump-launcher.socket" as my user
    and rebooting once again seems to fix it.

    But I am kindly asking if there would be a way for you as the maintainer to fix it in the package. Because, if I understand it correctly, everybody who installs the KDE-Plasma desktop environment would have this issue because plasma-workspace depends on
    drkonqi.

    I would appreciate if it could be fixed before the official release of Trixie.

    Thank you very much in advance and have a nice day!


    -- System Information:
    Debian Release: 13.0
    APT prefers testing-security
    APT policy: (500, 'testing-security'), (500, 'testing')
    Architecture: amd64 (x86_64)

    Kernel: Linux 6.12.35+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
    Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    Versions of packages drkonqi depends on:
    ii init-system-helpers 1.68
    ii kio6 6.13.0-6
    ii kwallet6 6.13.0-1
    ii libc6 2.41-10
    ii libgcc-s1 14.2.0-19
    ii libkf6configcore6 6.13.0-2
    ii libkf6configgui6 6.13.0-2
    ii libkf6coreaddons6 6.13.0-1
    ii libkf6crash6 6.13.0-1
    ii libkf6i18n6 6.13.0-1
    ii libkf6idletime6 6.13.0-1
    ii libkf6kiocore6 6.13.0-6
    ii libkf6kiogui6 6.13.0-6
    ii libkf6notifications6 6.13.0-1
    ii libkf6service-bin 6.13.0-1
    ii libkf6service6 6.13.0-1
    ii libkf6statusnotifieritem6 6.13.0-1
    ii libkf6syntaxhighlighting6 6.13.0-1
    ii libkf6wallet6 6.13.0-1
    ii libkf6widgetsaddons6 6.13.0-1
    ii libkf6windowsystem6 6.13.0-2
    ii libpolkit-qt6-1-1 0.200.0-4+b1
    ii libqt6core6t64 6.8.2+dfsg-8
    ii libqt6dbus6 6.8.2+dfsg-8
    ii libqt6gui6 6.8.2+dfsg-8
    ii libqt6network6 6.8.2+dfsg-8
    ii libqt6qml6 6.8.2+dfsg-7
    ii libqt6widgets6 6.8.2+dfsg-8
    ii libstdc++6 14.2.0-19
    ii libsystemd0 257.7-1
    ii qml6-module-org-kde-kirigami 6.13.0-2
    ii qml6-module-org-kde-kitemmodels 6.13.0-1
    ii qml6-module-org-kde-syntaxhighlighting 6.13.0-1

    Versions of packages drkonqi recommends:
    ii python3-psutil 7.0.0-2
    ii python3-sentry-sdk 2.18.0-1
    ii systemd-coredump 257.7-1

    drkonqi suggests no packages.

    -- no debconf information

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JuliusZet@21:1/5 to All on Sat Jul 26 13:10:01 2025
    Package: drkonqi
    Version: 6.3.4-1
    Followup-For: Bug #1102651

    Executing the command

    systemctl --user mask drkonqi-coredump-launcher.socket

    as root is probably a better work-around than what I mentioned in my previous message.

    I am still concerned though that a lot of people will install KDE Plasma and will get their journals spammed - unless they manually mask the unit.

    Is there really nothing we can do about this? :/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)