This appears to have been fixed in Lucid, which provides an updated 90consolekit script similar to the one above, but using a dbus call instead of ck-list-sessions to determine whether a session has already been started.
Using the new Lucid script, I get two Sessions after running X from the command line, as expected:
Session10:
unix-user = '1000'
realname = 'Paul Donohue'
seat = 'Seat1' session-type = ''
active = TRUE
x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '/dev/tty1' remote-host-name = ''
is-local = TRUE
on-since = '2010-04-29T23:17:02.170005Z' login-session-id = '4294967295'
Session3:
unix-user = '1000'
realname = 'Paul Donohue'
seat = 'Seat1' session-type = ''
active = FALSE
x11-display = '' x11-display-device = '' display-device = '/dev/tty1' remote-host-name = ''
is-local = TRUE
on-since = '2010-04-29T23:08:24.154070Z' login-session-id = '4294967295' idle-since-hint = '2010-04-29T23:17:30.017725Z'
Out of curiosity, I tried manually running the dbus commands used in the new script, but I get an error:
/etc/X11/Xsession.d# dbus-send --system --dest=org.freedesktop.ConsoleKit --type=method_call --print-reply --reply-timeout=2000 /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.GetCurrentSession
Error org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '5533'
I'm not sure if I should be concerned about this or not...
This appears to have been fixed in Lucid, which provides an updated 90consolekit script similar to the one above, but using a dbus call instead of ck-list-sessions to determine whether a session has already been started.
Using the new Lucid script, I get two Sessions after running X from the command line, as expected:
session- type = ''
x11-display- device = '/dev/tty8'
display- device = '/dev/tty1'
remote- host-name = '' 29T23:17: 02.170005Z'
login- session- id = '4294967295'
session- type = ''
x11-display- device = ''
display- device = '/dev/tty1'
remote- host-name = '' 29T23:08: 24.154070Z'
login- session- id = '4294967295'
idle-since- hint = '2010-04- 29T23:17: 30.017725Z'
Session10:
unix-user = '1000'
realname = 'Paul Donohue'
seat = 'Seat1'
active = TRUE
x11-display = ':0'
is-local = TRUE
on-since = '2010-04-
Session3:
unix-user = '1000'
realname = 'Paul Donohue'
seat = 'Seat1'
active = FALSE
x11-display = ''
is-local = TRUE
on-since = '2010-04-
Out of curiosity, I tried manually running the dbus commands used in the new script, but I get an error: Xsession. d# dbus-send --system --dest= org.freedesktop .ConsoleKit --type=method_call --print-reply --reply- timeout= 2000 /org/freedeskto p/ConsoleKit/ Manager org.freedesktop .ConsoleKit. Manager. GetCurrentSessi on .ConsoleKit. Manager. GeneralError: Unable to lookup session information for process '5533'
/etc/X11/
Error org.freedesktop
I'm not sure if I should be concerned about this or not...