"Timeout while waiting for mount to appear" when mounting NFS

Bug #871385 reported by Cory Maccarrone on 2011-10-09
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Low
Unassigned

Bug Description

I've got a couple NFS mounts in my /etc/fstab, set up to be user-mountable. These mounts show up as network mountpoints in Nautilus's computer:// location, which I can click on to mount. When I do click on them, nautilus successfully mounts the mountpoint -- it appears as a new harddisk in the same computer:// view (right next to the original icon I clicked). However, Nautilus then doesn't switch my view to that location, and after a few seconds pops up a message, "Unable to mount location: Timeout waiting for mount to appear".

After all this, I can manually click on the newly created icon and browse the drive.

Further, double-clicking on the original icon while the mount is already there causes nautilus to pop up a message, "mount.nfs: <location> is busy or already mounted". What I expect to happen is that this takes me to the view of the root of the mount.

Optimally, there shouldn't be two icons either.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sun Oct 9 10:13:05 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
XsessionErrors:
 (nautilus:1645): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:1645): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (dropbox:1670): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
 (npviewer.bin:2276): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so

Cory Maccarrone (darkstar6262) wrote :
Changed in nautilus (Ubuntu):
importance: Undecided → Low
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Paul Gevers (paul-climbing) wrote :

A friend of mine has the same error, while he is using xubuntu and mounts via gigolo. He also has the problem in Thunar and running Ubuntu Unity before he upgraded. So I believe the problem is in nfs-common and not specifically in nautilus.

Just for the record, his /etc/fstab line are:
192.168.0.102:/share/MD0_DATA/Public /home/toon/public nfs noauto,user,proto=tcp 0 0

Nicolas Boulesteix (noxx-free) wrote :

I experienced the same exactly behaviour with precise and NFS mount.

Previously I used autofs to mount NFS share, but with precise, autofs give very poor performance (multiple freeze of my desktop when NFS was used).

here my fstab line for yhe NFS share :

192.168.0.12:/volume1/public /media/nas/public nfs defaults,user,noauto,noatime,intr,udp 0 0

Nicolas Tanter (nicolas-tanter) wrote :

On Ubuntu 12.04, the "" error message disappears when adding a trailing slash to the server share path :

192.168.0.250:/volume1/music/ /media/Music nfs defaults,noauto,users 0 0

Nicolas Tanter (nicolas-tanter) wrote :

Edit : sorry, I forgot to paste the error message

On Ubuntu 12.04, the "Timeout waiting for mount to appear" error message disappears when adding a trailing slash to the server share path :

192.168.0.250:/volume1/music/ /media/Music nfs defaults,noauto,users 0 0

Cory Maccarrone (darkstar6262) wrote :

Confirmed, adding the trailing slash makes everything work wonderfully.

Valentin Crone (va-crone) wrote :

I have the same bug on Ubuntu 12.04 LTS with nautilus 3.4.2.

Sebastien Bacher (seb128) wrote :

There has been no activity here or mention of similar issues in years and it's likely resolved, closing but feel free to open a new report if you still have problems in newer versions

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers