← Back to team overview

desktop-packages team mailing list archive

[Bug 1489696] Re: black screen when enabling rotation on a gpu screen


This bug was fixed in the package xorg-server-lts-vivid -

xorg-server-lts-vivid (2:1.17.1-0ubuntu3.1~trusty1) trusty; urgency=medium

  * Backport vivid package for lts-vivid stack.

xorg-server (2:1.17.1-0ubuntu3.1) vivid; urgency=medium

  * disable-rotation-transform-gpuscreens.patch:
    Revert back to disabling rotations on GPU screens. (LP: #1489696)

 -- Timo Aaltonen <tjaalton@xxxxxxxxxx>  Wed, 02 Sep 2015 16:28:30 +0300

** Changed in: xorg-server-lts-vivid (Ubuntu Trusty)
       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.

  black screen when enabling rotation on a gpu screen

Status in HWE Next:
  In Progress
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-vivid package in Ubuntu:
Status in xorg-server source package in Trusty:
Status in xorg-server-lts-vivid source package in Trusty:
  Fix Released
Status in xorg-server source package in Vivid:
  Fix Committed
Status in xorg-server-lts-vivid source package in Vivid:

Bug description:
  Running with the proprietary nvidia drivers in an optimus config
  works, but enabling reflection or rotation on the intel screen causes
  a black screen to appear.

   * Causes a black screen if rotation or reflection is enabled.

  [Test Case]
   * Run xrandr --output SOMEOUTPUT --rotation left
      - Expected: Screen should rotate, or the call should fail.
      - Bad behavior: Succeeds, but causes a black screen.

  [Regression Potential]
   * The affected codepaths have reflection and rotation disabled for gpu screens. Another fix could be fixing reflection/rotation, but that will be more involved and likely require driver fixes.

  [Other Info]
   * This issue is copied from https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1308515 for vivid and wily.

To manage notifications about this bug go to: