Here are actually three problem at work: * The input device exposed inside the emulator /dev/input/event0 only emit absolute coordinate events. We recently experienced something similar with other incarnation of qemu in kvm: https://bugs.launchpad.net/mir/+bug/1489522 ( in that bug two mouse devices are available, the one that claims to expose relative events never emits them) The actual cause might be in the emulator integration itself. * The input device only emits those event on mouse button down. WIthout pressing a mouse button the evdev device remains silent. Another emulator problem? * The android input stack used in mir does not care about absolute mouse movement events. So even on mouse down it does not handle those events. The upcomig mir will, since it will default to mir-platform-input-evdev. So this will disappear with 0.18
At the moment you can see the mouse moves when you change to the new stack: apt-get update && apt-get install mir-platform-input-evdev3 then edit /usr/share/ubuntu-touch-session/usc-wrapper and add --platform-input-lib /usr/lib/i386-linux-gnu/mir/server-platform/input-evdev.so.3 to the call to unity-system-compositor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517597 Title: Ubuntu-emulator is broken on rc image 3 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517597/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
