nautilus crashed with SIGSEGV (due to librsvg)

Bug #701820 reported by Romano Giannetti
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
librsvg (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: nautilus

I know this is not a new bug; it's here since two year. I am reporting it as a new one hoping to help to solve it with a trace.

Main bug is bug #305546, assigned to librsvg. But in my opinion, the bug is sŧill *also* a bug for nautilus, because it *crashes*.

Simply drop the (attached) file organigrama.svg in whatever directory, and trying to open the directory in nautilus will crash it. Drop it into your ~/Desktop folder, and you'll have a nice catch-22.

Syslog says:

SYS: Jan 12 09:34:26 romano-asus kernel: [11943.209529] nautilus[17523]: segfault at 0 ip 083e544a sp b24ffac0 error 4 in librsvg-2.so.2.32.0[83cc000+30000]
SEC: Jan 12 09:34:45 romano-asus dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.349" (uid=1153 pid=17534 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.2" (uid=0 pid=935 comm="/usr/sbin/console-kit-daemon))

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Jan 12 09:34:29 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x83e544a: repz cmpsb %es:(%edi),%ds:(%esi)
 PC (0x083e544a) ok
 source "%es:(%edi)" (0x083f9f1b) ok
 destination "%ds:(%esi)" (0x0000007b) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/librsvg-2.so.2
 ?? () from /usr/lib/librsvg-2.so.2
 ?? () from /usr/lib/librsvg-2.so.2
 ?? () from /usr/lib/librsvg-2.so.2
 ?? () from /usr/lib/librsvg-2.so.2
Title: nautilus crashed with SIGSEGV
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Related branches

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Now I attach the file. Extact it and see nautilus explode (by the way, the same crash happens in whatever try to preview the file, for example, the browse window of firefox).

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

...so, I think that, given that librsvg is broken since two year, a workaround is badly needed. As disabling preview for svg file thru all the GTK widgets and nautilus.

visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 rsvg_get_url_string (str=0x0) at rsvg-mask.c:91
 rsvg_marker_parse (defs=0x8c79970, str=0x0)
 rsvg_parse_style_pair (ctx=<value optimized out>,
 rsvg_parse_style (ctx=0x8c51a88, state=0x8d57358,
 rsvg_parse_style_attrs (ctx=0x8c51a88, state=0x8d57358,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
affects: nautilus (Ubuntu) → librsvg (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package librsvg - 2.32.1-0ubuntu3

---------------
librsvg (2.32.1-0ubuntu3) natty; urgency=low

  * debian/patches/90_git_null_crasher.patch: crasher fix from git (lp: #608026)
    (lp: #701820)
 -- Sebastien Bacher <email address hidden> Tue, 15 Mar 2011 18:06:59 +0100

Changed in librsvg (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.