Hi. Rob Brewer - 04.09.25, 16:30:07 CEST: > > Not using Systemd here, so cannot really comment on that. Grepping the > > process list during a running Plasma session for "konqi" or "sentry" > > does not reveal any processes. > > I wish I wasn't using systemd but its difficult to run Debian without > it. The drkonqi-sentry-postman.service would seem to be on a timer > which runs at startup and on the hour and presumably started by > systemd, so unless you check the running process on the hour you would > probably be unlikely to notice it.
I am pretty sure no one replicated this setup for Runit based systems, so… unless KDE starts it by some other means, like for example with "kded", then it might just not run here. At least by looking at the package drkonqi – see below – it does not seem to be auto started by DBUS in case Systemd is not available. I think in case it is triggered by a timer then you can disable or mask the timer. Like systemctl --user disable drkonqi-sentry-postman.timer systemctl --user mask drkonqi-sentry-postman.timer Also… as a last effort brute force approach for now, you could replace the binary in "Exec=" in the service file with "/usr/bin/true" or something like that. You could also chmod "/usr/lib/x86_64-linux-gnu/libexec/ drkonqi-sentry-postman" to 000. At least as a stop-gap measure. Those service and timer files are in package "drkonqi". So I bet that is the package to report a bug for. It might even be possible to just remove that package. However in addition to some meta packages for some odd reason this would also remove the breeze themes for SDDM. So currently I'd not recommend to do that. Also you may prefer to keep those meta packages. Best, -- Martin
