[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: SystemSettings:: PolicyKit:: the bootstrap problem
From:       KSU <ksu257 () earthlink ! net>
Date:       2009-06-07 21:09:44
Message-ID: 4A2C2C98.8020106 () earthlink ! net
[Download RAW message or body]

George Kiagiadakis wrote:
> 2009/6/7 KSU <ksu257@earthlink.net>:
>> So, KDE-4.3 uses PolicyKit to provide access to SystemSettings::Login
>> Manager. �But, it appears that PolicyKit is also used to control access
>> to SystemSettings:PolicyKit Authorization. �This results in a bootstrap
>> problem. �Didn't anyone consider this?
>>
>> The question is, how do I authorize a user account (not using
>> SystemSettings?) so that I can use SystemSettings::PolicyKit
>> Authorization to authorize the user account to gain access to various
>> things -- specifically to configure the Login Manager in this case.
> 
> Yeah, it seems a bit weird... I faced this problem a few days ago as
> well. I finally solved it by adding this to my
> /etc/PolicyKit/PolicyKit.conf, inside the <config> tag:
> 
>         <match action="org.freedesktop.policykit.modify-defaults">
>                 <return result="auth_admin"/>
>         </match>
> 
> This allows me to modify settings in the systemsettings policykit
> module and asks me for the root password when I modify something.
> There may be better ways of doing this, I'm just telling you what
> worked for me.
>  
Thank you for the suggestion.  I tried it and it didn't work.

IIUC, the authorization should show up in the list of explicit 
authorizations; it didn't.

So, I tried:

	<match user="foo">
  		<return result="yes"/>
  	</match>

and that didn't work.

-- 
JRT

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]