Bug 789164

Summary:	Shotwell shows pictures in random order
Product:	[Fedora] Fedora	Reporter:	Volans <volans2000>
Component:	shotwell	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	mclasen, metherid, michel, spoyarek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 18:23:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Volans 2012-02-10 00:14:59 UTC

Description of problem:

I have a Canon camera, which gives name to the photos in the form IMG_XXXX.jpg (Example, IMG_0063.jpg). When I open the folder where those images are stored (doesn't matter if in the camera or in the PC, Shotwell doesn't follow a logical order. It shows first IMG_0063.jpg, then IMG_0067.jpg, then IMG_0083.jpg, then back again to IMG_0061.jpg.... (Just an example).

Makes it very hard to organize and upload my photos like that. I don't think it should be a normal behaviour of the program.

Version-Release number of selected component (if applicable):

Shotwell 0.10.1

How reproducible:

Just get a Canon camera, and try it... Perhaps it also happens by just naming some pictures in a folder, with that name form...

  
Actual results:

Chaos


Expected results:

User getting frustrated

Comment 1 Volans 2012-07-26 15:14:22 UTC

This bug disappeared, when I installed Fedora 17. Solved as far I know.

Comment 2 Fedora End Of Life 2013-01-16 15:29:34 UTC

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

Comment 3 Fedora End Of Life 2013-02-13 18:23:51 UTC

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.