Hide Forgot
Description of problem: On F16 shotwell seems to be the default image viewer. When I go to a folder and click to visualize a picture, it starts and displays it. When I go to the next picture (either by the keyboard or the arrow on the bottom right), the picture displayed isn't the next one on the folder. I cannot make sense on which is the order with which the pictures are started. I do find this very annoying and consider it as a bug (thus the present report). Version-Release number of selected component (if applicable): $ rpm -q shotwell shotwell-0.10.1-1.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. Go to a folder with different images 2. Double click on one 3. Try to go to the next image Actual results: The image displayed isn't the next one in alphabetical order Expected results: The image displayed is the next one in alphabetical order Additional info:
Was already a problem on F15. I'm still on F15 (x86) : $ rpm -q shotwell shotwell-0.10.1-1.fc15.i686 and this bug is present. It doesn't happen on the shotwell libraries, but on pictures you view on the fly with shotwell. Looks like there's a sorting which is done somewhere, but random-looking, and there's no option to sort pictures in this mode anyway.
I confirm this bug on F16.
Confirmed here as well: $ rpm -q shotwell shotwell-0.10.1-1.fc16.x86_64
As far as I can see, they fixed it in 0.12.3. I'm using Fedora 16, and had to compile it from source -- http://yorba.org/shotwell/install.html
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.