FS#10765 - Inkscape 0.46-4 segfaults at the Text and Font menu

Attached to Project: Arch Linux
Opened by Luca Bruno (kaeso) - Friday, 27 June 2008, 08:14 GMT
Last edited by Jan de Groot (JGC) - Sunday, 08 February 2009, 23:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

This bug was reported upstream at https://bugs.launchpad.net/inkscape/+bug/226499 but can't be reproduced on other distro.
It could something specific to your packaging, or a something particular in your environment.
This was reported to affect both x86 and x86_64 packages. Original bug report below:

*********
The bug is really easy to reproduce, I just open one inkscape instance (version 0.46-4) then open the Text and Font from the Text menu, then I just press close and inkscape crashes.
From console menu this is what I get:
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.

(inkscape:6002): GLib-WARNING **: g_main_context_prepare(): main loop already active in another thread
Segmentation fault

I'm using Arch Linux and have just downloaded the precompiled binary with pacman.
*********
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 08 February 2009, 23:18 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Won't build without gnomevfs: I could not reproduce a working binary that doesn't crash at text and font menu.
Comment by Jan de Groot (JGC) - Friday, 27 June 2008, 09:55 GMT
Can't reproduce it on x86_64, what architecture do you use?
Comment by Sebastian Kraft (needcoffee) - Friday, 27 June 2008, 21:36 GMT
Same problem here, as mentioned before on bugs.launchpad. I use inkscape svn on arch i686 (32 bit).
Comment by 甘露(Lu Gan) (ganlu) - Sunday, 29 June 2008, 12:48 GMT
Yeah, I confirm it. i686 with current packages.
Comment by Jan de Groot (JGC) - Monday, 30 June 2008, 08:18 GMT
Crashes on i686 here also. I tried rebuilding it, after applying two patches to get it built, it still crashes. I tried to debug using valgrind and gdb. In case of valgrind, gc does an invalid memory access and the program doesn't even start (I guess gc's memory allocation is something that valgrind doesn't like), in case of gdb, I get a crash inside glib that has to do with this GLib-WARNING message.
Comment by Sebastian Kraft (needcoffee) - Monday, 14 July 2008, 02:40 GMT
Error message has now slightly changed. I don't know if it is useful in some way. The new message is:

(inkscape:19056): GLib-WARNING **: g_main_loop_run(): called recursively from within a source's check() or prepare() member, iteration not possible.
Segmentation fault
Comment by Thorsten (Stellaris) - Thursday, 17 July 2008, 21:03 GMT
I can confirm the bug on i686 on a current Arch too, same error message as Sebastian's posted one.
Comment by 甘露(Lu Gan) (ganlu) - Friday, 18 July 2008, 13:31 GMT
Fedora package (inkscape.i386 0:0.46-2.fc9) doesn't have the problem so maybe this is Arch original one.
Comment by 甘露(Lu Gan) (ganlu) - Friday, 18 July 2008, 13:31 GMT
I mean on the Fedora 9. sorry.
Comment by Sebastian Kraft (needcoffee) - Friday, 18 July 2008, 15:42 GMT
Yes. I'm not sure, but there seems to be a problem with any gtklib or something. I switched back to ubuntu (not only due this problem) and there is not a problem with inkscape at all.
Comment by Anonymous Submitter - Monday, 04 August 2008, 20:26 GMT
Does someone how to get infos about how the Fedora or Ubuntu packages are made? I suspect there are different configure options given.
Comment by Jan de Groot (JGC) - Monday, 04 August 2008, 22:28 GMT
No matter what I try, this thing keeps crashing on i686 and works fine on x86_64. Tried to build without optimization (had to add patches for poppler though), but the text and font menu keeps crashing inkscape on i686. I've built gtkmm, glibmm, gtk2 and glib2 with debug symbols, but none give useful information.
Comment by Anonymous Submitter - Tuesday, 05 August 2008, 21:38 GMT
On the AUR Comment page of inkscape-svn the suggestion came up to remove all confiure options except --prefix=$pkgdir. That solved the error. Maybe it is an option for inkscape, too.
Comment by Anonymous Submitter - Friday, 08 August 2008, 22:48 GMT
Can you try to build it using --with-gnome-vfs? The svn-version works with this change (see in AUR).
Comment by P.H. (Vain) - Saturday, 09 August 2008, 14:40 GMT
Just to add some more details on the poppler issue:

Trying to recompile this inkscape version fails due to a changed method in poppler-lib. inkscape-svn in AUR already includes a fix - only the file src/extension/internal/pdfinput/pdf-parser.cpp is affected. To use the fix, make sure you've added -DPOPPLER_NEW_GFXFONT to your CXXFLAGS. Have a look at the current svn-code or just use the diff file I attached to this comment.

Anyway, I would expect these compile-errors to be gone when using current inkscape-sources...
   pdf-parser.cpp.diff (0.6 KiB)
Comment by Luca Morricone (orux) - Wednesday, 03 September 2008, 02:19 GMT
This is the solution:

http://www.archlinux.it/forum/viewtopic.php?id=2423
Comment by Michael (SiD) - Friday, 05 September 2008, 11:04 GMT
Version 0.46-6 worked for me. In version 0.46-7 the bug is back. (crashing when you close the text dialog-box)

Seems the problem is building it without gnome-vfs.
Comment by Anonymous Submitter - Friday, 05 September 2008, 18:18 GMT
I can confirm Michael's (Sid's) statement.
Comment by Michael (SiD) - Friday, 05 September 2008, 22:05 GMT
I just rebuild version 0.4.6-7 with gnome-vfs support and it does not crash.

I left a comment about this in the inkscape bug tracker.
https://bugs.launchpad.net/inkscape/+bug/226499
Comment by Matt Gushee (mgushee) - Monday, 03 November 2008, 01:51 GMT
Hey Luca,

Thanks for the solution! If there is important info in that thread that hasn't already been reported here or elsewhere, could you please provide a summary in English?
Comment by Matt Gushee (mgushee) - Tuesday, 04 November 2008, 01:22 GMT
Okay, I see what's going on.

First, Inkscape will segfault when built --without-gnome-vfs. BTW, I disagree w/ the severity being "medium." This bug makes Inkscape completely unusable for any project involving text. Really, the upstream source needs to be fixed, but it doesn't appear that that's going to happen immediately, so how about implementing the dead-simple workaround of building our package --with-gnome-vfs? Please?

Oh, but wait, there's more: seems that when the above is done, Inkscape fails to build against the current version of GTK. See:
https://bugs.launchpad.net/inkscape/+bug/238223
However, the fix for this is very simple, too:
http://launchpadlibrarian.net/15113774/gtk-clist.patch
Comment by JM (fijam) - Thursday, 20 November 2008, 20:23 GMT
I compiled inkscape 0.46 using 0.46-8 PKGBUILD and patches (poppler, gtk-clist and eqtexsvg) but WITHOUT gnome-vfs and I cannot reproduce the crash. If somebody could confirm that, it might be beneficial to drop gnome-vfs as a dependency, since it pulls quite a lot of stuff with it.
Comment by Jeroen Op 't Eynde (Duologic) - Sunday, 08 February 2009, 21:58 GMT
It seems to be fixed in 0.46-10, didn't try it without the gnome-vfs, I would like to see the package without that depencie in [extra]

Loading...