On Fri, Aug 21, 2020 at 01:53:32AM +0200, Anon1336 wrote:
> At first, I thought it was a one-time bug so I tried using the bpo.
> Once again, under the same conditions, Inkscape crashed. Finally, I
> tried using the 1.0 AppImage (to test "sterile" and see if this was
> Debian-specific or Inkscape in general). The result is the same. Since
> it wasn't a "world-ender" bug, I went back to using the native Debian
> bpo and decided to just save a lot (side-note: auto-save and recovery
> still occasionally fails).
Since you tried the AppImage and reproduced with that as well, could you
consider filing a bug report upstream directly at
https://gitlab.com/inkscape/inbox ?
Also, I'm uploading now 1.0-5 to backports, if you could see whether
that also triggers this crash it would be useful (1.0-2 disable a bunch
of asserts that might or might not be relevant).
> The errors (see below) point to the problem being Inkscape-specific (the core lib), so it's very concerning that there's this "domino effect".
>
> Here's the relevant dmesg outputs:
> inkscape[18142]: segfault at 148 ip 00007efbfefec5db sp 00007ffbffff9620 error 4 in libinkscape_base.so[7efbfe58a000+bb0000]
> traps: inkscape[28062] general protection fault ip:7efbfeed39a1 sp:7ffbffff8520 error:0 in libinkscape_base.so[7efbfe58a000+bb0000]
>
> If I have time, I'll try running Inkscape and Thunar from two consoles and try to reproduce the error. Hopefully it'll shed some light on it. Hopefully still, I won't need to.
Likewise, if you can get a stacktrace it usually helps nailing down where
the bug is.
--
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