Bug 8380 - multiple pointer devices in qemu
Summary: multiple pointer devices in qemu
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.2
Assignee: Maxin B. John
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 9365
  Show dependency tree
 
Reported: 2015-09-23 09:04 UTC by Jussi Kukkonen
Modified: 2016-08-26 08:07 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jussi Kukkonen 2015-09-23 09:04:58 UTC
qemu used to disable the emulated mouse when tablet emulation was enabled (as we do with "-usbdevice wacom-tablet"). The documentation still claims this should happen but it seems to have stopped working.

In qemu monitor:
| (qemu) info mice
|   Mouse #2: QEMU PS/2 Mouse
| * Mouse #3: QEMU PenPartner tablet (absolute)

Likewise with xinput_calibrator on target:
| # xinput_calibrator --list
| Device "Wacom Penpartner Pen" id=8
| Device "ImExPS/2 Generic Explorer Mouse" id=9


This seems to lead to a few problems:
* xinput_calibrator shows up on every boot of core-image-sato: it's trying to calibrate the emulated mouse which doesn't make sense to begin with and won't work
* There's a weird delay after booting when the mouse clicks don't do anything for 10 secs or so (could also be unrelated)
Comment 1 Ross Burton 2015-09-23 09:42:24 UTC
Can you look into this further?
Comment 2 Jussi Kukkonen 2015-09-23 10:31:53 UTC
Sure, I'll try.
Comment 3 Jussi Kukkonen 2015-10-06 12:33:23 UTC
First: xinput_calibrator apparently isn't part of any images we test regularly (like I originally thought) so this isn't too critical.


The two pointer devices have probably really been there all the time: the problem is that the emulated PS/2 mouse reports itself as an "absolute coordinate" device in XListInputDevices() and that makes xinput_calibrator rightly think it could be calibrated.
Comment 4 Ross Burton 2015-10-19 16:05:48 UTC
Jussi's investigation shows this to be deeper than expected.  Moving to 2.1.
Comment 5 Jussi Kukkonen 2015-11-18 12:47:51 UTC
I don't think this is medium+ (we already moved it from 2.0 to 2.1 so I think that proves it)
Comment 6 Jussi Kukkonen 2016-05-27 10:57:42 UTC
Note to self and Maxin:
Koens commit on xinput-calibrator recipe means xinput_calibrator_once.sh may now be run from both Xsession.d and autostart -- need to make sure this isn't a problem or fix it.
Comment 7 Maxin B. John 2016-06-15 13:41:38 UTC
Updated the work-around patch and sent it to oe-core ml:

http://lists.openembedded.org/pipermail/openembedded-core/2016-June/122856.html
Comment 9 Maxin B. John 2016-08-26 08:07:32 UTC
In qemu, the emulated PS/2 mouse reports itself as an "absolute coordinate"
device and that makes xinput_calibrator think it could be calibrated.

Add a dummy calibration file as a work around to prevent xinput_calibrator from popping up on every boot in qemu.