Rotation with Shotwell is not compatible with EOG
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eye of GNOME |
New
|
Undecided
|
Unassigned | ||
| NULL Project |
Invalid
|
Undecided
|
Unassigned | ||
| Shotwell |
Unknown
|
Unknown
|
|||
| eog (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: eog
On Ubuntu 10.10 beta including last updates.
How to reproduce :
- open a picture with EOG
- click on "Edit picture" button
- in the new window (Shotwell viewer), rotate the picture, then save, then close Shotwell
- EOG proposes to reload the picture, click on "Reload"
Result : EOG displays the picture without rotation.
Expected result : EOG should display the picture rotated the same way as in Shotwell.
Remarks :
1) may be linked or duplicate with bug #644168
2) I remember a discussion saying that there were several kinds of picture attributes for rotation (EXIF, ...), so I suppose this bug comes from the fact that EOG and Shotwell don't use the same way of rotating pictures. There should be a standard way of rotating pictures to avoid such problems....
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in eog: | |
| status: | Unknown → New |
| Sense Egbert Hofstede (sense) wrote | #1 |
| Changed in eog: | |
| importance: | Unknown → Undecided |
| Changed in shotwell: | |
| importance: | Undecided → Unknown |
| status: | New → Unknown |
| affects: | hundredpapercuts → null |
| Changed in null: | |
| status: | New → Invalid |
Thank you for taking the time to report this issue. However, I am rejecting this as a paper cut because a paper cut is a small usability issue in default or featured applications that are easy to install. From the conversation of the upstream developers it seems that this issue is complex, affecting multiple applications, and is not trivial to fix. Therefore it is not a paper cut.
This issue also is a duplicate of another bug report, bug #644168. It is probably better to have one bug report for all applications where this can go wrong. Please follow the conversation there from now on. Thanks!