There appears to be a problem with the DisplayConfiguration::power_mode flag in Mir.
I've added debug logging inside ms::MediatingDisplayChanger::update_input_rectangles to print the display configuration state. At startup, once unity8 starts, I see this output from USC: http://pastebin.ubuntu.com/16393116/ The power modes are wrong, which causes Mir to think the virtual display's geometry should be included in the input region. This patch is a quick fix, but not the correct one. http://pastebin.ubuntu.com/16393164/ Instead need to figure out why the power mode is being incorrectly determined when Mir reconfigures displays on unity8 connect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1580774 Title: mouse is getting stuck on a phantom edge Status in Canonical System Image: In Progress Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Incomplete Status in unity-system-compositor package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: frieza build 101/rc-proposed Steps: 1. connect mouse & keyboard to M10 2. launch xchat 3. go full screen 4. mouse move around across the entirety of the screen (landscape) expected: mouse can range over entire screen actual: gets stuck moving right note: i noticed it happening on xchat, but when changing focus to dash it was also continuing to happen So, i kinda suspect this may be related to rotation maybe. I do admit i did the full OOBE in portrait mode Problem is also persisting across reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580774/+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
