[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#791567: marked as done (libwayland-server0: Multiseat configurazione stopped working after libwayland upgrade from 1.7.0-2 to 1.8.1-1)

Your message dated Wed, 20 Apr 2016 22:15:01 +0200
with message-id <5717E345.2080307@debian.org>
and subject line Re: Bug#791567: libwayland-server0: Multiseat configurazione stopped working after libwayland upgrade from 1.7.0-2 to 1.8.1-1
has caused the Debian Bug report #791567,
regarding libwayland-server0: Multiseat configurazione stopped working after libwayland upgrade from 1.7.0-2 to 1.8.1-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
791567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791567
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libwayland-server0
Version: 1.8.1-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.

during an upgrade, libwayland updated from 1.7.0-2 to 1.8.1-1 and systemd/udev
from version 215-17 to
220-7. After that multiseat stopped working.
X server for seat1 is not started.
Using keyboard on seat1 affects seat0. The mouse does not have this behaviour.

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
- search on internet for known bugs or anomalies

I already opened a bug for systemd package and I wrote to systemd list. They
said that systemd just do a list of attached devices on seats. If output of
"loginctl seat-status" is ok it should not be a problem of systemd but
"something between X and gdm". Gdm upgraded from 3.14.1-7 to 3.14.1-8 therefore
should not be the cause.

"something between X and gdm" could be libwayland?

Regards



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwayland-server0 depends on:
ii  libc6    2.19-18
ii  libffi6  3.1-2+b2

libwayland-server0 recommends no packages.

libwayland-server0 suggests no packages.

-- debconf-show failed

--- End Message ---
--- Begin Message --- 
On 06/07/15 12:07, Alberto wrote:
> Package: libwayland-server0
> Version: 1.8.1-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.
> 
> during an upgrade, libwayland updated from 1.7.0-2 to 1.8.1-1 and systemd/udev
> from version 215-17 to
> 220-7. After that multiseat stopped working.
> X server for seat1 is not started.
> Using keyboard on seat1 affects seat0. The mouse does not have this behaviour.
> 
> 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
> - search on internet for known bugs or anomalies
> 
> I already opened a bug for systemd package and I wrote to systemd list. They
> said that systemd just do a list of attached devices on seats. If output of
> "loginctl seat-status" is ok it should not be a problem of systemd but
> "something between X and gdm". Gdm upgraded from 3.14.1-7 to 3.14.1-8 therefore
> should not be the cause.
> 
> "something between X and gdm" could be libwayland?

Definitely not. wayland doesn't do anything on an X session.

I'm closing this. Feel free to reopen if you're still suffering from this, and
we'll look for a package to reassign this to.

Cheers,
Emilio

--- End Message ---
Reply to: