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 416118 - EOG order of displaying images is different from Nautilus'
EOG order of displaying images is different from Nautilus'
Status: RESOLVED DUPLICATE of bug 340957
Product: eog
Classification: Core
Component: general
2.17.x
Other All
: Normal minor
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-08 16:53 UTC by Matteo Settenvini
Modified: 2007-03-08 17:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Matteo Settenvini 2007-03-08 16:53:40 UTC
Please describe the problem:
If you've got a folder with a gallery of images numbered like: 
{ image1.jpg, image2.jpg, ..., image10.jpg, image11.jpg, ..., image20.jpg, ... }
and you open it in Nautilus, the images are ordered as shown above.

However, EOG displays them in alphabetical order:
{ image1.jpg, image10.jpg, image11.jpg, ..., image2.jpg, image20.jpg, ... }

This is quite annoying if you're trying to read a book/comics with eog. Also, it's inconsistent with Nautilus behaviour.

Steps to reproduce:
1. Download an image from the internet, and put it in an empty folder. Call it "image1.jpg"
2. "for i in `seq 2 30`; do cp image1.jpg image$i.jpg; done"
3. Open the folder in Nautilus: you'll see it's ordered correctly
4. Open the first image in EOG and watch the titlebar for the filename. Now try advancing.


Actual results:
Images in EOG are ordered in alphanumerical order.

Expected results:
Images shown in EOG are ordered as in Nautilus.

Does this happen every time?
Yeah.

Other information:
Comment 1 Claudio Saavedra 2007-03-08 17:05:22 UTC
This is fixed as of 2.15.3.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. You may want to check for a software upgrade.

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