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.
Bug 1061085 - librsvg2-2.26.0-6 breaks Gnome
Summary: librsvg2-2.26.0-6 breaks Gnome
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: librsvg2
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthias Clasen
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-04 11:15 UTC by Jonathan Underwood
Modified: 2018-12-04 17:18 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-04 20:52:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jonathan Underwood 2014-02-04 11:15:23 UTC
Description of problem:
Updating a system to librsvg2-2.26.0-6 causes endless spawning of Nautilus browsers upon login and the system becomes unusuable. Downgrading to librsvg2-2.26.0-5 fixes the problem.

dmesg and /var/log/messages is full of messages like:

Feb  4 10:43:26 vincent kernel: nautilus[18098] general protection ip:7f2555a3f33c sp:7fff9b0e0c40 error:0 in librsvg-2.so.2.26.0[7f2555a19000+37000]
Feb  4 10:43:26 vincent abrt[18104]: Not saving repeating crash in '/usr/bin/nautilus'


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


How reproducible:
librsvg2-2.26.0-6

Steps to Reproduce:
1. Update to librsvg2-2.26.0-6
2. Boom.
3.

Really, did this package actually go through QA?!

Comment 1 Ask Jakobsen 2014-02-04 12:28:19 UTC
Same problem on 6.5.

Comment 2 Tomas Hoger 2014-02-04 12:32:36 UTC
Work is in progress to correct this regression.

Comment 3 Jonathan Underwood 2014-02-04 13:33:30 UTC
(In reply to Tomas Hoger from comment #2)
> Work is in progress to correct this regression.

Good to hear, thanks for the notification.

Comment 4 Akemi Yagi 2014-02-04 14:41:51 UTC
Like the submitter, I, too, am thinking in terms of QA process. That is, what could / should have been done to catch this type of bugs. In this particular case, restart of X would have produced the error.

Comment 5 Martin Jürgens 2014-02-04 18:37:28 UTC
confirmed. really frustrating to have this bug appear in a stable release.

Comment 6 Alexander Lindqvist 2014-02-04 18:45:54 UTC
Also affected on all upgraded workstations. 

Downgrading while Nautilus spawns new windows stops the process and automatically begins to close all windows again..

But this is not what we expect from an EL update. This should have been caught in QA.

Comment 7 Tomas Hoger 2014-02-04 20:52:34 UTC
RHSA-2014:0127 erratum was updated with a new build of librsvg2 that fixes the reported crash, see bug 924414 comment 25.


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