[Pkg-xfce-devel] Bug#525909: shutdown with hal not working
andreimpopescu at gmail.com
Wed Apr 29 06:01:37 UTC 2009
On Tue,28.Apr.09, 22:40:05, Yves-Alexis Perez wrote:
> > 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
This works for startx with libpam-ck-connector installed.
> In the end, I don't think we'll add the pam module to Recommends: of
> 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?
If you can't explain it simply, you don't understand it well enough.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
More information about the Pkg-xfce-devel