Bug#790743: systemd: Multiseat is not working after upgrade of systemd from 215-17 to 220-7

Alberto Brosich abrosich at ogs.trieste.it
Wed Jul 1 13:54:07 BST 2015


On Wed, 1 Jul 2015 14:29:51 +0200 Michael Biebl <biebl at debian.org>
wrote:
> Control: found -1 220-7
> 
> (you said it is already broken in 220-7, so marking the bug
accordingly)

Sorry, but the version has been recorded automatically by reportbug.

> 
> Am 01.07.2015 um 14:11 schrieb Alberto:
> > Package: systemd
> > Version: 221-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I have a machine with 2 nvidia graphic cards, configured as
multiseat, with 2
> > seats.
> > Debian is version testing (stretch). I use nouveau driver for
nvidia cards.
> > The output of "loginctl seat-status seat1" is normal.
> 
> Can you post the output before and after the upgrade?

Unfortunately I do not have the previous output. The current one is:

seat1
         Devices:
                 
 ├─/sys/devices/pci0000:00/0000:00:07.0/0000:03:00.0/drm/card1
                  │ [MASTER] drm:card1
                  │
├─/sys/devices/pci0000:00/0000:00:07.0/0000:03:00.0/drm/card1/card1-DP
-2
                  │ │ [MASTER] drm:card1-DP-2
                  │
└─/sys/devices/pci0000:00/0000:00:07.0/0000:03:00.0/drm/card1/card1-DVI
-I-2
                  │   [MASTER] drm:card1-DVI-I-2
                 
 ├─/sys/devices/pci0000:00/0000:00:07.0/0000:03:00.0/graphics/fb1
                  │ [MASTER] graphics:fb1 "nouveaufb"
                  └─/sys/devices/pci0000:00/0000:00:1d.1/usb6
                    usb:usb6
                    ├─/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6
-1:1.0/0003:04B3:3025.0003/input/input27
                    │ input:input27 "LITE-ON Technology USB NetVista
Full Width Keyboard."
                    └─/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6
-2:1.0/0003:045E:0040.0004/input/input28
                      input:input28 "Microsoft Microsoft 3-Button Mouse
with IntelliEye(TM)"


> 
> > This Monday, during an upgrade, systemd was updated from version
215-17 to
> > 220-7. After that multiseat stopped working.
> > X server for seat1 is not started.
> 
> I'm not quite familiar how this setup works. Can you describe it in
more
> detail?

Should be quite simple (
http://www.freedesktop.org/wiki/Software/systemd/multiseat/).
You have to create a new seat just attaching to it a graphic device:

loginctl attach seat1
/sys/devices/pci0000:00/0000:00:07.0/0000:03:00.0/drm/card1

etc. (for every device associated to the second graphics card, and for
a keyboard and a mouse)

At the beginning all devices are attached to seat0, that always exixts.
After that you have a new seat (seat1). Restarting gdm (or any other
desktop manager supporting systemd) the new seat should be working.
It is the systemd-logind that do the job.

For example, previously, I attached a specific usb port on the second
seat. Putting a pendisk in that port started the automatic mount on the
second seat, with the correct permissions for the user logged in on
that seat (different from the user on seat0).

> 
> > Using keyboard on seat1 affects seat0. The mouse does not have this
behaviour.
> > Downgrade to 215-17 is a nightmare due too many dependencies.
> > 
> > I tried:
> > - loginctl flush-devices and the loginctl attach to redo multiseat
> > configuration
> > - move of keyboard and mouse on another usb ports
> > - change of desktop manager (from gdm3 to lightdm)
> > - upgrade of systemd to 221-1 from unstable
> > - search on internet for known bugs or anomalies
> 
> This doesn't sound like a downstream integration issue. So it would
be
> great if you can file it upstream at
> https://github.com/systemd/systemd/issues

Ok, I will do it.

> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 




More information about the Pkg-systemd-maintainers mailing list