Places side pane gets confused with nfs mounts

[jhansonxi]

Binary package hint: nautilus

I'm on Ubuntu 9.10 (Karmic Koala) using Gnome 2.28.1 and the included Nautilus. To get around brainstorm #456 I have multiple nfs mounts in fstab with noauto and user options similar to:

server:/srv/archive /home/user/server/archive nfs defaults,noauto,user 0 0

These show up as unmounted drives in the Nautilus places panel. If I click on one it mounts but usually instead of adding the up-arrow icon to the existing place to show that it is mounted, it duplicates the place at the bottom of the list and adds the arrow to the duplicate. If I click on the original place again I get an error message like "Unable to mount archive" "mount.nfs: /home/user/server/archive is busy or already mounted". Other open Nautilus windows duplicate the pane. Sometimes it will report a different nfs mount as if the places entries are mismatched from the names shown. Sometimes all unmounted places stop responding to mouse clicks (won't mount) while the mounted entries act normal. Sometimes a new Nautilus window opens when "Browse media when inserted" is checked, sometimes the existing window is used. Sometimes I'll get a DBus "NoReply" error. Sometimes a timeout error waiting for the mount to appear. Sometimes closing all the Nautilus windows (but not killing the primary Nautilus process) corrects the places panel, sometimes not even when the process is killed. Unmounting all the nfs mounts and closing the windows seems to fix it (usually).

The "usuallys" could imply a timing bug of some sort.

All of this is normal to Nautilus as there is nothing in the logs.

I also noticed that the icons for nfs and nfs4 places are different with the nfs4 icons being generic drives. I'm not sure if that is related or not.

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[jhansonxi (jhansonxi)]

https://bugzilla.gnome.org/show_bug.cgi?id=603514

[Sebastien Bacher (seb128)]

The issue has been fixed in newer versions