Comment 4 for bug 1371250

Hello,

I'm using multiseat under ubuntu lts 16.04

I found a description of what is happening here:
https://lists.launchpad.net/ubuntu-multiseat/msg00505.html

In short, seat-1 lock/switch user doesn't work and generates tons of error logs

[+763003.64s] DEBUG: Launching process 27821: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp
[+763003.69s] DEBUG: Launching process 27822: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp
[+763003.74s] DEBUG: Launching process 27823: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp
[+763003.79s] DEBUG: Launching process 27824: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp
[+763003.84s] DEBUG: Launching process 27825: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp

I configured allow-user-switching=false so that my logs won't fill up.

[Seat:seat-1]
xserver-command=/usr/bin/X :1 -s seat-1
xserver-config=/etc/X11/xorg.conf.nvidia
# This kept constant respawn of X from filling up logs, but only allows one login - greeter fails to start
allow-user-switching=false

Now what happens, just as reported in this bug is that I can start lightdm, and someone can login once to seat-1, but once they log out there is no greeter respawned.

I think this bug should be updated to include Xenial as well.

Anyways I'm sure multiseat is a rare thing but I wanted someone to know it matters to me.

I'm so close to having it work!

Is there anything else I can try to work around?

I see the question above:

"Should we adopt the following solution for this bug?"

I vote yes to that.

Thanks.