Bug 1034770 - Gtk-CRITICAL **: IA__gtk_text_tag_table_remove: assertion `tag->table == table' failed
Summary: Gtk-CRITICAL **: IA__gtk_text_tag_table_remove: assertion `tag->table == tabl...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gtk2
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Benjamin Otte
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 13:34 UTC by Tomas Pelka
Modified: 2017-12-06 11:23 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:23:29 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Tomas Pelka 2013-11-26 13:34:23 UTC
Description of problem:
Using gedit raising following gtk critical assertion:

 (gedit:32368): Gtk-CRITICAL **: IA__gtk_text_tag_table_remove: assertion `tag->table == table' failed

Version-Release number of selected component (if applicable):
gtk2-2.20.1-4.el6
gedit-2.28.4-3.el6

How reproducible:
100%

Steps to Reproduce:
1. run gedit
2.
3.

Actual results:
see description

Expected results:


Additional info:
gedit work as expected

Comment 2 Jan Kurik 2017-12-06 11:23:29 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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