[Pkg-utopia-maintainers] Bug#520720: Bug#520720: gnome-power-manager: Stopped working after consolekit upgrade)
corsac at debian.org
Wed Apr 29 05:51:06 UTC 2009
On ven, 2009-04-24 at 17:43 +0200, Michael Biebl wrote:
I'm jumping on this issue because we have the same kind of problems.
90consolekit “ignore” when libpam-connector is enabled bites us at Xfce
because quite a lot of people will use console to login.
> > Alternatively, what do you think about having 90consolekit test for
> > well-known environment variables rather than XDG_SESSION_COOKIE? I see
> > that GDM sets GDMSESSION... if the other consolekit-using display
> > managers set other variables, the script could test for the existence of
> > any of them.
> Hm, do you know such a list of environemnt variables.
> I think GNOME uses GNOMERC.
> Problem is, we have a lot of window managers / desktop environments in
> Debian ;-)
Yeah, the list would be hard to maintain. And yes it's not really the
> > I guess it would be better for all the ConsoleKit-using display managers
> > to, if they insist on not relying on libpam-ck-connector, to set a
> > common environment variable that the script can test for.
I aggree. I mean, libpam-ck-connector should _only_ sets the variable if
it's indeed an XDG_SESSION. I mean, only if the user logged in through a
CK-enabled DM. (I didn't yet test with slim and libpam-ck-connector
activated but I guess it won't work either). Those are the problematic
ones. I don't know if libpam-ck-connector can detect that they already
have a CK session, but that would make a lot more sense.
And if it's not possible, is that really grave to have a stale CK
session from the pam module?
-------------- 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-utopia-maintainers