|Summary:||Enter/Leave event woes with multiple master devices.|
|Product:||xorg||Reporter:||Peter Hutterer <peter.hutterer>|
|Component:||Server/General||Assignee:||Peter Hutterer <peter.hutterer>|
|Status:||RESOLVED WONTFIX||QA Contact:||Xorg Project Team <xorg-team>|
|i915 platform:||i915 features:|
|Bug Depends on:|
Description Peter Hutterer 2010-04-22 20:39:22 UTC
Fedora bug 538482 <https://bugzilla.redhat.com/show_bug.cgi?id=538482> Quoting Jason Woofenden: If you create a second mouse pointer (xinput --create-master), and leave this extra pointer in the wrong place, you can't use the gnome panel menus anymore. Steps to Reproduce: 1. xinput --create-master foo; xinput --reattach ... (to make a 2nd mouse pointer you can move around) 2. Move the extra mouse pointer (the one you will leave alone in the next step) so it is over the area where sub-menus of the application menu appear (so about one inch down and three inches rightward from the top,left corner of the screen) 3. Using your main mouse, click the applications menu (which works normally) then mouseover a category, say accessories. The submenu will appear, but you cannot click any of the items in it, and mousover blueness is missing in the submenu. Notice also that you cannot click these items or get the rollover effect with the extra mouse pointer either.
Comment 1 Jeremy Huddleston Sequoia 2011-05-28 17:45:32 UTC
I'd still like to have this in 1.10 if possible. Peter, is this on your short list? Do you expect the changes to be intrusive?
Comment 2 Peter Hutterer 2011-05-29 16:01:37 UTC
it's not on the short list, sorry. This is buggy MPX behaviour on legacy clients. Buggy yes, but already a case where it's hard to do the right thing to begin with since we're emulating a single device with multiple devices.
Comment 3 Keith Packard 2011-08-15 15:46:28 UTC
This doesn't seem to be a 1.11 release blocker to me; is there some reason it was added to this list? It's not a regression from previous behaviour.
Comment 4 Jeremy Huddleston Sequoia 2011-08-15 17:38:14 UTC
It's in the 1.11 tracker because I bumped it out of the 1.10 tracker. This has been around for a while, and it certainly shouldn't block 1.11.
Comment 5 Peter Hutterer 2016-11-28 04:39:47 UTC
This is a mass change of bugs. Bugs assigned to me that haven't been updated in the last 3 years are closed as WONTFIX, because, well, let's at least be honest about it. Please do not re-open unless you have a really good reason to do so (e.g. you're fixing it yourself). If it hasn't been fixed in the last 3 years, it probably won't be fixed anytime soon either. Sorry.