Crafted preferences.xml makes SVG Input dialog constantly appear
Summary:
With the attached preferences.xml and an otherwise fresh config, Inkscape pops up this modal SVG Input dialog on virtually every operation.
It appears on startup, when a new window is opened, and even on selecting different objects. Furthermore, clicking Cancel crashes Inkscape skipping the crash handler dialog.
Steps to reproduce:
- Overwrite
preferences.xmlwith the attached file. - Open Inkscape
What happened?
Inkscape pops up the SVG Input dialog. It originates from this backtrace,
3 g_main_loop_run (x86_64) /usr/lib/libglib-2.0.so.0 0x7ffff4f39d8f
4 gtk_dialog_run gtkdialog.c 1398 0x7ffff791eaa7
5 Inkscape::Extension::Extension::prefs() extension.cpp 1122 0x7ffff688c0ba
6 Inkscape::Extension::open(Inkscape::Extension::Extension *, const char *) system.cpp 122 0x7ffff6890a1e
7 ink_file_open(Glib::RefPtr<Gio::File> const&, bool *) file.cpp 100 0x7ffff695ce7e
8 Inkscape::load_document(const char *) svg-renderer.cpp 52 0x7ffff6b765c4
9 Inkscape::svg_renderer::svg_renderer(const char *) svg-renderer.cpp 55 0x7ffff6b7664a
10 Inkscape::UI::Widget::MarkerComboBox::MarkerComboBox(Glib::ustring, int) marker-combo-box.cpp 120 0x7ffff6f78b88
So while populating the markers combo box, specifically while loading share/inkscape/ui/bad-marker.svg, the dialog is created. Clicking Cancel throws an uncaught exception in a signal handler, which crashes.
What should have happened?
It shouldn't be possible to get Inkscape into this state. The preferences file that causes this behaviour originated simply from testing the command palette, so in theory this situation can occur just by performing everyday operations.
Sample attachments:
Version info
Both 1.2.2 and 1.3-dev on Arch Linux.
