Interestingly, bug 1517133 shows this issue existed before the switch to libinput. So the bug has remained consistent with both android-input and libinput backends in Mir. And the switch to libinput made no visible difference.
I have a theory that the relative motion data Unity8 is receiving might be incomplete. Because it's a nested server and subject to input resampling, meaning it will only get input events at 59Hz. It's possible we don't have sufficient logic to merge the relative motion data accurately before it's delivered to Unity8 at the lower rate. ** Summary changed: - Mouse cursor moves way too slow in Unity 8 with a 1000Hz mouse + Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539009 Title: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1539009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
