[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#922097: inkscape stops with message complaining about an internal illegal instruction on start



Control: tag -1 moreinfo unreproducible

Hi,

On Tue, Feb 12, 2019 at 12:46:48AM +0000, André Isidoro Fernandes Esteves wrote:
> From either the kde menu or the command line inkscape stops with the following message  in a dialog:
> 
> O Inkscape encontrou um erro interno e será fechado agora.
> Inkscape has found an internal error and will be closed...

Please remember to always run your program with LANG=en LC_ALL=C.UTF-8
to prevent report error messages in English.
(although in this case it's easy to figure what it's saying…).

> on the command line:
> aife@elektrum:~$ inkscape
> 
> (inkscape:11286): glibmm-WARNING **: 00:41:36.444: Glib::ConstructParams::ConstructParams(): object class "gtkmm__GtkArrow" has no property named "arbow_type"
> 
> 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.
> Illegal instruction (núcleo despejado)
> aife@elektrum:~$ 

I can't reproduce this, and I'm afraid we'll need you to submit either a
core dump or a traceback.

To do the latter, please install gdb and the inkscape debug symbols
(from the inkscape-dbgsym package, see
https://wiki.debian.org/AutomaticDebugPackages)

Then run

$ gdb inksacpe
GNU gdb (Debian 8.2.1-1) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
…
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from inkscape...done.
(gdb) r
Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]
…

at this point you should see the same error message again, and once it
crashes again you will be at the same "(gdb)" prompt.

There, run the command "bt" and "bt full" to get the stack trace; copy
it and attach it here in the bug.

To get a core dump, run `ulimit -c unlimited` in the shell, and run
inkscape.  Once it crashes you will see the file created in the current
directory, if you could attach that as well it would surely help to
debug it further (although the back)race should be enough to at least
check what's going on; it could easily be that the crash comes from a
library rather than inkscape proper).

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: