| Summary: | Inkscape crashes with GLib problem when trying to print | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexander Hsia <xanderhsia> |
| Component: | Current packages | Assignee: | Marc Hildebrand (RETIRED) <zypher> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bryce, cniehaus |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Alexander Hsia
2004-12-06 20:44:44 UTC
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? |
