Cairo render prints nothing bitmap render crashes program

I just tried the December 18 and the December 20th build and got nothing on my prints. I'm running in XP. I tried the bitmap setting but still got nothing. I notice that the page range only allows "All". "Selection " and other settings are greyed out.

Confirmed, running the build of December 21th on a XP machine. Both Bitmap and Cairo printing crash inkscape. I cannot get a backtrace because no debugging symbols appear to be included in the windows builds these days.

Debugging symbols are now included in the nightly windows build, but there's still a problem in getting a backtrace. I only get this

DotNet runtime error: "This application has requested the Runtime to terminate it in an unusual way...."

and in gdb:

Program exited with code 03.
(gdb) bt
No stack.
(gdb)

http://bugzilla.gnome.org/show_bug.cgi?id=482089

To work around this currently, make sure you have gtk/gtkmm 2.12.1 or newer installed. This contains the fix for the gtk bug that is causing the problem.

Sounds like we should configure automake to issue an error if using gtk 2.12.0 specifically. Here's a patch for automake to kick out if that version is present. Tested on my system and works correctly.

It might be nice to give the user a way to override this via a configure flag, since I think this will make Inkscape unbuildable on Ubuntu. Alternatively, perhaps we could get seb128 to SRU the libgtk+ fix into Gutsy?

This has been worked around with svn commit 16865.

Btw, we decided to mark bugs Fix Released when committed to the main SVN tree. Many people use Inkscape dev builds, so a fix there is considered "released".

I'm running Windows XP, Inkscape0712181705.7z.
When I print, the crash message I get in DOS is:

C:\Python25\APP>python inkcl.py
return code: 3

(inkscape.exe:1308): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Error from StartDoc cairo_win32_surface_create: The handle is invalid.

terminate called after throwing an instance of 'Gtk::PrintError'

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

My question is, how do I check which version of gtk I have, and where would I get a newer version? I have a directory called gtk-2.0, is this obsolete?

Printing dialog still crashes Inkscape into desktop under WinXP SP2 even with latest SVN build: inkscape-0801141700.7z
This is pretty critical error.

For windows-specific problems, please open a new bug report. The bug originally described here (100% CPU, no print-out) has been fixed. Thanks!

I can't print either in Win XP

Do you get any feedback if you run Inkscape using this script?

C:\Python25\APP>python inkcl.py

from http://kaioa.com/node/42