https://bugs.kde.org/show_bug.cgi?id=444084
--- Comment #3 from pa...@web.de --- The assumption, that kscreen_backend_launcher is D-Bus activated is correct. The D-Bus service file is located in /usr/share/dbus-1/services/org.kde.kscreen.service and has the following content: [D-BUS Service] Name=org.kde.KScreen Exec=/usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher Now the question arises how to change stdout or stderr in a D-Bus service file. It seems to be possible to append some arguments to the Exec line (as in org.freedesktop.Telepathy.Client.KTp.Approver.service), but otherwise the only used attributes seem to be (found by cat /usr/share/dbus-1/services/*.service | rg = | cut -f1 -d= | sort | uniq): AssumedAppArmorLabel, Exec, Name, SystemdService, User There seems to be some documentation in https://dbus.freedesktop.org/doc/dbus-daemon.1.html in chapter INTEGRATING SYSTEM SERVICES. Maybe it's possible to not start kscreen_backend_launcher from the D-Bus service file, but instead start a systemd service, which then starts kscreen_backend_launcher with the correct logging options. -- You are receiving this mail because: You are watching all bug changes.