Comment 31 for bug 1209008

I have two discrete cards. So the difference is that your integrated card is probably on the "platform bus", while both of my discrete cards are PCI-E devices.

I started testing multiseat setup described in this thread only last Saturday and since then have always been using the lightdm version which supports automatic multiseat; in one of my posts above (where I thought that the multiseat setup didn't work) I enclosed my full lightdm.conf; it only consisted of logind-load-seats and logind-check-graphical.

# apt-cache policy lightdm
lightdm:
  Zainstalowana: 1.10.4-0ubuntu2 # means: Installed
  Kandydująca: 1.10.4-0ubuntu2 # means: Candidate
  Tabela wersji:
 *** 1.10.4-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     1.10.3-0ubuntu2 0
        500 http://pl.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
     1.10.0-0ubuntu3 0
        500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

The full lightdm.conf I'm using now:

[LightDM]
logind-load-seats=true
logind-check-graphical=true

[SeatDefaults]
allow-guest=false

[Seat:seat-1]
xserver-command=/usr/bin/X -core -dpms -s 0

And with this setup the card assigned to seat0 in xorg.conf wakes up correctly, but the other does not. I'm wandering which step of restarting lightdm does the trick of waking it up fully? Because, as I said before, the seat-1 is not completely lost after wakeup; if I brutally restart lightdm it comes back, of course all graphical sessions terminated and lightdm login screen displayed again at both seats.

My random guess is that the problem is in the X server. Perhaps for waking up there is some code path which works in a similar way to what probing used to work, that is, it only searches for platform display devices?