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 770896 - Bookmarks move around on the sidebar -- please display them statically
Bookmarks move around on the sidebar -- please display them statically
Status: RESOLVED DUPLICATE of bug 744589
Product: nautilus
Classification: Core
Component: Bookmarks
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-05 13:46 UTC by Greg
Modified: 2017-08-31 16:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Greg 2016-09-05 13:46:18 UTC
The bookmarked entries on my Nautilus Sidebar change positions in the Sidebar stack. I most frequently see them move after removing a USB thumb drive after having done some work.

Say my Sidebar looks like this:
1-Desktop
2-Papers
3-Projects
4-Records

I will insert a USB thumb drive, do some work and then when I eject the thumb drive and remove it from the computer I often see the bookmarks move. So they now might look like this:

1-Desktop
3-Projects
4-Records
2-Papers

I do not understand what causes this movement but it seems to most often coincide with USB thumb drive use.
Comment 1 Greg 2016-09-29 17:17:55 UTC
Here's a recent example: I have "Desktop" bookmarked in my Nautilus sidebar. I deleted a file that was in the "Desktop folder" and the bookmark named "Desktop" in the sidebar moved positions in the stack. Why are the sidebar entries moving by themselves?
Comment 2 António Fernandes 2017-08-31 16:25:01 UTC
Thanks for taking the time to report this.

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.
Comment 3 António Fernandes 2017-08-31 16:25:17 UTC

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