Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On mer, 2009-04-29 at 09:01 +0300, Andrei Popescu wrote: 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 signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
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. By the way, could you try to run Xfce using: startx /usr/bin/startxfce4 Thanks! -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
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? 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 signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
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 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 signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On Tue, 28 Apr 2009 08:35:24 +0200, Yves-Alexis wrote: 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 copypaste mistake. After cleaning it(attached for reference) up I get: [09:34] enr...@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] enr...@ukio (0): ~/src$ polkit-config-file-validate [09:35] enr...@ukio (0): ~/src$ [09:35] enr...@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). Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc PolicyKit.conf Description: Binary data pgpXW5WKlKPpr.pgp Description: PGP signature
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
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. Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On Tue, 28 Apr 2009 14:09:43 +0200, Yves-Alexis wrote: 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? Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc pgpe986uVA2LD.pgp Description: PGP signature
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On mar, 2009-04-28 at 19:30 +0200, Enrico Tröger wrote: 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 signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On Tue, 28 Apr 2009 20:34:10 +0200, Yves-Alexis wrote: 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] enr...@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? Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc pgpPI6Yl2Euby.pgp Description: PGP signature
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On mar, 2009-04-28 at 20:48 +0300, Andrei Popescu wrote: 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 signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
On lun, 2009-04-27 at 23:12 +0300, Andrei Popescu wrote: 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 signature.asc Description: This is a digitally signed message part
Bug#525909: [Pkg-xfce-devel] Bug#525909: shutdown with hal not working
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. 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 signature.asc Description: This is a digitally signed message part
