GNOME Bugzilla – Bug 116824
using the Nuvola icon theme immediately crashes nautilus in libart
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Red Hat Linux release 9 (Shrike) Package: librsvg Severity: critical Version: GNOME2.3.3 2.3.6 Gnome-Distributor: GNOME.Org Synopsis: crash during nautilus startup Bugzilla-Product: librsvg Bugzilla-Component: general Bugzilla-Version: 2.3.6 BugBuddy-GnomeVersion: 2.0 (2.3.3) Description: Description of the crash: I'd just started up nautilus (probably pointing at the industrial theme still) in my jhbuilt enviroment (which, come to think of it, might not have industrial) when I got this stack trace, which looks to be in librsvg. Debugging Information: Backtrace was generated from '/home/louie/jhbuilt/bin/nautilus' [New Thread 1085637216 (LWP 1463)] [New Thread 1106001200 (LWP 1469)] [New Thread 1097608496 (LWP 1468)] 0xffffe002 in ?? ()
+ Trace 38458
Thread 1 (Thread 1085637216 (LWP 1463))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-06 09:54 ------- Unknown version 2.3.6 in product librsvg. Setting version to the default, "unspecified". Reassigning to the default owner of the component, librsvg-maint@bugzilla.gnome.org.
moving into needinfo. waiting 2 weeks before closing. we need the svg(s) that caused this crash please
At the very least, the Nuvola icon theme in gnome-themes-extras seems to cause this. No idea how to track that down to a specific svg, though.
After looking at Micke's trace, I'd mark that bug a dup of this one, since this one has a stack trace in it and hence is searchable. Have updated the title and cc'd Micke.
Lush, Wasp, and Gorilla from gnome-themes-extra all cause this crash; BlueSphere and Flat-Blue do not.
BTW, Dom, if there is some test program that I can use other than nautilus I'll happily build/run it on all those themes to discover the offending svgs.
hey luis, you can use 'rsvg foo.svg foo.png' to convert svgs to pngs, even run it inside of a shell-script loop or something: for $file in `ls *.svg`; do rsvg $file $file.png done then see where you have foo.svg but not foo.svg.png or if you'd like, use 'eog foo.svg' to view the svgs 1 by 1
OK, so I found at least one criminal :) [Turns out that using nautilus to view theme directories helps narrow it down real fast ;) Attaching it. Output: [louie@localhost apps]$ rsvg gnome-gimp.svg gnome-gimp.png rsvg: art_render_gradient.c:333: art_render_gradient_linear_render_8: Assertion `(offset_fraction != stops[ix-1].offset) || (d_offset >= 0.0)' failed. Aborted
Created attachment 18085 [details] icon that crashes nautilus, rsvg, presumably gnome-theme-manager
really strange. it doesn't happen here at all - no warning or anything. maybe i have an older libart or something. i get an icon of wilbur on top of a "document" background
Should it be reassigned over there, maybe? It definitely happens here (pretty much head libart, I guess.)
Ok, just tested this on my RH9 machine running libart_lgpl 2.3.12-0.ximian.6.2 and CVS librsvg. Works like a charm for me.
As far as I can see from the changelog I'm running libart_lgpl 2.3.12. here, so unless someone committed something without updating the ChangeLog there shouldn't be differences between my build and XD2. [We don't patch libart.] Blah. Micke, what are you running?
The stack trace makes this look the same as bug 116942, which is the crash that I received and have duplicated multiple times. Should that bug be marked as a duplicate of this one? [And, just for the record, I have Redhat 9, on which I've installed XD2, and which I then later (a week or two ago) went and built gnome from cvs with jhbuild.] Both these bugs also look similar to bug 96296, although there's no way my crash could have been caused by a mixture of Gnome 1.4 and Gnome 2.x libraries. Also, I downloaded Luis' test icon. The first five or so times I viewed the icon in nautilus, I received no crash. But I just now was able to get the crash by going to the directory containing that icon. That directory doesn't contain any other icons, so I guess that means that this crash isn't 100% reproducable.
this should be fixed in libart 2.3.14