After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703578 - Closing gimp window with Import PDF open causes gimp to lose window but not exit
Closing gimp window with Import PDF open causes gimp to lose window but not exit
Status: RESOLVED DUPLICATE of bug 629941
Product: GIMP
Classification: Other
Component: General
2.8.6
Other Linux
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-07-03 22:49 UTC by Ari Pollak
Modified: 2013-07-04 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
proposed patch (2.60 KB, patch)
2013-07-04 17:11 UTC, Massimo 		accepted-commit_now Details | Review

Description Ari Pollak 2013-07-03 22:49:12 UTC 
Steps to reproduce:

1. Run gimp file.pdf
2. Click the gimp window close button 
3. This gets printed to stdout and all the gimp windows disappear, but the process is still left running. Which is kind of a problem since you won't know that if you didn't open gimp from a console, and then you try to run gimp again and nothing happens.

(gimp:22117): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'

(gimp:22117): Gimp-Core-CRITICAL **: gimp_message_valist: assertion `handler == NULL || G_IS_OBJECT (handler)' failed
Comment 1 Ari Pollak 2013-07-03 22:49:29 UTC 
Oh, forgot the original bug report: http://bugs.debian.org/714871
Comment 2 Massimo 2013-07-04 17:11:51 UTC 
Created attachment 248403 [details] [review]
proposed patch

Ii seems to fix the issue, if there are no objections I'll push it
tomorrow
Comment 3 Michael Natterer 2013-07-04 18:07:48 UTC 
Comment on attachment 248403 [details] [review]
proposed patch

Looks correct.
Comment 4 Michael Natterer 2013-07-04 18:59:18 UTC 
This is actually a duplicate, will use the patch here anyway.

*** This bug has been marked as a duplicate of bug 629941 ***