Description of problem: Gimp doesn't quit if ufraw-gimp is opened by it. Version-Release number of selected component (if applicable): gimp.x86_64 (2:2.6.10-1.fc13) ufraw-gimp.x86_64 (0.16-2.fc13) How reproducible: always Steps to Reproduce: 1. Open a NEF (nikon raw) image with GIMP. It will open GIMP and ufraw-gimp plugin. 2. Quit GIMP from the UI, without closing ufraw-gimp. Actual results: GIMP disappears from the screen but... if you ever need to open the GIMP once again you'll have a surprise, because: [andrei@Q9650:~]$ gimp --verbose Another GIMP instance is already running. as a consequence of: [andrei@Q9650:~]$ ps -ef | grep gimp andrei 4484 1700 4 02:54 ? 00:00:01 /usr/bin/gimp-2.6 /__sda3/pics/andrei.pics/01.raw/20071129004 - parcizvor.nef Expected results: When choosing from the UI to quit GIMP, it has to trully quit (not just the UI)... even if it has a plugin like ufraw-gimp opened for working. Additional info: Works as expected if you manually close the ufraw first.
hello, anyone there ? :)
Argh, sorry for dropping this. I can confirm the issue that the GIMP windows close, but the process stays running. With a different type of raw image file, also opened by ufraw, then closing GIMP, I get these error messages: (gimp:20302): GLib-GObject-WARNING **: invalid uninstantiatable type `-g-type-private--IFaceHolder' in cast to `GObject' (gimp:20302): Gimp-Core-CRITICAL **: gimp_message_valist: assertion `handler == NULL || G_IS_OBJECT (handler)' failed
The xsane plugin (another external one) doesn't have this problem.
I could see the same issue when pressing "Ctrl+Q" to quit GIMP while it was loading another image format (JPEG): GIMP-Error: Execution error for procedure 'file-jpeg-load': Procedure 'file-jpeg-load' returned no return values (gimp:10595): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' (gimp:10595): Gimp-Core-CRITICAL **: gimp_message_valist: assertion `handler == NULL || G_IS_OBJECT (handler)' failed
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I can reproduce this on F-15 with these versions: gimp-2.6.11-14.fc15.x86_64 ufraw-gimp-0.18-2.fc15.x86_64 It only happens to me if the image file name is supplied on the command line, however. If the file is opened via the File/Open menu entry, gimp exits (albeit with some warnings). I've checked this with the current development version of GIMP which shows the same or similar issues. I'll file this upstream as I currently don't know where the problem might lie.
It seems I've already done that: https://bugzilla.gnome.org/show_bug.cgi?id=629941
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Keeping this open for tracking.
gimp-2.8.6-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gimp-2.8.6-3.fc18
gimp-2.8.6-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gimp-2.8.6-3.fc19
Package gimp-2.8.6-3.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gimp-2.8.6-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12584/gimp-2.8.6-3.fc19 then log in and leave karma (feedback).
gimp-2.8.6-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
gimp-2.8.6-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.