Bug 324597 - Rotating and saving a JPEG image changes the image itself, not the EXIF orientation tag
Summary: Rotating and saving a JPEG image changes the image itself, not the EXIF orien...
Status: RESOLVED FIXED
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 4.11.1
Platform: Ubuntu Linux
: VHI major
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords: usability
: 328282 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-09-06 19:08 UTC by Tanja Schulte
Modified: 2019-08-24 17:56 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tanja Schulte 2013-09-06 19:08:25 UTC
I'm shocked: I've just rotated some jpg images via the buttons in the toolbar, was asked to save the rotated images when I wanted to quit, said yes - and now the files are not even half the file size they were before (3,3 MB before, 732,2 KB to 1,3 MB after saving). That really is a "no go". Saving after rotation has to be lossless - or at least I want to be asked at which compression I want to save.

Reproducible: Always
Comment 1 Christoph Feck 2013-09-11 23:25:45 UTC
I would say this is a bug, but not really a duplicate of bug 294594. Rotating the image should only update EXIF info, not write a new image in the first place.
Comment 2 Nate Graham 2017-09-09 13:42:57 UTC
Also not-quite-a-duplicate of https://bugs.kde.org/show_bug.cgi?id=294594. They're not the same, but unnecessarily re-saving the image triggers 294594.

Using this as the base for other bugs reporting "rotating image changed/deleted metadata and reduced the file size instead of just changing the EXIF rotation tag".
Comment 3 Nate Graham 2017-09-09 13:43:59 UTC
*** Bug 328282 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2019-08-12 19:46:14 UTC
This appears to be fixed as of Gwenview 19.04.0. Please verify.
Comment 5 Nate Graham 2019-08-24 17:56:33 UTC
Yup, can confirm fixed.