Closed luisbocanegra closed 10 months ago
Well, solving this doesn't seem to be as straight forward as allowing access to the restricted interface like this:
[Desktop Entry]
Exec=kde-material-you-colors
Icon=color-management
Name=KDE Material You Colors
Comment=Starts/Restarts background process
Type=Application
X-KDE-AutostartScript=true
X-KDE-DBUS-Restricted-Interfaces=org.kde.KWin.ScreenShot2
The reason it doesn't work is because kde-material-you-colors
is not running by its own (like a compiled program would do), but rather through the python interpreter.
One can test this by replacing the exec with the interpreter e.g. /usr/bin/python
and it would immediately work. But then the point of giving this privileged access to a specific program is lost, as now any python script ran through the same interpreter could possibly make bad use of that permission and that's not good.
Some solutions come to mind:
Describe the bug I just realized that in a fresh KDE installation screenshot mode doesn't work because I didn't add
X-KDE-DBUS-Restricted-Interfaces=org.kde.KWin.ScreenShot2
to the desktop file.It worked on my system because I had a dummy launcher just for that purpose and forgot to add it to the project ¯_(ツ)_/¯
To Reproduce Steps to reproduce the behavior:
kde-material-you-colors
Desktop (please complete the following information):