Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48695 - [gimp] tiff exif data not preserved
Attached to Project:
Arch Linux
Opened by Hellracer (hellracer) - Friday, 25 March 2016, 23:28 GMT
Last edited by Isenmann Daniel (ise) - Tuesday, 29 March 2016, 08:42 GMT
Opened by Hellracer (hellracer) - Friday, 25 March 2016, 23:28 GMT
Last edited by Isenmann Daniel (ise) - Tuesday, 29 March 2016, 08:42 GMT
|
DetailsIt seems that the repository version if Gimp is compiled without libtiff. This causes the loose of exif metadata when opening a tiff file and exporting to jpg. The jpg file does not contain any exif data anymore. Please compile with libtiff support to prevent.
Tested on * Arch x64 with * gimp 2.8.16-1 installed * libtiff 4.0.6-2 installed Steps to reproduce: * Open jpg file with exif data in Gimp * Save file as jpg and set to keep exif data in export dialog * Check exif data of the exported jpg with a tool you like, no exif data there |
This task depends upon
Closed by Isenmann Daniel (ise)
Tuesday, 29 March 2016, 08:42 GMT
Reason for closing: Upstream
Additional comments about closing: Must be fixed upstream first, which is planned for 2.10
Tuesday, 29 March 2016, 08:42 GMT
Reason for closing: Upstream
Additional comments about closing: Must be fixed upstream first, which is planned for 2.10
ldd $(which gimp) | grep tiff
libtiff not in the list.
/usr/lib/gimp/2.0/plug-ins/file-tiff-save
NEEDED libtiff.so.5
/usr/lib/gimp/2.0/plug-ins/file-tiff-load
NEEDED libtiff.so.5
https://bugzilla.gnome.org/show_bug.cgi?id=56443
So my fault by misinterpreting the output of ldd.