Bug#349415: it's tuxpaint.svg -- libart doesn't like it

[Ben Armstrong]

On Sun, 2006-01-22 at 22:51 +0000, Jeroen Nijhof wrote:
> I looked a bit further, and found that gnome-panel tries to load
> /usr/share/icons/hicolor/scalable/apps/tuxpaint.svg
> (rather than a .png or .xpm version). And it looks like 
> libart_lgpl_2.so.2 (from libart-2.0-2 version 2.3.17-1) doesn't like that
> file; eog tuxpaint.svg crashes with a segfault.
> 
> So I suspect that libart-2.0-2 has a bug -- this bug is probably
> a dupe of #298225: line 125 of tuxpaint.svg contains a
> number 3.7787101e+16.
> 
> So Ben, it might be wise to correct tuxpaint.svg -- replacing
> 3.7787101e+16 by 0 seems to work, and allows for it to be viewed in eog
> I tried replacing it by 3000 or 6000 first, but that gives an artifact.

OK.  I've had upstream fix this and commit it.  I have gnome-panel
2.12.2 and libart-2.0-2 2.3.17-1 and cannot reproduce your bug, so I may
need assistance testing.

> Still, it's a rather annoying denial of service for gnome-panel
> that such an anomalous icon can cause such trouble, especially since it
> is hard to clean up: pretty much the only way was to log in on a text console
> and remove all of .gnome*, and start again.

I agree.  I have copied the fixed svg from CVS into my working copy of
0.9.15b so it will be included in my next tuxpaint upload (0.9.15-2, but
I'm not quite ready yet).

Ben