Bug 1148202

Summary: Xwayland gtk2: menu items are not accessible by mouse
Product: [Fedora] Fedora Reporter: Christian Stadelmann <fedora>
Component: waylandAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: ajax, enaut.w
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-16 21:43:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christian Stadelmann 2014-09-30 23:15:33 UTC
Description of problem:
It seems like all (or at least most) gtk2 applications have problems with mouse interaction with menus. 

Version-Release number of selected component (if applicable):
F21 Alpha

How reproducible:
always for geany (for both context menus and menu bar), sealert (has only context menu), libreoffice (both).
never for:firefox (gtk2), evolution (menus, mail list, calendar, …) , vlc, Konsole, nautilus
menu works, context menu doesn't for: gnome-terminal, roxterm (gtk3), evolution email view

Steps to Reproduce:
1. Open menu or context menu
2. try mouse interaction with menu

Actual results:
menu does not respond to mouse. Menu items don't get highlighted when hovering on them. Clicking on a menu item does not trigger any action but hides the menu. It seems like mouse position is incorrectly handled.

Expected results:
Menu items should get highlighted when hovering and actions should be triggered when clicking the menu.



Additional info:
This seems to be affect only gtk2 apps but not gtk3 or qt-based apps.

Comment 1 Dietrich 2014-10-02 09:24:23 UTC
*** Bug 1148020 has been marked as a duplicate of this bug. ***

Comment 2 Christian Stadelmann 2014-10-16 21:43:32 UTC
This bug is fixed in gnome 3.14.1 release.