Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1241786 > unrolled thread
| Started by | dE <de.techno@gmail.com> |
|---|---|
| First post | 2025-04-13 14:30 +0200 |
| Last post | 2025-04-27 02:10 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#1102945: drkonqi:6.3.4-1 enables user systemd unit for root user. dE <de.techno@gmail.com> - 2025-04-13 14:30 +0200
Bug#1102945: drkonqi:6.3.4-1 enables user systemd unit for root user. Witold Baryluk <witold.baryluk@gmail.com> - 2025-04-27 02:10 +0200
| From | dE <de.techno@gmail.com> |
|---|---|
| Date | 2025-04-13 14:30 +0200 |
| Subject | Bug#1102945: drkonqi:6.3.4-1 enables user systemd unit for root user. |
| Message-ID | <KB4Df-ddOT-5@gated-at.bofh.it> |
Package: drkonqi Version: 6.3.4-1 Severity: important dpkg --search drkonqi-coredump-launcher.socket drkonqi: /usr/lib/systemd/user/sockets.target.wants/drkonqi-coredump-launcher.socket drkonqi: /usr/lib/systemd/user/drkonqi-coredump-launcher.socket This package is installing a systemd unit for all users with lines -- ConditionUser=!@system which results in endless logs of -- drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). 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. First this must not be enabled for all users. Some users are not using GUI or QT applications at all. In my case, this dependency was pulled by plasma-workspace. This can't even be disabled because -- # systemctl --user disable drkonqi-coredump-launcher.socket The following unit files have been enabled in global scope. This means they will still be started automatically after a successful disablement in user scope: drkonqi-coredump-launcher.socket This has to be masked for the root user.
[toc] | [next] | [standalone]
| From | Witold Baryluk <witold.baryluk@gmail.com> |
|---|---|
| Date | 2025-04-27 02:10 +0200 |
| Message-ID | <KFXKN-gvc4-1@gated-at.bofh.it> |
| In reply to | #1241786 |
Package: drkonqi Version: 6.3.4-1 Followup-For: Bug #1102945 X-Debbugs-Cc: witold.baryluk@gmail.com Dear Maintainer, I think I am seeing same issue. I have multiple DMs installed, including Plasma. But I use Gnome Shell or MATE usually, with zero QT applications running. And Gdm as DM. This happens even on a clean reboot. Yes, I see systemd journal spammed: Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). Apr 26 23:57:16 debian systemd[21468]: 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. every 10 seconds I cannot even uninstall it easily, because it also causes uninstall of few other meta-packages (causing apt to show about 100 other packages to be marked as auto installed, including plasma and some other KDE programs), and also for example sddm themes. Which I would prefer it did not uninstall. Cheers -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.15.0-rc3 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages drkonqi depends on: ii init-system-helpers 1.68 ii kio6 6.13.0-2 ii kwallet6 6.13.0-1 ii libc6 2.41-7 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-2 ii libkf6kiogui6 6.13.0-2 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-1 ii libpolkit-qt6-1-1 0.200.0-4+b1 ii libqt6core6t64 6.8.2+dfsg-5+b1 ii libqt6dbus6 6.8.2+dfsg-5+b1 ii libqt6gui6 6.8.2+dfsg-5+b1 ii libqt6network6 6.8.2+dfsg-5+b1 ii libqt6qml6 6.8.2+dfsg-7 ii libqt6widgets6 6.8.2+dfsg-5+b1 ii libstdc++6 14.2.0-19 ii libsystemd0 257.5-2 ii qml6-module-org-kde-kirigami 6.13.0-1 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.5-2 drkonqi suggests no packages. -- no debconf information
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web