A popup with the following message appears: Unable to perform shutdown org.freedesktop.hal.power-management.shutdown no <-- (action, result) [ Quit ] HAL configured as follows: [ebuild R ] sys-apps/hal-0.5.12_rc1-r2 USE="X acpi consolekit crypt disk-partition policykit -apm -debug -dell -doc -laptop (-selinux)" 0 kB XFCE4 components (excerpt, hopefully the ones you care about): [ebuild R ] xfce-base/xfce4-4.6.1 USE="alsa cups xscreensaver -minimal -oss" 0 kB [ebuild R ] xfce-extra/exo-0.3.101 USE="hal libnotify python -debug -doc" 0 kB [ebuild R ] xfce-extra/xfce4-power-manager-0.8.0_beta2 USE="xfce -debug" 0 kB Will attach a photo I took of the warning.
Created attachment 190415 [details] xfce-shutdown-failure.jpg
This is policykit denying access. Do you have hal emerged with the policykit flag? If so, do you have consolekit installed and running (/etc/init.d/consolekit)? I suspect you have 2 options: you can enable policykit and consolekit, and add consolekit to your default runlevel, or you can disable the policykit USE flag.
I have added the consolekit init script to the default runlevel. I can confirm that HAL has both consolekit & policykit set on both systems. Both systems still fail to shut down or reboot, the error message remains the same.
Adding xfce@g.o for informational purposes
Well I suspect this change as root of all evil: Do we have to add this rules on our own in the future? --- /etc/dbus-1/system.d/hal.conf 2009-06-03 15:47:26.000000000 +0200 +++ /etc/config-archive/etc/dbus-1/system.d/hal.conf 2009-05-14 21:59:55.000000000 +0200 @@ -15,7 +15,6 @@ </policy> <!-- Allow anyone to invoke methods on the Manager and Device interfaces --> - <!-- Policykit regulates actual access --> <policy context="default"> <allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.DBus.Introspectable"/> @@ -58,5 +57,48 @@ </policy> + <!-- Gentoo specific rules to allow 'plugdev' group to access Volumes and Power Management --> + <policy group="plugdev"> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.DBus.Introspectable"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.DBus.Properties" /> + + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Manager"/> + + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.CPUFreq"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.DockStation"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.KillSwitch"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.KeyboardBacklight"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.LaptopPanel"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.Leds"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.LightSensor"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.Storage"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.Storage.Removable"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.Volume"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.WakeOnLan"/> + <allow send_destination="org.freedesktop.Hal" + send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/> + + </policy> + </busconfig>
Those rules are added if you have -policykit on hal. Otherwise, they are not. If you have +policykit on hal, you must use policykit/consolekit to enable this kind of thing.
Well, then hal should definetly state this in it's elog! And maybe one should provide a policy to regain the old behaviour. Changing such things without being notified is not an option. BTW: There is no way to zu circumvent consolkit with pam enabled and bluez-4.x since this rdepends pambase with consolkit enabled...
Hal does state this in the elog; and there's no reason why you can't emerge hal with -policykit even if something else is depending on policykit. I haven't tried it, but it should work. As for the option to re-add that policy, that is dbus policy. It allows one to send messages to hal. If hal is build with policykit enabled, then everyone can send messages to hal, and hal will use policykit to decide whether to answer the request. The policy files for dbus and the status of the plugdev group won't matter. Sort answer: For a desktop system, if you have -policykit, you need to be in plugdev. This has not changed. If you have policykit, then hal will use policykit to authenticate everything. This has not changed. All that's changed is that root is now included in the need for being in plugdev (and this is a change in dbus, not in hal).
Nothing left for xfce@ to do.
Let me know if there's still a problem.
I just tripped over this problem (and then googled this bug report) after globally enabling the policykit flag. Could someone leave a pointer here how to add a policy to re-enable shutdown and friends? (I'm using xfce, not gnome.)
