Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 964831[details]
Nautilus about files backtrace
Description:
Nautilus About Files returns "Gtk-CRITICAL **: gtk_text_buffer_apply_tag: assertion 'tag->priv->table == buffer->priv->tag_table' failed" in terminal
Version-Release number of selected component (if applicable):
nautilus-3.8.2-10.el7.x86_64
Steps to Reproduce:
1. In a terminal window, as a non-root user, run "nautilus."
3. In the upper left portion of the screen, just to the right of Activites in
gnome-shell, click the Files menu.
4. Click "About Files" in this menu.
5. Click the "License" button in the "About Files" dialog.
Actual results:
About files is opened, output in terminal:
(nautilus:30052): Gtk-CRITICAL **: gtk_text_buffer_apply_tag: assertion 'tag->priv->table == buffer->priv->tag_table' failed
Expected results:
1. A scrollable description of the license should appear in the "About Files"
dialog.
2. The full license is not expected to appear in this dialog.
3. There should be no obvious misformatting, corruption, or characters
rendered as boxes with hex digits.
This is not an issue within the GNOME 3.14 rebase (nautilus-3.14.2-1.el7.x86_64). The Licence button has been replaced with a hyperlink that opens browser and leads to online version of GPL.
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.
https://rhn.redhat.com/errata/RHBA-2015-2236.html
Created attachment 964831 [details] Nautilus about files backtrace Description: Nautilus About Files returns "Gtk-CRITICAL **: gtk_text_buffer_apply_tag: assertion 'tag->priv->table == buffer->priv->tag_table' failed" in terminal Version-Release number of selected component (if applicable): nautilus-3.8.2-10.el7.x86_64 Steps to Reproduce: 1. In a terminal window, as a non-root user, run "nautilus." 3. In the upper left portion of the screen, just to the right of Activites in gnome-shell, click the Files menu. 4. Click "About Files" in this menu. 5. Click the "License" button in the "About Files" dialog. Actual results: About files is opened, output in terminal: (nautilus:30052): Gtk-CRITICAL **: gtk_text_buffer_apply_tag: assertion 'tag->priv->table == buffer->priv->tag_table' failed Expected results: 1. A scrollable description of the license should appear in the "About Files" dialog. 2. The full license is not expected to appear in this dialog. 3. There should be no obvious misformatting, corruption, or characters rendered as boxes with hex digits.