Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1160219 - gtk3-3.14 : irregular appearance with systray menu of GTK3 applets
Summary: gtk3-3.14 : irregular appearance with systray menu of GTK3 applets
Keywords:
Status: CLOSED DUPLICATE of bug 1149335
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 21
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-04 11:14 UTC by Wolfgang Ulbrich
Modified: 2014-11-10 22:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-10 21:18:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Wolfgang Ulbrich 2014-11-04 11:14:21 UTC
Description of problem:
Left click on the icon - menu doesn't stay open, must hold down the left mice button.

Version-Release number of selected component (if applicable):
gtk3-3.14.4-1

How reproducible:
Use any other desktop than gnome and try to open the context menu of an GTK3 applet in systray, ie. with nm-applet, firewalld-applet, gnote......simply all.
Affected desktops:
mate, xfce, lxde


Additional info:
This bug was implemented by this commit.
https://git.gnome.org/browse/gtk+/commit/?id=6b7b55
https://bugzilla.gnome.org/show_bug.cgi?id=736702#c1

Comment 1 Wolfgang Ulbrich 2014-11-04 11:15:19 UTC
*** Bug 1149335 has been marked as a duplicate of this bug. ***

Comment 2 Wolfgang Ulbrich 2014-11-04 11:34:27 UTC
It happens also in cinnamon with ie. gnote applet.

Comment 3 Wolfgang Ulbrich 2014-11-10 21:18:07 UTC

*** This bug has been marked as a duplicate of bug 1149335 ***


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