Thanks. The logs show Mir knows about the display getting re-enabled and
the backlight coming back on is the only part that Mir is responsible
for. I think the relevant aspects of Mir are working correctly.
** Changed in: mir
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1638929
Title:
after disabling a display, enabling makes screens go black
Status in Canonical System Image:
New
Status in Light Display Manager:
New
Status in Mir:
Invalid
Status in QtMir:
Confirmed
Status in lightdm package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
Reproduce:
turn off then turn on some display (output.used = false then output.used =
true)
What happens:
Turning off works fine, turning it back on does not
What should happen:
it should work as expected
USC log: http://pastebin.ubuntu.com/23420797/
Unity8 log: (see that mirserver: Disabled works fine)
http://pastebin.ubuntu.com/23420803/
Unity8 log (w debug): http://pastebin.ubuntu.com/23451437/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638929/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
