group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #10756
[Bug 1636397] Re: Fix modesetting slave output names
** 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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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