[Pkg-xfce-devel] Bug#526009: Bug#526009: Bug#526009: Bug#526009: Attempt to summarize
corsac at debian.org
Wed Apr 29 05:56:34 UTC 2009
On mer, 2009-04-29 at 00:50 +0100, James Westby wrote:
> On Tue, 2009-04-28 at 23:47 +0200, Yves-Alexis Perez wrote:
> > Ok. I've tested and we have indeed propagation problems. I'm not sure
> > how it's supposed to be handled, but I think it's a bug in consolekit. I
> > don't exactly know how it should be done, but:
> > - either the authentication propagates from console to X
> No, you should end up with two sessions from consolekit's point of view.
Fine, so 90consolekit should run. That's exactly the point of
> > - either the 90consolekit shouldn't prevent ck-launch
> This causes other problems.
> Is startxfce4 called by other things (e.g. GDM), or is it a script that
> the user is expected to use to launch their session similar to startx?
Both. It works fine to use it from GDM, to directly use startxfce4 from
console, to run startx /usr/bin/startxfce4, to put it in .xsession and
> If it's the latter then it should probably be modified to explicitly
> create a consolekit session for the user session it is creating. That
> would fix this issue without leading to multiple sessions for each
I don't want to divert from upstream, and I don't think that's the role
of Xfce initscript to set-up CK. It shouldn't depend on it and that's
why I definitely want Xfce/Debian users to use the Xsessions.d scripts,
because they are installed by the packages themselves, so it'll
automagically work. (except in this case because of the stale CK session
problem, but I started discussing it on #526006 and #520720)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
More information about the Pkg-xfce-devel