| Summary: | multiple pointer devices in qemu | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Jussi Kukkonen <jku> |
| Component: | core | Assignee: | Maxin B. John <maxin.john> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, ross.burton |
| Version: | unspecified | ||
| Target Milestone: | 2.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | |||
| Bug Blocks: | 9365 | ||
|
Description
Jussi Kukkonen
2015-09-23 09:04:58 UTC
Can you look into this further? Sure, I'll try. 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. Jussi's investigation shows this to be deeper than expected. Moving to 2.1. I don't think this is medium+ (we already moved it from 2.0 to 2.1 so I think that proves it) 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. Updated the work-around patch and sent it to oe-core ml: http://lists.openembedded.org/pipermail/openembedded-core/2016-June/122856.html 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. |