restart-multiple-users policy prevents restart, even though no other users are logged in

[Forest]

I just upgraded from xubuntu natty to oneiric and switched from gdm to lightdm.

Now, when I try to restart my system, I am prompted for my password by a dialog box with this message:

  System policy prevents restarting the system when other users are logged in

Under the Details widget, I see this:

  org.freedesktop.consolekit.system.restart-multiple-users

I guess this would all be fine if other users actually were logged in to the system, but there are none. My login (through lightdm) is the only one.

[Forest (foresto)]

Further investigation reveals that the system seems to think that no users are logged in. Not even me.

$ who
$ uptime
 11:00:40 up 21 min, 0 users, load average: 0.89, 0.89, 0.70
$ who -q
# users=0
$ last |head -1
reboot system boot 3.0.0-13-generic Sat Nov 26 10:39 - 11:17 (00:38)

Could it be that, when a restart is requested, whatever code checks for multiple users is doing something like if (usercount != 1), which would evaluate to true if multiple users are logged in *or* if no users are logged in? If so, perhaps this is related to Bug #871070

[Forest (foresto)]

May also be related to bug #870297.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you get a "ck-list-sessions" log when getting the issue?

[Forest (foresto)]

$ ck-list-sessions
Session4:
        unix-user = '120'
        realname = 'RabbitMQ messaging server'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/???'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2012-01-06T17:27:13.153273Z'
        login-session-id = ''
Session5:
        unix-user = '1000'
        realname = 'Forest'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':0'
        x11-display-device = '/dev/tty7'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2012-01-06T17:27:51.421367Z'
        login-session-id = ''

Interesting. So is this rabbitmq's fault for creating a console session, or lightdm's or consolekit's fault for treating it like a user session?