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
