Actually, I think #478274 is a different issue, and it looks like my issue has been (mostly) fixed in Karmic.
In Jaunty, if I logged in at a text console, 'ck-list-sessions' would show "active = FALSE" for the session associated with the active text console. It would only ever show "active = TRUE" if the login occurred via GDM or another graphical login manager, and this was the problem I was reporting (although, at the time, I clearly thought that 'active' was supposed to be a static flag set at session creation, not a dynamic flag that changed whenever the active console changed). In Karmic, it now shows "active = TRUE" for the active console, whether it is a graphical or text console, so that problem is solved. However, I still have a problem where if I log in via a text console, then run 'startx', I get "active = FALSE" if I run 'ck-list-sessions' within X. This is because the display device associated with my current session (/dev/tty1) does not match the active display device (/dev/tty7 for X). This can be easily worked around by editing /etc/X11/Xsession.d/90consolekit and changing if [ -z "$XDG_SESSION_COOKIE" ] && [ -x "$CK_LAUNCH_SESSION" ]; then to if [ -x "$CK_LAUNCH_SESSION" ]; then which causes a new ConsoleKit session to be created (with the correct display device) when I run 'startx'. If using a graphical login manager, this change may (or may not? I don't really know) cause two ConsoleKit sessions to be created for each X session, so perhaps the if statement should be changed to something like the following? if [ "`ck-list-sessions | grep tty7`" == ""] && [ -x "$CK_LAUNCH_SESSION" ]; then This should prevent duplicate sessions if GDM creates a session with device tty7, but should allow the session to be created when running 'startx' from a text console. David: as for your problem, all of my local sessions show up under 'Seat1', so I suspect that is your problem. However, I have no clue why your sessions don't end up in the right seat. All of my machines were installed ages ago and have been updated through several releases, so this isn't necessarily just an updated-vs-fresh-install problem... -- ConsoleKit sets active=FALSE for non-graphical logins https://bugs.launchpad.net/bugs/363568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
