Bug 979049
Summary: | tree twisties in evo's tree view stop working after clicking GtkStatusIcon | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Tomas Pelka <tpelka> |
Component: | gtk2 | Assignee: | Benjamin Otte <otte> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.5 | CC: | fidencio, jkoten, mcrha |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gtk2-2.20.1-4.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 05:29:14 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
Tomas Pelka
2013-06-27 13:40:18 UTC
This is a GTK+ issue: https://bugzilla.gnome.org/show_bug.cgi?id=581050 Something to do with the interaction between GtkStatusIcon and GtkTreeView. Never got fully investigated by GTK+ maintainers. We stopped using GtkStatusIcon about the time we ported to gtk3 and the problem went away on its own. I tested the proposed upstream patch and indeed, it fixes the issue. I suggest to include the patch into the gtk2 update. The patch has landed in GTK2 upstream, so it should be fine to include: commit b32a9eb691920f21ad3b9127c833aaba15727c4b Author: Michael Natterer <mitch> Date: Thu May 31 11:02:09 2012 +0200 GtkTreeView: make tree expanding/collapsing more robust gtk_grab_remove() *after* we did the expanding/collapsing, otherwise grab_notify() might kick in and mess with our state. Fixes bug #675835. gtk/gtktreeview.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Thanks Benjamin, I'm committing this to sources. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1544.html |