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 678662 - Erroneous "close without saving" warning
Erroneous "close without saving" warning
Status: RESOLVED DUPLICATE of bug 675399
Product: GIMP
Classification: Other
Component: User Interface
2.8.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-06-23 11:09 UTC by Zozori
Modified: 2012-06-27 22:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Zozori 2012-06-23 11:09:39 UTC 
Image is scanned or read from JPG file into Gimp. Image is processed in Gimp and saved (exported) as JPG. X button at upper right corner of Gimp window is pressed in order to close the image. 

A warning pops up: Save the changes to image 'Untitled' before closing? "Close without Saving" has to be pressed to finally achieve closing of the image.

This warning should not occur because the image had been saved just before the attempt to close it.
Comment 1 Michael Schumacher 2012-06-23 11:16:56 UTC 
The image has been exported to a lossy format, but not saved in XCF. The dialog is intentional.
Comment 2 Zozori 2012-06-27 20:59:12 UTC 
In most cases I work only with JPG, not with XCF format (I think I am not the only one). For this application the warning is useless and has to be ignored. This is bad if Gimp is closed and the picture was neither saved nor exported after the last changes. 

Suggestion: The warning should inform, whether the picture was ...
... exported but not saved or ...
... not exported and not saved
Comment 3 Michael Schumacher 2012-06-27 22:15:35 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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