** Changed in: xorg-server-lts-xenial (Ubuntu Xenial)
Status: New => Invalid
** Changed in: xorg-server-lts-xenial (Ubuntu Yakkety)
Status: New => Invalid
** Also affects: xorg-server (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xorg-server-lts-xenia
** Also affects: xorg-server-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-lts-xenial (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hello Timo, or anyone else affected,
Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then
in the -proposed repository.
Please help us b
yakkety has this, close HWE next task
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636397
Title:
Fix modesetting slave output names
To
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu6.1
---
xorg-server (2:1.18.4-1ubuntu6.1) yakkety; urgency=medium
* modesetting-unifdef-slave-support.diff: Fix modesetting slave output
names. (LP: #1636397)
-- Timo Aaltonen Tue, 01 Nov 2016 10:06:42 +0200
**
unity8 tests have always been brittle; the autopilot ones (which use X)
succeeded, while the QML ones (which don't use X) didn't, so this
appears unrelated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This bug was fixed in the package xorg-server - 2:1.18.4-0ubuntu0.2
---
xorg-server (2:1.18.4-0ubuntu0.2) xenial; urgency=medium
* modesetting-unifdef-slave-support.diff: Fix modesetting slave output
names. (LP: #1636397)
-- Timo Aaltonen Tue, 01 Nov 2016 10:08:51 +0200
**
This seems to have caused a regression with the unity8 test:
http://autopkgtest.ubuntu.com/packages/u/unity8/xenial/i386
Could someone have a look at this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636397
Title:
Fix modesetting slave output names
To manage notifications about t
Hello Timo, or anyone else affected,
Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
** Description changed:
- From a private bug:
- "Currently, NVIDIA and modesetting drivers are using same output names, that
creates confusion for xrandr clients like gnome-setting-daemon or xrandr
utility.
+ [Impact]
+ Currently, NVIDIA and modesetting drivers are using same output names, that
** Tags added: originate-from-1626412 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636397
Title:
Fix modesetting slave output names
To manage notifications about this bug go to:
https:
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu7
---
xorg-server (2:1.18.4-1ubuntu7) zesty; urgency=medium
* modesetting-unifdef-slave-support.diff: Fix modesetting slave output
names. (LP: #1636397)
-- Timo Aaltonen Tue, 25 Oct 2016 10:48:45 +0300
** Chang
** Description changed:
From a private bug:
"Currently, NVIDIA and modesetting drivers are using same output names, that
creates confusion for xrandr clients like gnome-setting-daemon or xrandr
utility.
When modesetting outputs act as slave for other x-screen (like NVIDIA
X-screen her
14 matches
Mail list logo
