Hello, Thanks, but, as I said, I had followed the instructions on the Wiki, which were exactly what you sent. It still does not work. Is there anything else that might be causing the issue? -- Leonid

On Fri, Feb 13, 2009 at 08:36:12AM +0100, Jan de Groot wrote:

Remember that this configuration inside policykit will allow EACH and EVERY user on your system to do these actions, which is wrong. There's consolekit for this. Sessions should either be launched via kdm or gdm which have native consolekit support, or using ck-launch-session when starting from xinitrc. There's also a pam module that can be used, but somehow it doesn't always work fine (slim doesn't work with it at least).

IMHO the recent updates needed a news. And what about the GUI interfaces policykit-gnome and policykit-kde?

Even specifying the user with <match user="sjoden"> would alloy all users the same priveledges? On Thu, Feb 12, 2009 at 11:36 PM, Jan de Groot wrote:

On Thu, 2009-02-12 at 15:11 -0800, Zack wrote:

...

This will likely fix the problem for you. Put this in /etc/PolicyKit/PolicyKit.conf and restart hal, /etc/rc.d/hal restart.

<config version="0.1"> <match user="yourusername"> <match action="org.freedesktop.hal.storage.*"> <return result="yes" /> </match> <match action="hal-storage-mount-fixed-extra-options"> <return result="yes" /> </match> <match action="hal-storage-mount-removable-extra-options"> <return result="yes" /> </match> </match> </config>

Remember that this configuration inside policykit will allow EACH and EVERY user on your system to do these actions, which is wrong. There's consolekit for this. Sessions should either be launched via kdm or gdm which have native consolekit support, or using ck-launch-session when starting from xinitrc. There's also a pam module that can be used, but somehow it doesn't always work fine (slim doesn't work with it at least).

Ok. That is working for me though. All I've done is add that to the PolicyKit.conf, used gconf to set openbox as the default wm in gnome, and start X with 'exec gnome-session' with SLiM. On Fri, Feb 13, 2009 at 12:16 PM, Leonid Grinberg wrote:

It shouldn't, no. However, in this case, it's not allowing it even to the specified user.

On Fri, 2009-02-13 at 15:37 -0500, Leonid Grinberg wrote:

Wait, I am using KDE (vanilla 4.2, not kdemod) not SLiM. Should I do something analogous for KDE?

KDE 4.2 has native consolekit integration when using kdm, so in that case there's nothing you have to change. If you want to use startx, you should use "exec ck-launch-session startkde4" instead of just "exec startkde4".

On Fri, 2009-02-13 at 16:30 -0500, Leonid Grinberg wrote:

So, though I am using KDE, I am actually doing it through GDM. Is there a way to get GDM to integrate it?

2009/2/13 Jan de Groot :

...

On Fri, 2009-02-13 at 15:37 -0500, Leonid Grinberg wrote:

...

Wait, I am using KDE (vanilla 4.2, not kdemod) not SLiM. Should I do something analogous for KDE?

KDE 4.2 has native consolekit integration when using kdm, so in that case there's nothing you have to change. If you want to use startx, you should use "exec ck-launch-session startkde4" instead of just "exec startkde4".

both kdm and gdm have consolekit integration, so this should all work fine on your system without any modification.