Bug 1016785

Summary: Bookmarks using network protocols (sftp, smb, etc) only show up in sidebar after manually connecting to server
Product: [Fedora] Fedora Reporter: Michael Knepher <mknepher>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ccecchi, mclasen, niklasdoose, ofp_freak, pascal.schott, stefan.kirrmann, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-22 17:32:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Knepher 2013-10-08 16:57:06 UTC
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 Sighter 2013-11-13 17:59:28 UTC
Confirmed here on arch linux too.

@Michael Knepher maybe you can throw the bug on the nautilus bugtracker.

These nautilus guys are driving me crazy :)

Comment 2 Michael Knepher 2013-11-22 17:32:22 UTC
Upstream fix to https://bugzilla.gnome.org/show_bug.cgi?id=711548 seems to have taken care of this. Closing.