← Back to team overview

ubuntu-multiseat team mailing list archive

[Bug 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup

 

It seems to be that the problem occurs after this:

** (lightdm:1153): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0:
Interrupted system call

(The console number depends on luck, of course.)

I would guess that whatever code is emitting that error message is not
handling the situation correctly. In case of "Interrupted system call" I
would guess the correct way to handle the problem is to repeat the
system call. I think the code instead emits this error and proceeds
blindly forward.

-- 
You received this bug notification because you are a member of Ubuntu
Multiseat, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/997483

Title:
  VT_WAITACTIVE does not work well with a multiseat setup

Status in Light Display Manager:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Related to the fix introduced in bug #851612 .

  Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed):
  [+2.97s] DEBUG: New display ready, switching to it
  [+2.97s] DEBUG: Activating VT 8
  [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call
  [+77.56s] DEBUG: Got signal 15 from process 1
  [+77.56s] DEBUG: Caught Terminated signal, shutting down

  And in x-1-greeter.log:
  [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts
  [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001
  [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
  [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached

  On vt7, unity-greeter would get stuck after password input.
  On vt8, unity-greeter appears after that "getting session list timeout", which is about a minute later than vt7, and does not have a password input field.

  lightdm blocked by VT_WAITACTIVE may be the cause...

  Tested with lightdm 1.2.0-0ubuntu2 in precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions