Bug 591818 - unable to "mount" local directory over custom location
Summary: unable to "mount" local directory over custom location
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nautilus
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Tomáš Bžatek
QA Contact: desktop-bugs@redhat.com
: 619703 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-13 09:03 UTC by Lubos Kocman
Modified: 2015-03-03 22:48 UTC (History)
3 users (show)

Fixed In Version: nautilus-2.28.4-11.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-10 21:11:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
screenshot of alert (87.75 KB, image/jpeg)
2010-05-13 09:03 UTC, Lubos Kocman
no flags Details

System ID Priority Status Summary Last Updated
GNOME Bugzilla 601848 None None None Never

Description Lubos Kocman 2010-05-13 09:03:02 UTC
Description of problem:

I'm unable to "mount" more likely add local directory e.g. /var/tmp over Places-> Connect to server -> Custom Location -> uri /var/tmp

This was working on rhel 5.5. Directory appeared on the desktop with description /var/tmp over null.

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

RHEL 6.0 snapshot 2


How reproducible:

Steps to Reproduce:
1. click on gnome-panel -> Places
2. click on Connect to server
3. service type: Custom location
4. Location (URI): /var/tmp
Actual results:

You must enter a name for the server
Please enter a name and try again.

Expected results:

Directory should be visible from desktop, with information that it's mounted over null.

Additional info:

drwxrwxrwt. 3 root root 4096 May 13 10:25 /var/tmp

Comment 1 Lubos Kocman 2010-05-13 09:03:32 UTC
Created attachment 413687 [details]
screenshot of alert

Comment 3 RHEL Program Management 2010-05-13 10:24:06 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 4 Tomáš Bžatek 2010-05-20 14:44:52 UTC
This is upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=601848, posted a patch there. Waiting few days to get some feedback from upstream.

Comment 5 Tomas Pelka 2010-06-21 08:23:27 UTC
No more mentioned error. Lubos please could you confirm?

nautilus.x86_64 0:2.28.4-11.el6


Comment 6 Lubos Kocman 2010-06-21 08:45:29 UTC

the error message was changed to:

"Cannot display location "/home/". volume doesn't implement mount"

1) Which seems reasonable to me, if RedHat is not going to support this feature any more. In this case it's ok.

2) But if it should work, then I have to say that it's not working:

$ rpm -qa gvfs* nautilus

Comment 7 Lubos Kocman 2010-06-21 11:19:12 UTC
As this seems to be expected behaviour I believe that we can move this as verified.

Comment 8 Tomáš Bžatek 2010-06-24 15:02:27 UTC
OK, let's shed some light on how this works. Since transition from gnome-vfs2 to GIO the behaviour has changed a little bit. First, you shouldn't use plain "/home/" string as a URI, this should be file:///home/. This however still works in the Run dialog (Alt+F2 by default).

Second, there won't be any icon on the desktop as the local fs is always mounted, no matter what directory (we always fall back to root, except for some protocols). The philosophy has changed, you should use bookmark for this now, if you want to save the connection somehow.

So yes, this is expected behaviour. My change was to make the Custom URI entry work again.

Comment 9 Tomáš Bžatek 2010-07-30 08:54:01 UTC
*** Bug 619703 has been marked as a duplicate of this bug. ***

Comment 10 releng-rhel@redhat.com 2010-11-10 21:11:44 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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