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 774026 - Modifications maked while exporting are visible (partially) in exported file
Modifications maked while exporting are visible (partially) in exported file
Status: RESOLVED DUPLICATE of bug 309196
Product: GIMP
Classification: Other
Component: General
Other Linux
: Normal minor
: ---
Assigned To: GIMP Bugs
Depends on:
Reported: 2016-11-07 00:41 UTC by Hilary Jendrasiak
Modified: 2016-11-08 11:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Hilary Jendrasiak 2016-11-07 00:41:51 UTC
You can't modify image while exporting because modifications will be exported too (in some part of file).

How to see it:
1. Work on big image (it just need to gain some time while exporting).
2. Export to png (imho: it's obvious that this is not the only bugged format).
3. While exporting make some changes on image.
4. At last we have file with part of original image and part (on bottom) after our changes maked while exporting.

Example result:
Yes, you see result of: export, modify, modify, end exporting.

Solution (some ways can be joined each other):
a) Block any modifications while exporting.
b) Show warning before modifications will be commited and can destroy exported file.
c) (Option in gimp's settings?) exporting can be: 1. copy whole image to other place in RAM. 2. export from that place(!). Any modifications we can make as always, because exporting is from copy of image. Copy from ram to ram is easy to make, but better way is make it as only an option and default- just block modifying while exporting.
Comment 1 Michael Natterer 2016-11-08 11:22:03 UTC
Thanks for taking the time to report this.
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 309196 ***