export drawing to png failed

[Benjamin Drung]

Binary package hint: inkscape

I have a command similar to "cat go-last.svg | inkscape -f /dev/stdin -e go-last.png". Instead of creating a go-last.png, I get following output:

** (inkscape:5190): WARNING **: Die automatische Ermittlung des Formats ist fehlgeschlagen. Die Datei wird als SVG-Dokument geöffnet.
Background RRGGBBAA: ffffff00
Area 0:0:16:16 exported to 16 x 16 pixels (90 dpi)
Bitmap saved as: gnome-wine/16x16/actions/go-last.png

** (inkscape:5190): CRITICAL **: bool sp_png_write_rgba_striped(SPDocument*, const gchar*, long unsigned int, long unsigned int, double, double, int (*)(const guchar**, int, int, void*), void*): assertion `fp != NULL' failed

You can simply reproduce it by checking out gnome-colors and running make:
svn checkout http://gnome-colors.googlecode.com/svn/trunk/ gnome-colors-read-only && cd gnome-colors-read-only/gnome-colors && make

ProblemType: Bug
Architecture: amd64
Date: Sat Jul 11 19:52:56 2009
DistroRelease: Ubuntu 9.10
Package: inkscape 0.47~pre1-0ubuntu1
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
SourcePackage: inkscape
Uname: Linux 2.6.31-2-generic x86_64

[perfectska04 (perfectska04-deactivatedaccount)]

Same issue for me, the files don't export at all with 0.47~pre. It works perfectly using the stable 0.4.6 version in Jaunty.

[Felix Crux (felixc)]

Just to confirm, are you seeing this bug in the Ubuntu-provided package? If so, I will mark it as confirmed since we have two separate reports.

If you are only experiencing the bug in a version of the software built from upstream sources, then this is not something that the Ubuntu project can fix, and it should be reported to the software developers. Cheers!

[Benjamin Drung (bdrung)]

Yes, the bug is in the Ubuntu-provided package.

[Benjamin Drung (bdrung)]

The bug only appears, if I use relative path names. So a valid workaround is to use absolute path names.

[Peter Moulder (pjrm)]

It looks like r20247 changed it so that the filename was interpreted relative to the document's directory (presumably /dev in this case).

Ted, do you recall what this change was for? Should just one of the callers be made to interpret changed to consult the document's directory, so that the argument to -e is relative to the current working directory as one would expect?

[su_v (suv-lp)]

Bug #168715 “Exports to relative paths should work properly”?
(includes patch <http://launchpadlibrarian.net/19325258/relative2.patch> apparently first committed in rev. 20135)

[su_v (suv-lp)]

Not reproduced with Inkscape 0.48+devel r9906 on OS X 10.5.8

LeWitt:bug suv$ cat 398221-drawing.svg | inkscape -f /dev/stdin -e 398221-bitmap.png
Xlib: extension "RANDR" missing on display "/tmp/launch-q7Xggu/:0".

** (inkscape:72808): WARNING **: Format autodetect failed. The file is being opened as SVG.
Background RRGGBBAA: ffffff00
Area 0:0:400:400 exported to 400 x 400 pixels (90 dpi)
Bitmap saved as: 398221-bitmap.png
LeWitt:bug suv$

@Benjamin - can you confirm that the error still exists with current stable version 0.48 on Ubuntu?

[Benjamin Drung (bdrung)]

No, this bug is fixed in inkscape 0.48.0-1ubuntu1 (Ubuntu 10.10), because it's a duplicate of bug #168715.