¡Hola Willi! El 2017-03-23 a las 18:45 +0100, Willi Mann escribió:
% su # export $(dbus-launch) # systemsettings5
in the SDDM settings window, it tells me the same as when I try it as ordinary user (I'm not allowed to save the configuration, transl. from German).
The changes made as root weren't applied to the /etc/sddm.conf file?
Unfortunately not.
As mentioned writting this change as root don't need an interaction with the agent so this should work, otherwise it's policykit at fault, not the agent. (also, you don't have an agent running as root).
Mmh, are you using apparmor with a particular configuration? Do you have another session started as root? Do you have another X session started with your user?
(assuming that you tested this with the sddm kcm)
Do you have the polkit-kde-authentication-agent-1 service running?
I have such a process running, under the desktop's user uid.
Well, any agent should be replaceable, you can kill it and start a different one, let's say lxqt-policykit's lxqt-policykit-agent.
You can test this with pkexec bash to avoid mudding the test with the kcm authhelper, if it works with lxqt-policykit-agent then the issue is in the kde agent, otherwise, please reassign the issue to policykit-1
Happy hacking, -- "The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time." -- Tom Cargill Saludos /\/\ /\ >< `/
Attachment:
signature.asc
Description: PGP signature