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~trusty2 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! -- 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 : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp