Bug 4322 - two mouse pointers in wayland on qemu
Summary: two mouse pointers in wayland on qemu
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: graphics (show other bugs)
Version: 1.4
Hardware: Other Multiple
: Low normal
Target Milestone: Future
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-04-16 16:08 UTC by Alexandru Georgescu
Modified: 2018-04-10 16:35 UTC (History)
6 users (show)

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

Attachments
2 pointers (3.03 MB, image/jpeg)
2013-04-16 16:08 UTC, Alexandru Georgescu 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Georgescu 2013-04-16 16:08:39 UTC 
Created attachment 1177 [details]
2 pointers

poky dylan dab237bc6a7679dfeaa981c14736aedc7b04ecb9


STEPS TO REPRODUCE
1. Build a core-image-sato with Wayland (qemux86-64)
2. Boot it  and start Weston compositor
3. Play with the mouse

EXPECTED RESULTS
3. Only 1 pointer is displayed

ACTUAL RESULTS
3. There are 2 pointers displayed (one from Host and one from the virtual machine).


see screenshot for exemplification.
Comment 1 Ross Burton 2013-04-17 08:23:57 UTC 
Presumably because Sato-in-Qemu is configured with the input device as a touch panel, and an invisible X cursor (strictly speaking a point theme with no image content, not hidden in the XFixes sense).  With this the host pointer works as expected.

Then you run a nested Weston.  This tells X to hide it's cursor (which is already hidden) and draws it's own.  At no point was Qemu told to hide it's own cursor.
Comment 2 Ross Burton 2013-04-17 08:26:43 UTC 
Slight correction - mbwm does use XFixes instead of a cursor theme to hide the cursor.
Comment 3 valentin 2014-04-03 14:59:22 UTC 
Moved to 1.5.2
Comment 4 Ross Burton 2018-04-10 16:35:42 UTC 
I'm calling this expected behaviour if you do something unusual.