Bug#525909: shutdown with hal not working
Andrei Popescu
Version: 4.6.1-1
Severity: important
Hello,
The shutdown via hal used to work for a while, but now it doesn't. I get
an error similar to this one in .xsession-errors
** (x-session-manager:5417): WARNING **: xfsm-shutdown-helper.c:234:
Failed to contact HAL:
org.freedesktop.hal.power-management.reboot-multiple-sessions auth_admin
<-- (action, result)
I also tested with a new user and hal is indeed running on my machine.
Regards,
Andrei
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xfce4-session depends on:
ii fortune-mod 1:1.99.1-3.1 provides fortune cookies on demand
ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit
ii libc6 2.9-8 GNU C Library: Shared libraries
ii libcairo2 1.8.6-2+b1 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.12-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.80-4 simple interprocess messaging syst
ii libfontconfig1 2.6.0-3 generic font configuration library
ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib
ii libglade2-0 1:2.6.4-1 library to load .glade files at ru
ii libglib2.0-0 2.20.1-1 The GLib library of C routines
ii libgtk2.0-0 2.16.1-2 The GTK+ graphical user interface
ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library
ii libpango1.0-0 1.24.0-3+b1 Layout and rendering of internatio
ii libsm6 2:1.1.0-2 X11 Session Management library
ii libwnck22 2.24.2-2 Window Navigator Construction Kit
ii libx11-6 2:1.2.1-1 X11 client-side library
ii libxfce4util4 4.6.1-1 Utility functions library for Xfce
ii libxfcegui4-4 4.6.1-1 Basic GUI C functions for Xfce4
ii libxfconf-0-2 4.6.1-1 Client library for Xfce4 configure
ii xfce4-settings 4.6.1-1 graphical application for managing
ii xfconf 4.6.1-1 utilities for managing settings in
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
Versions of packages xfce4-session recommends:
ii dbus-x11 1.2.12-1 simple interprocess messaging syst
ii hal 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer
ii x11-xserver- 7.4+2 X server utilities
ii xfce4-panel 4.6.1-1 The Xfce4 desktop environment pane
ii xfce4-utils 4.6.1-1 Various tools for Xfce
ii xfdesktop4 4.6.1-1 xfce desktop background, icons and
ii xfwm4 4.6.1-1 window manager of the Xfce project
Versions of packages xfce4-session suggests:
ii sudo 1.7.0-1 Provide limited super user privile
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Yves-Alexis Perez
> The shutdown via hal used to work for a while, but now it doesn't. I
> get
> an error similar to this one in .xsession-errors
>
> ** (x-session-manager:5417): WARNING **: xfsm-shutdown-helper.c:234:
> Failed to contact HAL:
> org.freedesktop.hal.power-management.reboot-multiple-sessions
> auth_admin
> <-- (action, result)
>
> I also tested with a new user and hal is indeed running on my machine.
Are consolekit and policykit installed on the box?
--
Yves-Alexis
Pascal Gervais
Same behavior here since the recent hal update. Consolekit and
policykit are installed. If this can help, I don't use any display
manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
Yves-Alexis Perez
> Same behavior here since the recent hal update. Consolekit and
> policykit are installed. If this can help, I don't use any display
> manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
Hmhm, good point, that may be related, I'll have to try. Andrei, how do
you start Xfce? Using a DM or directly through startx/startxfce4?
Cheers,
--
Yves-Alexis
Yves-Alexis Perez
> policykit are installed. If this can help, I don't use any display
> manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
By the way, could you try to run Xfce using:
startx /usr/bin/startxfce4
Thanks!
--
Yves-Alexis
Enrico Tröger
Hey,
>Same behavior here since the recent hal update. Consolekit and
>policykit are installed. If this can help, I don't use any display
>manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
yeah, happens here as well. And I also don't use any display manager,
just logging in into the console and then start Xfce by startxfce4.
So this might be related?
I also tried playing around with /etc/PolicyKit/PolicyKit.conf but it
didn't change anything. The current version is attached just in case
someone is interested. (my user is member of the 'powerdev' group)
To get some debug info, I stopped the hal daemon and restarted it with:
/usr/sbin/hald --verbose=yes --use-syslog
The relevant messages when trying to shutdown the system are attached
in the file hal.log. It seems the following message is quite
interesting:
[W] ci-tracker.c:366: Error doing GetSessionForUnixProcess on
ConsoleKit: org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to
lookup session information for process '2465'
Process 2465 was xfce4-session.
The only related messages in ~/.xsession-errors were:
** Message: xfsm-shutdown-helper.c:268: Using HAL to shutdown/reboot
the computer.
** (xfce4-session:2465): WARNING **: xfsm-shutdown-helper.c:234: Failed
to contact HAL: org.freedesktop.hal.power-management.shutdown no <--
(action, result)
I'm on Debian Testing with:
ii consolekit 0.3.0-2
ii hal 0.5.12~git20090406.46dc48-2
ii hal-info 20090309-1
ii libhal-dev 0.5.12~git20090406.46dc48-2
ii libhal-storage-dev 0.5.12~git20090406.46dc48-2
ii libhal-storage1 0.5.12~git20090406.46dc48-2
ii libhal1 0.5.12~git20090406.46dc48-2
ii libpolkit-dbus2 0.9-3
ii libpolkit-grant2 0.9-3
ii libpolkit2 0.9-3
ii policykit 0.9-3
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc
Andrei Popescu
> On lun, 2009-04-27 at 17:19 -0400, Pascal Gervais wrote:
> > Same behavior here since the recent hal update. Consolekit and
> > policykit are installed. If this can help, I don't use any display
> > manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
sorry for not mentioning.
> Hmhm, good point, that may be related, I'll have to try. Andrei, how do
> you start Xfce? Using a DM or directly through startx/startxfce4?
I use gdm, but I can reproduce this with both startx and startxfce4.
What else can I try?
Regards,
Andrei
P.S. Pascal, sorry for the previous mail
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
Yves-Alexis Perez
> On Tue,28.Apr.09, 07:52:35, Yves-Alexis Perez wrote:
> > On lun, 2009-04-27 at 17:19 -0400, Pascal Gervais wrote:
> > > Same behavior here since the recent hal update. Consolekit and
> > > policykit are installed. If this can help, I don't use any display
> > > manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
>
> I also have policykit and consolekit installed. First thing I checked,
> sorry for not mentioning.
>
> > Hmhm, good point, that may be related, I'll have to try. Andrei, how do
> > you start Xfce? Using a DM or directly through startx/startxfce4?
>
> I use gdm, but I can reproduce this with both startx and startxfce4.
> What else can I try?
>
Hmh, not sure. Here I'm using slim and/or gdm and didn't have any
problem. Do you use sid or squeeze at the moment?
Cheers,
--
Yves-Alexis
Yves-Alexis Perez
> [W] ci-tracker.c:366: Error doing GetSessionForUnixProcess on
> ConsoleKit: org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to
> lookup session information for process '2465'
>
> Process 2465 was xfce4-session.
Does this happen everytime. I mean, does this happen if you completely
quit the session and retry? Does this happen with another user? Does
this happen after a manual reboot? The powerdev group is not needed
anymore if you use policykit + consolekit, iirc (and anyway there's no
more dbus stuff for handling the powerdev group).
>
> The only related messages in ~/.xsession-errors were:
> ** Message: xfsm-shutdown-helper.c:268: Using HAL to shutdown/reboot
> the computer.
> ** (xfce4-session:2465): WARNING **: xfsm-shutdown-helper.c:234: Failed
> to contact HAL: org.freedesktop.hal.power-management.shutdown no <--
> (action, result)
That could be because you indeed don't have permissions to contact the
hal daemon.
>
> I'm on Debian Testing with:
Debian Testing doesn't really have a consistent situation wrt. Xfce so
it might be related too. Which Xfce packages versions do you have?
Cheers,
--
Yves-Alexis
Enrico Tröger
>On mar, 2009-04-28 at 08:02 +0200, Enrico Tröger wrote:
>
>> [W] ci-tracker.c:366: Error doing GetSessionForUnixProcess on
>> ConsoleKit: org.freedesktop.ConsoleKit.Manager.GeneralError: Unable
>> to lookup session information for process '2465'
>>
>> Process 2465 was xfce4-session.
>
>Does this happen everytime. I mean, does this happen if you completely
>quit the session and retry? Does this happen with another user? Does
Yes, it happens everytime and yes it happens also with a newly created
user.
>this happen after a manual reboot? The powerdev group is not needed
Yes. I always do a 'manual reboot' in terms of su -c "halt" or su -c
"reboot" as HAL doesn't do it for me :(.
>anymore if you use policykit + consolekit, iirc (and anyway there's no
>more dbus stuff for handling the powerdev group).
Ok, I just re-used it as I had to use it before with the old HAL stuff.
Some more information:
I noticed my previously posted PolicyKit.conf was invalid XML by a
copy&paste mistake. After cleaning it(attached for reference) up I get:
[09:34] enrico@ukio (0): ~/src$ polkit-auth
org.freedesktop.hal.power-management.shutdown
org.freedesktop.hal.power-management.shutdown-multiple-sessions
org.freedesktop.hal.power-management.reboot
org.freedesktop.hal.power-management.reboot-multiple-sessions
org.freedesktop.hal.power-management.suspend
org.freedesktop.hal.power-management.hibernate
org.freedesktop.hal.storage.unmount-others
[09:35] enrico@ukio (0): ~/src$ polkit-config-file-validate
[09:35] enrico@ukio (0): ~/src$
[09:35] enrico@ukio (0): ~/src$ polkit-action --action
org.freedesktop.hal.power-management.shutdown
action_id: org.freedesktop.hal.power-management.shutdown
description: Shut down the system
message: System policy prevents shutting down
the system
default_any: no
default_inactive: no
default_active: yes
I guess "message: System policy prevents shutting down" is not
really what I want.
With an empty PolicyKit.conf I get no output at all from polkit-auth.
>> I'm on Debian Testing with:
>
>Debian Testing doesn't really have a consistent situation wrt. Xfce so
>it might be related too. Which Xfce packages versions do you have?
Self-compiled SVN version (currently the same as 4.6.1).
Yves-Alexis Perez
> > On lun, 2009-04-27 at 17:19 -0400, Pascal Gervais wrote:
> > > Same behavior here since the recent hal update. Consolekit and
> > > policykit are installed. If this can help, I don't use any display
> > > manager like GDM, XDM, SLIM, etc. I start Xfce with startxfce4.
>
> I also have policykit and consolekit installed. First thing I checked,
> sorry for not mentioning.
>
> > Hmhm, good point, that may be related, I'll have to try. Andrei, how do
> > you start Xfce? Using a DM or directly through startx/startxfce4?
>
> I use gdm, but I can reproduce this with both startx and startxfce4.
> What else can I try?
With gdm it should work fine. Could you try ck-list-sessions and report
what it give?
Without gdm, it seems that you need libpam-ck-connector. Could you
install it, log out and log back in, then start xfce (using startxfce4
or startx /usr/bin/startxfce4). And retry ck-list-sessions as well as
the shutdown stuff.
I hope it'll fix your problem. If it does, we'll add a recommends on
xfce4-session for this one.
Cheers,
--
Yves-Alexis
Andrei Popescu
On Tue,28.Apr.09, 14:09:43, Yves-Alexis Perez wrote:
>
> With gdm it should work fine. Could you try ck-list-sessions and report
> what it give?
$ ck-list-sessions
Session18:
unix-user = '1000'
realname = 'Andrei Popescu,,,'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2009-04-28T06:05:21.601257Z'
login-session-id = '4294967295'
> Without gdm, it seems that you need libpam-ck-connector. Could you
> install it, log out and log back in, then start xfce (using startxfce4
> or startx /usr/bin/startxfce4). And retry ck-list-sessions as well as
> the shutdown stuff.
>
> I hope it'll fix your problem. If it does, we'll add a recommends on
> xfce4-session for this one.
Sorry:
$ dpkg -l libpam-ck-connector | grep ^ii
ii libpam-ck-connector 0.3.0-2 ConsoleKit PAM module
It's already a Recommends of consolekit.
Regards,
Andrei
Enrico Tröger
>On mar, 2009-04-28 at 09:10 +0300, Andrei Popescu wrote:
>> On Tue,28.Apr.09, 07:52:35, Yves-Alexis Perez wrote:
>> > On lun, 2009-04-27 at 17:19 -0400, Pascal Gervais wrote:
>> > > Same behavior here since the recent hal update. Consolekit and
>> > > policykit are installed. If this can help, I don't use any
>> > > display manager like GDM, XDM, SLIM, etc. I start Xfce with
>> > > startxfce4.
>>
>> I also have policykit and consolekit installed. First thing I
>> checked, sorry for not mentioning.
>>
>> > Hmhm, good point, that may be related, I'll have to try. Andrei,
>> > how do you start Xfce? Using a DM or directly through
>> > startx/startxfce4?
>>
>> I use gdm, but I can reproduce this with both startx and
>> startxfce4. What else can I try?
>
>With gdm it should work fine. Could you try ck-list-sessions and report
>what it give?
>
>Without gdm, it seems that you need libpam-ck-connector. Could you
>install it, log out and log back in, then start xfce (using startxfce4
>or startx /usr/bin/startxfce4). And retry ck-list-sessions as well as
>the shutdown stuff.
>
>I hope it'll fix your problem. If it does, we'll add a recommends on
>xfce4-session for this one.
It did for me, sort of.
After installing libpam-ck-connector, ck-list-sessions actually
recognises the session and prints it.
But with a plain PolicyKit.conf I still couldn't shutdown/reboot my
system. I had to uncomment the content of the posted PolicyKit.conf to
get it working. After that, polkit-auth listed the shutdown and reboot
actions and shutting down the system from Xfce actually worked.
Why did the *kit guys make things so complicated?
The remaining questions are:
- Shouldn't it work a bit more out of the box, also for users without
any fancy display manager?
- Is it worth forwarding this bug to the consolekit/policykit packages
to get some more input?
Andrei Popescu
> $ dpkg -l libpam-ck-connector | grep ^ii
> ii libpam-ck-connector 0.3.0-2 ConsoleKit PAM module
Hello again,
As per the information in #525945 and #526009 I *purged*
libpam-ck-connector and now restart works with gdm and startx, but not
with startxfce4.
HTH,
Enrico Tröger
>> But with a plain PolicyKit.conf I still couldn't shutdown/reboot my
>> system. I had to uncomment the content of the posted PolicyKit.conf
>> to get it working. After that, polkit-auth listed the shutdown and
>> reboot actions and shutting down the system from Xfce actually
>> worked.
>
>That's weird. But anyway it's a policykit problem. And btw I think you
>changed something, because it does work out of the box on all machines
>I tried.
Ok, good to hear it's only on my system. At least good for other
users :).
But then, just for curiosity, I want to know what's different on my
system.
[20:42] enrico@ukio (0): /tmp$ groups
enrico dialout cdrom floppy audio video plugdev users fuse sambashare
netdev kvm
Does that seem ok?
Do I need to be member of any other groups? Maybe "polkituser" or
something?
What else could be wrong/different?
Yves-Alexis Perez
> >I hope it'll fix your problem. If it does, we'll add a recommends on
> >xfce4-session for this one.
>
> It did for me, sort of.
>
> After installing libpam-ck-connector, ck-list-sessions actually
> recognises the session and prints it.
Ok.
>
> But with a plain PolicyKit.conf I still couldn't shutdown/reboot my
> system. I had to uncomment the content of the posted PolicyKit.conf to
> get it working. After that, polkit-auth listed the shutdown and reboot
> actions and shutting down the system from Xfce actually worked.
That's weird. But anyway it's a policykit problem. And btw I think you
changed something, because it does work out of the box on all machines I
tried.
>
> Why did the *kit guys make things so complicated?
Yeah, I'm wondering too :/
>
> The remaining questions are:
> - Shouldn't it work a bit more out of the box, also for users without
> any fancy display manager?
It does, if you install libpam-ck-connector, which we will add as a
Recommends to xfce4-session.
> - Is it worth forwarding this bug to the consolekit/policykit packages
> to get some more input?
If you want, you can clone the bug and reassign to the package owning
the PolicyKit.conf package you had to tune.
Cheers,
--
Yves-Alexis
Yves-Alexis Perez
> On Tue,28.Apr.09, 20:18:07, Andrei Popescu wrote:
>
> > $ dpkg -l libpam-ck-connector | grep ^ii
> > ii libpam-ck-connector 0.3.0-2 ConsoleKit PAM module
>
> Hello again,
>
> As per the information in #525945 and #526009 I *purged*
> libpam-ck-connector and now restart works with gdm and startx, but not
> with startxfce4.
You should be able to still use startxfce4 by using:
exec startxfce4
in .xsession, and not use any .xinitrc. Then, just run startx and you
should have
1) consolekit correctly setup
2) all stuff provided by startxfce4 (mainly this is the xscreensaver
stuff) running
In the end, I don't think we'll add the pam module to Recommends: of
xfce4-session.
xfce4-session already Recommends: hal, which depends on consolekit,
which Recommends: the libpam-ck-connector.
We will document the various ways to start Xfce in the xfce4-utils
README.Debian (see #526009 for more info), but I don't think we should
add anything more to xfce4-session.
What do you think?
--
Yves-Alexis
Andrei Popescu
> > As per the information in #525945 and #526009 I *purged*
> > libpam-ck-connector and now restart works with gdm and startx, but not
> > with startxfce4.
>
> You should be able to still use startxfce4 by using:
> exec startxfce4
>
> in .xsession, and not use any .xinitrc. Then, just run startx and you
> should have
> 1) consolekit correctly setup
> 2) all stuff provided by startxfce4 (mainly this is the xscreensaver
> stuff) running
> In the end, I don't think we'll add the pam module to Recommends: of
> xfce4-session.
> xfce4-session already Recommends: hal, which depends on consolekit,
> which Recommends: the libpam-ck-connector.
>
> We will document the various ways to start Xfce in the xfce4-utils
> README.Debian (see #526009 for more info), but I don't think we should
> add anything more to xfce4-session.
>
> What do you think?
AFAICT the default configuration shutdown does not work at all. One has
to either purge libpam-ck-connector (which is pulled in by consolekit)
or edit one's .xsession and even then, only startx will work, not gdm or
startxfce4. That means xfce4 users are actually better of just purging
libpam-ck-connector, with 2 out of 3 default start methods working.
IMHO the default configuration should just work, so (I'm just guessing)
xfce4-session needs to somehow use libpam-ck-connector to correctly
register the session with consolekit.
How are other session managers doing it?
Regards,
Yves-Alexis Perez
> AFAICT the default configuration shutdown does not work at all.
That's wrong :)
> One has
> to either purge libpam-ck-connector (which is pulled in by consolekit)
> or edit one's .xsession and even then, only startx will work,
On this point you're right. We _will_ have to advertise that the correct
way to run Xfce from console is to use startx only, with exec startxfce4
on .xsession. But people can still do otherwise, they just won't have
all the Debian bits.
> not gdm or
It works fine from gdm, wether or not you have libpam-ck-connector,
because:
- gdm talks directly to CK
- (and that's a problem by itself) 90consolekit won't run if
libpam-ck-connector has already run a CK session
> startxfce4.
Yes. I mean, this will work, but only providing the Xfce bits, not the
Debian bits. And yes, CK (as well as gpg-agent and stuff like that)
belongs to Debian. Upstream might want to tune their startxfce4 (I mean
the /etc/xdg/xfce4/xinitrc, in fact) to add CK support, but I'm not
convinced it's a good idea anyway.
> That means xfce4 users are actually better of just purging
> libpam-ck-connector, with 2 out of 3 default start methods working.
No, it'll work fine from GDM and KDM (the “CK-enabled” DM). I didn't
test yet but I think it won't work from slim or console, but that's a
problem in consolekit which I've commented on there.
>
> IMHO the default configuration should just work, so (I'm just guessing)
> xfce4-session needs to somehow use libpam-ck-connector to correctly
> register the session with consolekit.
No. xfce4-session has nothing to do with libpam-ck-connector.
> How are other session managers doing it?
GNOME/KDE people use CK-enabled DM. Not sure about LXDE. Other people
might just be bitten as we are. Or not use ck/pk/hal for shutdown or
device management.
Cheers,
--
Yves-Alexis