https://bugs.kde.org/show_bug.cgi?id=444084
David Redondo changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=444084
Bug Janitor Service changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
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.serv
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=
https://bugs.kde.org/show_bug.cgi?id=444084
--- Comment #2 from pa...@web.de ---
Some more observations:
qCDebug really goes to stderr according to https://stackoverflow.com/a/26325743
"If the process' stderr has a console attached, that's where the debug log will
go."
So one idea could be, to r
https://bugs.kde.org/show_bug.cgi?id=444084
pa...@web.de changed:
What|Removed |Added
Component|common |libkscreen
--- Comment #1 from pa...@web.de ---
S
https://bugs.kde.org/show_bug.cgi?id=444084
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=444084
pa...@web.de changed:
What|Removed |Added
CC||pa...@web.de
--
You are receiving this mail beca
