Bug 1148202 - Xwayland gtk2: menu items are not accessible by mouse
Summary: Xwayland gtk2: menu items are not accessible by mouse
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1148020 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-30 23:15 UTC by Christian Stadelmann
Modified: 2014-10-16 21:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-16 21:43:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.