After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 497229 - Error rotating .NEF RAW images
Error rotating .NEF RAW images
Status: RESOLVED DUPLICATE of bug 338495
Product: f-spot
Classification: Other
Component: Editing
SVN
Other All
: Normal enhancement
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-15 22:56 UTC by Josh Gerdes
Modified: 2008-05-08 05:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Josh Gerdes 2007-11-15 22:56:20 UTC
Please describe the problem:
In SVN version 3458 (and release version 0.4.0) when trying to rotate a RAW (.NEF) image I get the following error:

Error while rotating photo.
Received error "Unable to rotate photo type" while attempting to rotate xxxx.NEF


Steps to reproduce:
1. Open f-spot
2. Select an image while in the 'Browse" view
3. Click 'Rotate Right' or 'Rotate Left'


Actual results:
A window pops up with the following error:

Error while rotating photo.
Received error "Unable to rotate photo type" while attempting to rotate xxxx.NEF

Expected results:
The image is rotated or the the 'Rotate Right' and 'Rotate Left' buttons are disabled when an image with an incompatible photo type is selected.

Does this happen every time?
yes

Other information:
This possibly could be related to other bugs but I did not find a suitable match in my search.

If RAW is not supported for image rotation then I think the rotation edit buttons should be disabled when a RAW image is selected.  

Ultimately I would like RAW to be supported so I can rotate RAW images if need be.
Comment 1 Maxxer 2007-11-16 07:54:31 UTC
Very much related to Bug 338495, I think.

Switching to enhancement.
Adding .NEF to bug summary.
Comment 2 Maxxer 2008-05-08 05:44:28 UTC

*** This bug has been marked as a duplicate of 338495 ***