touch-packages team mailing list archive

[Daniel d'Andrada <daniel.dandrada@xxxxxxxxxxxxx>]

Mir keeps sending pointer events after it hits a boundary only if you're
using the primary display. If you connect and external monitor, it
doesn't work like that anymore.

Steps to reproduce:
- Flash an N7 and install silo0 in it.
- Add "initctl set-env --global QT_LOGGING_RULES=qtmir.mir.input.debug=true" to /usr/share/upstart/sessions/unity8.conf
- sudo restart lightdm
- in a phablet terminal: tail -f ~/.cache/upstart/unity8.log
- connect a bluetooth mouse and check the output, you should see a lot of entries like "qtmir.mir.input: Received MirPointerEvent(x=971,y=573,relative_x=-1,relative_y=0)"
- see that the mouse goes through the entire screen and you always get mouse events even when the pointer reaches a boundary
- now conenct an external monitor and see what happens

expected outcome:
mouse events keep coming like before

actual outcome:
you have invisible boundaries since mouse events stop coming when the pointer reaches some width and height boundary.

Note that the cursor you see on the screen is drawn by unity8 and it's
driven solely by the relative movement in MirPointerEvents.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1488417

Title:
  nexus4 window mode mouse motion bounded incorrectly

Status in canonical-pocket-desktop:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid

Bug description:
  when connecting a monitor to the Nexus4 during windowed mode, the
  device is put into landscape mode. the mouse motion appears to not
  have followed the orientation and is bounded by roughly portrait width
  instead of landscape width

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1488417/+subscriptions