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 712273 - Bookmarks using network protocols (sftp, smb, etc) only show up in sidebar after manually connecting to server
Bookmarks using network protocols (sftp, smb, etc) only show up in sidebar af...
Status: RESOLVED DUPLICATE of bug 711548
Product: nautilus
Classification: Core
Component: Bookmarks
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-14 07:28 UTC by kristian
Modified: 2013-11-14 15:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kristian 2013-11-14 07:28:55 UTC 
Stolen from https://bugzilla.redhat.com/show_bug.cgi?id=1016785 (Have same problem)
Michael Knepher 2013-10-08 12:57:06 EDT

Description of problem:
I have a number of nautilus bookmarks pointing to sftp and smb locations. After upgrading to Fedora 20, these bookmarks do not show up in the nautilus sidepane, though they are still listed in the bookmarks window (Files -> Bookmarks). Only local folder bookmarks are shown. If I select "Connect to Server" and connect to one of these locations, the bookmark appears in the sidepane. Disconnecting from the network section causes the bookmark to disappear.

Version-Release number of selected component (if applicable):
3.10.0-1.fc20

How reproducible:
Always

Actual results:
Bookmarks for networked locations only appear in the sidepane after they are connected to manually using "Connect to Server"

Expected results:
Bookmarks for networked locations should always appear in the sidepane.
Comment 1 António Fernandes 2013-11-14 15:34:18 UTC 
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. It should be solved in the next software version. You may want to check for a software upgrade.

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