Dear Maintainer,

I want to open a file to edit in Inkscape, but it crashes (SIGSEGV /
Segmentation fault) under some circumstances / with some files.

    * What led up to the situation?

1. Open Inkscape
2. In the start modal, open the "Time to Draw" tab
3. In the "Time to Draw" tab, select the "Existing Files" sub-tab
4. In the the "Existing Files" sub-tab, select "Browse for other
files..." and then press the "Load" button.
5. In the "Open a different file" window, navigate to a local folder.

    * What exactly did you do (or not do) that was effective (or
      ineffective)?

The first file in that folder is automatically pre-selected.
It is an svg file, which I do not want to open.
A preview of that svg file is shown on the right hand side.

I attached Screenshot from 2024-03-10 12-19-20.png in this state
(pre-selected file, seeing preview, before the crash. In the terminal
you can see an earlier crash.).

When I select a different file or navigate to a different folder,
Inkscape crashes.

The issue can be reproduced with different files.
I have attached 240310-inkscape-files.zip which contains a folder each
for two files that lead to a crash, and a third that does not lead to a
crash.

The crash only happens when with the "Open a different file" window from
the start screen.

The crash does NOT happen, when I disable the "Enable preview" checkbox.

The crash does NOT happen, when I already have a file open, and use
"File -> Open ...".

I can open the problematic files without any issue in Inkscape (Right
click -> Open With ...).

    * What was the outcome of this action?

Inkscape crashes (SIGSEGV / Segmentation fault).

I have attached a backtrace from gdb in: 240310-inkscape-gdb.txt

I have also attached the output from coredumpctl of another crash. I
have that dump available, but am not sure if I should attach it or not
(ca. 9MB compressed / 156MB uncompressed).

    * What outcome did you expect instead?

No crash. Being able to navigate to a different folder, or selecting a
different file and seeing another preview.


I am reporting this from Debian stable, as this is where I encountered
the issue. If you want, I am happy to try if I can reproduce this in
Debian testing. Nonetheless, as it is a crash I think it should be
tracked & fixed in Debian stable.
Although I think crashes may deserve a higher Severity, I selected
normal, as there is no data loss, the circumstances seem limited, and
there are at least two workarounds available.


Kind regards
André