https://bugs.kde.org/show_bug.cgi?id=444084
--- Comment #4 from pa...@web.de --- Going with the systemd unit file is the way to go. After appending SystemdService=plasma-kscreen.service to /usr/share/dbus-1/services/org.kde.kscreen.service and creating /usr/lib/systemd/user/plasma-kscreen.service with the content [Unit] Description=KScreen PartOf=graphical-session.target [Service] ExecStart=/usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher Type=dbus BusName=org.kde.KScreen TimeoutSec=5sec Slice=background.slice # Disable restart as we're dbus activated anyway Restart=no and doing a restart, there are nor further kscreen warnings in the Journal. Instead they are logged with priority info as they should be, which can be checked with "journalctl --boot --output verbose _SYSTEMD_USER_UNIT=plasma-kscreen.service". I used plasma-krunner.service as a template for the plasma-kscreen.service above, which means, that the kscreen backend moves from the app.slice into the background.slice. I think this makes sense, as the kscreen backend is not really an app, but I wanted to highlight this, as it is, strictly speaking, a separate issue. So the only remaining piece for me, is to create a patch from the instruction above and submit it, I guess. -- You are receiving this mail because: You are watching all bug changes.
