Consolekit session not active

Bug #584855 reported by Olaf Leidinger
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: upstart

Ubuntu Lucid Lynx, i386, all updates installed, starting from a fresh install.

The system seems to boot normally, but the splash screen is not shown and there is no drum sound in gdm.
When switching to the console, there is __no__ login screen.
Logging in using gdm, there is no login sound either and usb sticks can't be mounted, as the user is "not authorized".
The reason for the behaviour after login seems to be console-kit:

$ ck-list-sessions
Session2:
 unix-user = '1000'
 realname = '****'
 seat = 'Seat1'
 session-type = ''
 active = FALSE
 x11-display = ':0'
 x11-display-device = '/dev/tty7'
 display-device = ''
 remote-host-name = ''
 is-local = TRUE
 on-since = '2010-05-24T08:20:08.353095Z'
 login-session-id = ''

The session is not active!

I found it curious, that there was no terminal login prompt, so I tried to figure out, how to debug upstart. Therefore I inserted the option "--debug" into grub.conf (for the record: via /etc/default/grub) et voilà: the system boots up normally (except for all the debug messages).

I assume, that the problem occurred via update, as I updated the system yesterday, after installing it and the problem occurred this morning. It seems to be somehow tied to this machine, which isn't mine. As before yesterday's reinstall, there was also a fresh install of 10.4 on this machine and it had in retrospect the same problem.

Description: Ubuntu 10.04 LTS
Release: 10.04

Revision history for this message
Olaf Leidinger (leidola) wrote :
Revision history for this message
Olaf Leidinger (leidola) wrote :

So summarized: Something seems to get stuck in the boot process on this system, when not using --debug for upstart.
What's the best way to tackle the problem?

Revision history for this message
Olaf Leidinger (leidola) wrote :

I think this one is related to #554172. As recommended there I did the following:

 - add --verbose to kernel commandline
 - recorded boot.log with and without --debug
 - recorded the output of initctl list with and without --debug
 - noted the runlevel for both cases

By the way. It seems as if the problems described above occur, even if --debug is present, but much less frequent.

Revision history for this message
Olaf Leidinger (leidola) wrote :
Revision history for this message
Olaf Leidinger (leidola) wrote :
Revision history for this message
Olaf Leidinger (leidola) wrote :
Revision history for this message
Olaf Leidinger (leidola) wrote :

And finally the runlevel:
  - failing case: unknown
  - working case: N 2

Is this some race condition?

Revision history for this message
Olaf Leidinger (leidola) wrote :

As suggested in bug #554172 I tried to comment out the line

console output

of /etc/init/rc.conf. This also works around the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.