Created attachment 52056 [details] This is the original image, which is then mirrored and flipped in the other attachements. Version: unspecified (using KDE 4.5.1) OS: Linux When I use the 'mirror' or 'flip' tools in Gwenview 2.5.0 (I don't know the english strings for that as I don't use english locale, but these are the tools that flips the image either horiz. or vert.) and then I save the image as a new file, it is displayed ok, but when I reload the picture, you can see the original unflipped image in the background and over that is the new flipped image, but it is shifted either to the left (mirror) or to the top (flip) by some amount of pixels, therefore enabling you to see the original image beneath it (see the attachements for better understanding). Interesting is, that it doesn't happen with all images. I'll upload two testcases so you can see. Reproducible: Always Steps to Reproduce: 1. Open the image 2. Use Mirror or Flip tool Actual Results: The image is displayed as it should be, but it is not saved that way. Expected Results: Have the image saved ok (what I see is what I want to have saved). I'm marking this bug as a major as it describes it as 'bug that causes data loss', which this bug certainly does (worst case scenairo would be if you'd overwritte your original image).
Created attachment 52057 [details] This image is only mirrored and then saved as a normal JPG with no additional settings.
Created attachment 52058 [details] This one is flipped and then again saved as JPG with no extra options whatsoever.
Created attachment 52059 [details] This is another original JPG image with different buggy results when mirrored/flipped
Created attachment 52060 [details] This is mirrored version of the previous attached image. See the tiny bar on the right
Created attachment 52061 [details] This is flipped version of the second image. Interesting is, that this image seems ok.
I can reproduce the reported problem using the attached original image in KDE SC 4.8 beta2
probably related with bug 132352 and bug 153066.
*** This bug has been marked as a duplicate of bug 132352 ***