Inkscape (GTK+/Quartz) calls all output extensions when quitting while clipboard not empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Triaged
|
Medium
|
Unassigned |
Bug Description
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.
Confirmed with
- GTK+ 2.24.10 on Mac OS X 10.5.8 (32bit, Intel)
- GTK+ 2.24.11 on OS X 10.7.4 (64bit)
Steps to reproduce:
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. PS export options dialog after closing the main window (and crashes when cancelling the export options dialog).
System Info OS X 10.7.4:
Xcode 4.3.2, llvm-gcc-4.2, MacPorts 2.1.2
glib2 2.33.10, glibmm 2.32.1, gtk2 2.24.11, gtkmm 2.24.2
description: | updated |
description: | updated |
Changed in inkscape: | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | removed: crash |
summary: |
- Inkscape (GTK+/Quartz) calls output extensions or crashes when quitting - while clipboard not empty + Inkscape (GTK+/Quartz) calls all output extensions when quitting while + clipboard not empty |
Changed in inkscape: | |
importance: | High → Medium |
Changed in inkscape: | |
milestone: | none → 0.92 |
tags: |
added: gtk-quartz removed: gtk-osx |
Possibly related to
Bug #418242 “Incorrect call to output plugins (with persistent error message) on copy”