[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2017-02-02 Thread Brian Murray 
** 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-xenial (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: xorg-server-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: xorg-server (Ubuntu Trusty)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-xenial package in Ubuntu:
  Invalid
Status in xorg-server source package in Trusty:
  Invalid
Status in xorg-server-lts-xenial source package in Trusty:
  Fix Committed
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server-lts-xenial source package in Xenial:
  Invalid
Status in xorg-server source package in Yakkety:
  Fix Released
Status in xorg-server-lts-xenial source package in Yakkety:
  Invalid

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2017-02-02 Thread Brian Murray 
** 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 Desktop
Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-xenial package in Ubuntu:
  Invalid
Status in xorg-server source package in Trusty:
  Invalid
Status in xorg-server-lts-xenial source package in Trusty:
  Fix Committed
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server-lts-xenial source package in Xenial:
  Invalid
Status in xorg-server source package in Yakkety:
  Fix Released
Status in xorg-server-lts-xenial source package in Yakkety:
  Invalid

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2017-01-10 Thread Chris Halse Rogers 
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 by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-24 Thread Timo Aaltonen 
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-18 Thread Launchpad Bug Tracker 
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

** Changed in: xorg-server (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-18 Thread Martin Pitt 
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-18 Thread Launchpad Bug Tracker 
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

** Changed in: xorg-server (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-10 Thread Brian Murray 
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Committed
Status in xorg-server source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-04 Thread Kai-Heng Feng 
** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Committed
Status in xorg-server source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-02 Thread Chris Halse Rogers 
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.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: xorg-server (Ubuntu Yakkety)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Committed
Status in xorg-server source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-01 Thread Timo Aaltonen 
** 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 
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 here), modesetting driver uses different scheme of output names
  to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
- output's name scheme."
+ output's name scheme.
  
  From a reviewed upstream patch:
  
  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."
  
  so we need to backport that to zesty/yakkety/xenial.
+ 
+ [Test Case]
+ Enable dGPU, test that output to DP works.
+ 
+ [Regression Potential]
+ There should be none, as this leftover was a simple mistake that shouldn't be 
there.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  New
Status in xorg-server source package in Yakkety:
  New

Bug description:
  [Impact]
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme.

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

  [Test Case]
  Enable dGPU, test that output to DP works.

  [Regression Potential]
  There should be none, as this leftover was a simple mistake that shouldn't be 
there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-10-31 Thread Anthony Wong 
** Tags added: originate-from-1626412 somerville

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  New
Status in xorg-server source package in Yakkety:
  New

Bug description:
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme."

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-10-28 Thread Launchpad Bug Tracker 
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

** Changed in: xorg-server (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  New
Status in xorg-server source package in Yakkety:
  New

Bug description:
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme."

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1636397] Re: Fix modesetting slave output names

2016-10-25 Thread Timo Aaltonen 
** 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 here), modesetting driver uses different scheme of output names
  to avoid kind of confusion we are seeing here. There is a bug in
- moesetting X-driver gets shipped with X-server, which disables slave
+ modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme."
  
  From a reviewed upstream patch:
  
  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."
  
  so we need to backport that to zesty/yakkety/xenial.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1636397

Title:
  Fix modesetting slave output names

Status in xorg-server package in Ubuntu:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server source package in Yakkety:
  New

Bug description:
  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 here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme."

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1636397/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp