Crash upon any action

Bug #224020 reported by rockysynergy
4
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Undecided
Unassigned

Bug Description

I'm using Inkscape with Ubuntu 8.0.4(hardy). The inkscape version is 0.46. After opening the inkscape and as soon as I do anything the inkscape crashed with the error massage in terminal saying"(inkscape:7386): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed". I run the gdb and get the below out put:

y-laptop:~$ which inkscape | gdb
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
(gdb) Hangup detected on fd 0
error detected on stdin

Revision history for this message
Rygle (rygle) wrote :

We probably need more information that this. Can you please run gdb first, and then run inkscape from within gdb?

Changed in inkscape:
status: New → Incomplete
Revision history for this message
rockysynergy (rockysynergy) wrote :

Hey Rygle,

I have done what you asked me to do and use script recorded the output. Please find the output in the attachment.

Blessings,
Rocky

Revision history for this message
Rygle (rygle) wrote :

Hi Rocky,

To use gdb on windows, I normally do the following;
Instead of "(gdb) run inkscape", I would do "(gdb) file inkscape.exe inkscape.dbg" (which loads the debugging symbols) and then "(gdb) run".

I imagine this should translate fairly easily over to the linux context, but I'm sorry I have no idea where to get you a copy of the debug symbols file to load, and it's specific for each particular build, so you can't just use the Win32 one, or even from another version of Inkscape. On Windows it's simply a file called inkscape.dbg - after searching the wiki for debug, I couldn't come up with anything linux specific (Linux people know everything don't you?).

Can anyone help with regard to debug symbols on linux?

Having said that, what you did post seems to have a little helpful information;
=========
** (inkscape:16009): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(const gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_TEST_EXISTS )' failed
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

(inkscape:16009): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb62ff720 (LWP 16009)]
0xb68b64a3 in strncmp () from /lib/tls/i686/cmov/libc.so.6
=========

This may be helpful for someone who knows a bit more than me.

Revision history for this message
rockysynergy (rockysynergy) wrote :

Hey Rygle,

It has been a long time not reply to this. Because I think degrade to Unbuntu 7.04 or compile from source may purge the problem away. But none of these really works.

I followed tutorial from https://wiki.ubuntu.com/DebuggingProgramCrash and https://wiki.ubuntu.com/Backtrace did the debug again. and the result file is attached.

Blessings,
Rocky

Revision history for this message
Igor Fedorow (bud-wiser) wrote :

a possible solution/workaround might be to uninstall all fonts except some "basic" fonts, and try again. running inkscape on three different machines with gentoo, i also had it crash after any action (on all machines) with the same

GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed"

error message. i had a large collection of custom truetype-fonts installed on all machines. once i removed them, the error went away (apart from MUCH faster startup times). there must have been at least one font that caused the glib-error.

hope this helps!

Revision history for this message
rockysynergy (rockysynergy) wrote : Re: [Bug 224020] Re: Crash upon any action

Hey Igor Fedorow,

This really helps! Thanks very much!

Blessings,
Rocky

On Wed, Sep 24, 2008 at 3:40 PM, Igor Fedorow <email address hidden> wrote:

> a possible solution/workaround might be to uninstall all fonts except
> some "basic" fonts, and try again. running inkscape on three different
> machines with gentoo, i also had it crash after any action (on all
> machines) with the same
>
> GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed"
>
> error message. i had a large collection of custom truetype-fonts
> installed on all machines. once i removed them, the error went away
> (apart from MUCH faster startup times). there must have been at least
> one font that caused the glib-error.
>
> hope this helps!
>
> --
> Crash upon any action
> https://bugs.launchpad.net/bugs/224020
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Inkscape: A Vector Drawing Tool: Incomplete
>
> Bug description:
> I'm using Inkscape with Ubuntu 8.0.4(hardy). The inkscape version is 0.46.
> After opening the inkscape and as soon as I do anything the inkscape crashed
> with the error massage in terminal saying"(inkscape:7386): GLib-CRITICAL **:
> g_utf8_casefold: assertion `str != NULL' failed". I run the gdb and get the
> below out put:
>
> y-laptop:~$ which inkscape | gdb
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> (gdb) Hangup detected on fd 0
> error detected on stdin
>

Revision history for this message
ScislaC (scislac) wrote :

Given that you commented that the issue was taken care of, I'm closing this report.

Changed in inkscape:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.