User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.68 Safari/537.17 Build Identifier: A RAW file (in my case Nikon NEF files), opened via the ufraw gimp plugin, or opened directly in UFRAW and then invoking GIMP on it, does not have any EXIF data (according to File->Properties->Advanced). Indeed it does not have ANY properties at all. Opening a JPEG file DOES show limited EXIF data (for example the camera model), but does not show the lens information at all. (Likewise the gimplensfun plugin identifies the camera model, but not the lens). Reproducible: Always Steps to Reproduce: 1.Right click on a .NEF file, and select Open with GIMP. 2. When the UFRAW screen appears, click OK. 3. File->Properties->Advanced Actual Results: Pane is blank Expected Results: Pane should show much EXIF data.
Created attachment 702064 [details] Example RAW file that can be used to exhibit/test the problem
The Image Properties dialog works on XMP metadata, and EXIF metadata are supposed to be converted if present. The metadata is preserved however, when being exported to JPEG, it contains EXIF metadata, almost the same as in the original RAW file (exceptions where metadata needs to be different between raw and jpeg). I'll look into this.
Hi Nils, could you please pass the patch for UFraw into bugzilla. I will try to fix that with the help of upstream:) Some logs which I gathered when gimp was run from command line were: While parsing XMP metadata: Error: No XMP packet found Not implemented yet (EDITOR_PROC)
Thread for that issue is discussed here: https://mail.gnome.org/archives/gimp-developer-list/2013-August/msg00047.html
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.