Comment 8 for bug 851055

This seems to have broken with the lightdm upgrade. Now, I get 2 consolekit sessions:

chr1s@farnsworth:~$ ck-list-sessions
Session3:
 unix-user = '1000'
 realname = 'Chris Coulson'
 seat = 'Seat1'
 session-type = ''
 active = FALSE
 x11-display = ':0'
 x11-display-device = '/dev/tty7'
 display-device = ''
 remote-host-name = ''
 is-local = TRUE
 on-since = '2011-09-15T21:23:40.636038Z'
 login-session-id = '4294967295'
Session4:
 unix-user = '1000'
 realname = 'Chris Coulson'
 seat = 'Seat1'
 session-type = ''
 active = TRUE
 x11-display = ''
 x11-display-device = ''
 display-device = '/dev/tty7'
 remote-host-name = ''
 is-local = TRUE
 on-since = '2011-09-15T21:23:40.648390Z'
 login-session-id = '4294967295'
 idle-since-hint = '2011-09-15T21:24:11.284720Z'

the inactive session is the one which should be active, so Policykit thinks I'm not on the active console.

Downgrading lightdm to 0.9.5-0ubuntu2 and restarting seems to fix it (I get 1 session, as expected now):

chr1s@farnsworth:~$ ck-list-sessions
Session2:
 unix-user = '1000'
 realname = 'Chris Coulson'
 seat = 'Seat1'
 session-type = ''
 active = TRUE
 x11-display = ':0'
 x11-display-device = '/dev/tty7'
 display-device = ''
 remote-host-name = ''
 is-local = TRUE
 on-since = '2011-09-15T21:40:33.541834Z'
 login-session-id = '4294967295'