Bug 236119 - places menu in panel isn't the same thing as the one in nautilus
Summary: places menu in panel isn't the same thing as the one in nautilus
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-12 00:28 UTC by cje
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-12 02:19:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description cje 2007-04-12 00:28:20 UTC
Description of problem:
this has come up before in another situation but the issue this time is that
i've used 'places->connect to server' to connect to a filesystem over ssh.  then
i've bookmarked a folder there.  then i've re-opened that bookmark from the
places menu in a nautilus window (sorry, i can't remember if it asked for
keyring access at this point) and it works.  when i try to open it from the
places menu in the panel it asks for gnome-keyring access for gnome-panel. 
technically this makes sense to me but i imagine it will gonfuse the heck out of

Version-Release number of selected component (if applicable):
gnome 2.18

How reproducible:

Steps to Reproduce:
1. connect to server file system over ssh
2. bookmark a folder
3. open the folder through places from nautilus and the panel
Actual results:
need keyring access for nautilus (i think) and gnome-panel

Expected results:
keyring access only needed once if at all.

Additional info:

Comment 1 Ray Strode [halfline] 2007-04-12 02:19:39 UTC
Unfortunately, that's not likely to get fixed with the current design.  It
should get fixed automatically when we switch to gvfs, I think.

Alex, correct me if I'm wrong.

Note You need to log in before you can comment on or make changes to this bug.