AFAICT due to changes in recent GTK+ 2.24.10 (or 2.24.11), Inkscape built with the quartz backend of GTK+ triggers random output extensions when quitting while data copied in Inkscape is still present on the clipboard.
Steps to reproduce:
1) mv ~/.config/inkscape{,-bkp}
2) launch inkscape (empty)
3) draw a rect
4) copy & paste the rect
5) quit Inkscape without saving
Expected result:
Inkscape quits.
Actual result:
- Inkscape 0.48.3.1:
Calls a series of output extensions (e.g. save as XCF, and some UniConvertor-based ones), and finally quits after having closed the dialogs with error messages from failing extensions.
- Inkscape trunk:
crashes immediately (backtrace attached), or opens e.g. PDF export options dialog after closing the main window (and crashes when cancelling the export options dialog).
AFAICT due to changes in recent GTK+ 2.24.10 (or 2.24.11), Inkscape built with the quartz backend of GTK+ triggers random output extensions when quitting while data copied in Inkscape is still present on the clipboard.
Steps to reproduce: inkscape{ ,-bkp}
1) mv ~/.config/
2) launch inkscape (empty)
3) draw a rect
4) copy & paste the rect
5) quit Inkscape without saving
Expected result:
Inkscape quits.
Actual result:
- Inkscape 0.48.3.1:
Calls a series of output extensions (e.g. save as XCF, and some UniConvertor-based ones), and finally quits after having closed the dialogs with error messages from failing extensions.
- Inkscape trunk:
crashes immediately (backtrace attached), or opens e.g. PDF export options dialog after closing the main window (and crashes when cancelling the export options dialog).