Bug 278661 - Gwenview does not preserve resolution ( dpi / ppi ) when saving rotated images
Summary: Gwenview does not preserve resolution ( dpi / ppi ) when saving rotated images
Status: RESOLVED FIXED
Alias: None
Product: gwenview
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.6
Platform: Ubuntu Linux
: VHI major
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords: usability
: 357312 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-07-28 02:28 UTC by Frank Myhr
Modified: 2025-08-17 10:48 UTC (History)
7 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Myhr 2011-07-28 02:28:28 UTC 
Version:           2.6 (using KDE 4.6.2) 
OS:                Linux

OS: Kubuntu 11.04 Natty AMD64

I opened a 600 ppi 8-bit grayscale TIFF in Gwenview, rotated it 90 degrees CCW ("Left") and saved it. The TIFF is compressed with the "Deflate" method if that matters. Gwenview saved the rotated file with tags that incorrectly indicate 97 ppi.

Xorg.0.log has:
[    21.180] (**) RADEON(0): DPI set to (143, 98)
Maybe Gwenview took PPI from X?

In any case, the Gwenview-rotated TIFF has much lower PPI (much larger physical size) than it should.

Reproducible: Didn't try

Steps to Reproduce:
see Details


Expected Results:  
Gwenview should preserve original TIFF's resolution (ppi) upon rotation.
Comment 1 Romain Henriet 2013-02-24 16:26:42 UTC 
I have the same problem with png files. The original file was 300 ppi and after rotation it was 96 ppi.
Comment 2 Nate Graham 2017-11-08 23:08:52 UTC 
*** Bug 357312 has been marked as a duplicate of this bug. ***
Comment 3 yevalesaurabh5 2022-10-19 11:48:03 UTC 
** Removed due to violation of community policy **
Comment 4 A Linux User 2025-08-17 10:48:22 UTC 
Cannot reproduce anymore using Gwenview 25.08.0.

Pngs, jpgs and tiffs all show correct sizes after rotation (checked using identify -verbose file | grep Print).

So I think that this got fixed in the meantime and the issue can be closed.