Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Could not determine active console Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 2 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 2 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 2 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 6 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 6 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 6 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 3 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 15 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 8 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 19 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 12 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 12 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 12 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 14 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 14 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 14 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 16 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 16 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 16 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 18 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 18 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 18 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 20 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 20 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 20 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 3 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 3 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 7 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 7 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: Error waiting for native console 7 activation: Invalid argument Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 4 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 4 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 9 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 9 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 26 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 29 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 30 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 30 returned -1 Aug 22 13:31:14 laptop console-kit-daemon[1108]: WARNING: VT_WAITACTIVE for vt 19 returned -1
Eventually they all return -1 and say error waiting for native console. Luckily I still had the GDM debug on, so it logged this a second later: Aug 22 13:31:15 laptop gdm-simple-slave[1210]: DEBUG(+): GdmServer: Starting X server process: /usr/bin/X :0 -nr -verbose -auth /var/run/gdm /auth-for-gdm-f4pe6Q/database -nolisten tcp vt7 Seems quiet clear to me. When things do not fail, one thread may eventually say: Aug 22 13:29:45 laptop console-kit-daemon[1088]: WARNING: VT_WAITACTIVE for vt 7 returned 0 I don't understand why it would say vt 1 after that: Aug 22 13:30:28 laptop console-kit-daemon[1133]: WARNING: VT_WAITACTIVE for vt 1 But that is just because I'm new to this I guess. :-) The real question is, thus again, is gdm the one initiating the start of consolekit. If so, then gdm is to early to talk to consolekit. Doing some more testing to see where the error in consolekit happends, just for reference. Because I'm still thinking how can I check what initiates the start of consolekit. -- Active VT tracking can fail at startup https://bugs.launchpad.net/bugs/544139 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
