Both inkscape-0.39 and inkscape-0.40 crash with a GLib error when trying to print. Reproducible: Always Steps to Reproduce: 1. Run inkscape 2. Open any svg 3. Print it from menu or button Actual Results: Inkscape brings up an error dialog box: "Inkscape encountered an internal error and will close". The command line posts something a bit more useful: (inkscape:27910): GLib-CRITICAL **: file gthreadpool.c: line 284 (g_thread_pool_new): assertion `g_thread_supported ()' failed GLib-ERROR **: The thread system is not yet initialized. aborting... 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 version of glib is 2.4.8 Expected Results: Printed the svg and continued. My version of GLib is glib-2.4.8 # emerge info Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r9 i686) ================================================================= System uname: 2.6.9-gentoo-r9 i686 AMD Athlon(tm) processor Gentoo Base System version 1.6.7 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Nov 11 2004, 03:23:16)] distcc 2.18.2 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O3" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O3" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirror.datapipe.net/gentoo http://open-systems.ufl.edu/mirrors/gentoo http://mirror.datapipe.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow 3dnowex X a52 acl acpi acpi4linux aim alsa apm atlas avi bash-completion berkdb bitmap-fonts blas bonobo c++ cairo cddb cdparanoia cdr cdrom chroot clisp crypt cscope cups dio directfb divx4linux djbfft dnd dts dv dvd dvdr dvdread eds encode erandom evms2 evo exif f77 faac faad fam fastcgi fbcon ffmpeg fftw flac foomaticdb fortran freetype ftp gb gd gdbm gif gimp gimpprint ginac gnome gnomedb gnuplot gphoto2 gpm gsl gstreamer gtk gtk2 gtkhtml guile hal hbci hdf5 icq ieee1394 imagemagick imap imlib ipv6 irda jabber java javascript jikes joystick jpeg junit kde lcms libg++ libwww lirc lufsusermount mad maildir matroska mcal mikmod mime mmap mmx mmx2 mng motif mozilla mozsvg mp3 mpeg mpeg4 mpi mplayer mysql ncurses nls nptl nvidia odbc ofx oggvorbis openal opengl opie oss pam pcre pda pdf pdflib perl pic plotutils png posix postgres ppds python qt quicktime quotes readline rtc samba scanner sdl shared sharedmem slang sndfile snortsam spamassassin spell sse ssl stroke svg svga tcltk tcpd tetex theora tiff transcode truetype truetype-fonts usb v4l v4l2 vnc wmf x86 xfs xine xinerama xml xml2 xmms xosd xrandr xsl xv xvid xvmc zlib"
Can you post a gdb backtrace? See http://inkscape.org/report_bugs.php for using gdb
OK. I following the instructions on running gdb and got a backtrace. Note that I do not have USE="debug" flag turned on. If this report doesn't have the right info , I can recompile and rerun gdb. Bear with me, this is first time I have run gdb, so I'm not really sure what I am looking for. ender@asengard ~/home $ gdb inkscape GNU gdb 6.2.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /usr/bin/inkscape (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1220237632 (LWP 31494)] (inkscape:31494): GLib-CRITICAL **: file gthreadpool.c: line 284 (g_thread_pool_new): assertion `g_thread_supported ()' failed GLib-ERROR **: The thread system is not yet initialized. aborting... Program received signal SIGABRT, Aborted. [Switching to Thread -1220237632 (LWP 31494)] 0xffffe410 in ?? ()
Hi Alex, Unfortunately that doesn't give enough info to troubleshoot this. Can you repeat this but then after issuing the run command, do "bt"? Also, I note that you're compiling as architecture 'athlon', but you've marked Hardware=x86. If you're compiling on athlon, shouldn't your Hardware be set to amd64? If so, then this bug is probably invalid... CFLAGS="-march=athlon -O3"
Is anyone else seeing this bug? I've not had this problem on gentoo so cannot recreate it. If someone can post a backtrace, we might be able to get a better clue as to what is happening. Note that printing is not always required when using Inkscape, so a crash in the printing subsystem should not be a blocker on Inkscape in general. Many people use other apps like Scribus to do the printing, or just use Inkscape for exporting to png, for example.
Recent updates to packages in Gentoo seem to have caused this problem to go away. I recently upgraded to inkscape-0.40-r1 and was not able to get this crash to reoccur on either my laptop or my main desktop machine. HOWEVER, the printing is not correct. None of the text shows up! I can convert the svg (eventually) to a pdf and everything prints out fine. Should I file a different bug?
Yes, there's a lot of unfinished work in the printing/postscript font handling. It's likely this is a missing feature rather than a bug. You could try using different fonts and see if that has an effect. Also, this code depends on gnome-print and pango, so changes in those could affect whether or not you see the problem. In any case, I'd recommend that you re-file this bug in Inkscape's bug tracker so it can be tracked there. It does not sound like this should be a blocker bug for Inkscape 0.40 on Gentoo...
This bug can be closed for gentoo.
Ok, closing this one. Thanks and cheers, Marc.
I still get this problem with inkscape-0.40-r1, but only if I have 'gnome' in my USE variable. Should the bug be reopened?
