doesn't switch to graphical VT when auto login is turned on, (multiseat)

[shawnlandden]

I have a working multiseat system with the 2nd seat Displaylink-based USB touchscreen.

the 2nd seat auto-logs in fine, and the first seat (AMD) comes up fine to lightdm.

If i set autologinup, then the 2nd seat starts fine, but the first seat is blank until i

ctrl-alt-f7

at which it logs in.

is it this in my Xorg, does it need to VT switch agressively like lightdm usually does, or is it this in my Xorg:

Section "ServerLayout"
  Option "AllowEmptyInput" "true"
EndSection

[shawnlandden (shawnlandden)]

precise

[shawnlandden (shawnlandden)]

this problem seems to be more general, so making title fit that

[Launchpad Janitor (janitor)]

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

[Felix (signor-rossi)]

Finally switched to xdm and the first login screen was shown.

Tried numerous things, which all did not work:
- Kernel parameter: nomodeset (Display did not come up at all)
- Kernel parameter: acpi=off nolapic noapic
- Blacklisting Framebuffer-Driver in "/etc/modprobe.d/blacklist-framebuffer.conf"
- Added 'Option "VGAAccess" "true/false"' in xorg_seat0.conf
- Added vt7 ond or -isolateDevice to X command in lightdm.conf
- Changed minimum-vt to 8 or higher in lightdm.conf
- Added 'chvt 7' to display-setup-script

Spent lots on hours on that... xdm is not very cute, but works. Current gdm is told not to support multiseat. kdm was no choice for me, because there is no other kde-stuff on that system. May be lxdm is an alternative until this bug is fixed.

[ELIPTUS (eliptus+launchpad)]

This issue appears to be timing related. I was able to work around it by adding "display-setup-script=sleep 10" to the first seat.

[shawnlandden (shawnlandden)]

actually i remember working around this with -sharevts and -novtswitch to Xorg

after working around it does the other seat work? do they both work at the same time?

[ELIPTUS (eliptus+launchpad)]

I already had -sharevts and -novtswitch in the X command-line and still saw the issue.

Yes, with this workaround, both seats work for me.

[shawnlandden (shawnlandden)]

Hmm, cause i eventually got both seats to auto-login and work. I guess i'll go look at my config and report back.

[ELIPTUS (eliptus+launchpad)]

Regarding my workaround, it appears to work for the initial launch, but not if I attempt to restart X.

[Felix (signor-rossi)]

I disabled tty2 to tty6 by removing /etc/init/tty[2-6].conf (or rename to *.bak).
Additionally I replaced getty with fgetty.
apt-get install fgetty
Changed "exec /sbin/getty -8 38400 tty1" to "exec /sbin/fgetty tty1" in /etc/init/tty1.conf

No lightdm brings up a login-screen on the first seat without the need to press CTRL-ALT-F7

[Felix (signor-rossi)]

Seems it was a random issue. After a further reboot, the problem came up again. On another machine with two seats the problem disapears reliabally when I add "minimum-vt=10" to /etc/lightdm/lightdm.conf. But this workarround does not work on the other machine...
Attached you see my config.

[Anthony (craigslistamc)]

This affected me while i had seat0 as auto-login. Seat1 would get lightdm greeter and seat0 would require ctrl+alt+F7
I switched it to seat1 being auto-login and now there is no need to do that. I updated the MultiseatX page using my setup as an example. The relevant files can be found there.

[Richard Hansen (rhansen)]

This is because LightDM assigns each seat a different virtual terminal, and switches to that virtual terminal whenever X is (re)started.

I have some changes to LightDM in progress to add more complete multiseat support. If you are using Ubuntu, please try installing the version of LightDM in my PPA (<https://launchpad.net/~a7x/+archive/multiseat>):

    sudo apt-add-repository ppa:a7x/multiseat
    sudo apt-get update
    sudo apt-get upgrade

More complete instructions can be found by visiting the PPA page.