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 634751 - Totem playlist does not keep order on addition of multiple files
Totem playlist does not keep order on addition of multiple files
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 636407 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-11-13 13:26 UTC by Omer Akram
Modified: 2012-04-23 17:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Omer Akram 2010-11-13 13:26:24 UTC 
"""
Steps to reproduce /on my machine/:
1. Open a folder with Nautilus with a dozen audio files, ordered by name.
2. Select all files.
3. Drag n drop them to Totem's Playlist.

What should happen:
Files are added to the playlist ordered by name.

What happens instead:
Files are added to the playlist not ordered by name.
"""

originally reported at: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/661882
Comment 1 Bastien Nocera 2010-11-13 13:46:01 UTC 
The files are added in the order they're listed in the drag'n'drop information. If you dropped the folder (as opposed to the files) then Totem would order them.

Why did you select the "browser plugin" component anyway?
Comment 2 Erik Andersen 2011-05-04 21:26:41 UTC 
For me, with .mov files, this only seems to happen when I drag in files and the playlist is long enough to need scollbars. Does this trigger it for anyone else?
Comment 3 Chris Wilson 2011-09-13 11:55:14 UTC 
This bug should be marked as a duplicate of this one: https://bugzilla.gnome.org/show_bug.cgi?id=636407
Comment 4 Cosimo Cecchi 2011-09-13 12:00:12 UTC 
*** Bug 636407 has been marked as a duplicate of this bug. ***
Comment 5 Bastien Nocera 2012-04-23 16:02:01 UTC 
*** Bug 663951 has been marked as a duplicate of this bug. ***
Comment 6 Chris Wilson 2012-04-23 17:14:37 UTC 
I've just tested this with version 3.0.1 and this appears to have been fixed in the transition to 3.x
Comment 7 Bastien Nocera 2012-04-23 17:17:27 UTC 
Great, closing.