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:
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.
There appears to be a problem with the DisplayConfigur ation:: power_mode flag in Mir.
I've added debug logging inside ms::MediatingDi splayChanger: :update_ input_rectangle s 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. pastebin. ubuntu. com/16393164/
http://
Instead need to figure out why the power mode is being incorrectly determined when Mir reconfigures displays on unity8 connect.