It looks like this is the way upstream ConsoleKit wants it. In order to get an active local session, you must open a session informing stuff like the UID and TTY. ck-launch-session doesn't do that and I find it unlikely that it'll ever do that because, to the best of my knowledge, the way XDM and friends run ck-launch-session, there's no way to gather the required information. In other words, even if ck-launch-session were modified to allow it to launch an active local session, it would still require patching the DMs.
So the solution seems to be patching the DMs. It looks like Mandriva and OpenSUSE already patch XDM: https://bugs.freedesktop.org/show_bug.cgi?id=17325 It also looks like upstream doesn't care much about this patch, which is understandable given that ConsoleKit is a relatively new technology and some important things that depend on it seem specific to Linux. I applied the patches to the Debian package, but ran out of time trying to make the package link because of the new DSO linking rules. I intend to complete it in a few weeks when I get some spare time. So, in short, I believe this won't be fixed in ConsoleKit and we can post bug reports (priority wishlist) against the DMs. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
