GNOME Bugzilla – Bug 57766
Gimp saves wrong data!
Last modified: 2009-08-15 18:40:50 UTC
I noticed Gimp 1.2.1 saves wrong data. For me it looks that it saves a previous history snapshot instead of the current one. How to reporoduce (my steps) - scan the data (XSane) - crop, rotate (do whatever) - save as PNG -> previous snapshot gets saved Quick workaround I 'developed': do anything that is undoable but in this case won't change the buffer (I use FlattenImage ;-). Save will probably still use previous one, but it's the same than current, so it saves what it should from the beggining
Are you sure that you are not simply saving the wrong layer? Did the Export dialog show up warning you about multiple layers? How exactly can we easily reproduce your problem? I do not want to scan an image, so you should probably start with "Create New Image (size foo x bar, type blah...)". Then please specify exactly what to do (e.g. "Crop Image to size foo x bar") and how to save (thru the menu? filetype specified or by extension?).
Yes, I am absoulutely sure. There ain't any layers except that scanned one. I invoke "Save as" via menu. Chosing PNG "by extension" or specifing it manually gives no difference. I'll try to reproduce that bug w/o the scanning part. Anyway I now got a feeling that it not saves previous history state but the the 1st history entry (in my case it's image just after scan).
Do as follow: - "New image" (via menu) (2549x3509 pixels) RGB and other defaults - paint something (I did 2 squares on the top - rotate 90 degres clockwise (invoked by my keyboard shortcut) - save as PNG you will get blank image (1st step)... but rotated...
Sorry, I can not reproduce this (using gimp-1.2.2-pre3) and I can't imagine how this could ever happen.
Maybe this would change something. I got mostly default GIMP settings except for: "Undo levels" = 20 "Tile Cache Size" = 256MB GIMP 1.2.1 from Debian's unstable .deb package (precompiled)
Additional information: the preview image is saved correctly, but the main data ain't. I've encountered some additional problems, that looks to me as memory handing related. Haven't tried to reproduce them yet.
Are you sure that your problem is not similar to bug #51114 ? The examples (2a) and (2d) show two cases in which the wrong data is saved in a PNG file when the size of the image (canvas) is not the same as the size of the layer. If your shortcut key rotates the current layer instead of rotating the whole image, then that could explain why the PNG file does not contain what you expect (because it will save the contents of the layer and ignore the canvas size). That would also explain why flattening the image solves the problem. The mismatch between the preview (.xvpics thumbnail) and the saved data is caused by another bug: see bug #25272. Please have a look at bug #51114 and check if your problem is similar to that one, or if you have found a different bug. If this is a different problem and you suspect that it is related to the memory, then maybe you could check the output of "free" while the Gimp is running (to see if the memory gets too low on your machine). Also, I recommend that you upgrade to the latest stable version of the Gimp: version 1.2.2 (there is a .deb package available).
Closing this old bug, assuming that it was a duplicate of bug #51114. This problem should not occur anymore with gimp-1.2.3 or later.
*** This bug has been marked as a duplicate of 51114 ***