disk mounter applet shows nfs and davfs mounts only when they are mounted

[Oliver]

Binary package hint: gnome-applets

the disk mounter shows no nfs and davfs mount points except they are mounted e.g. by a console command.
I can unmount these mounted drives and of course the icon disappears instead of showing the unmounted drive!

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * What ubuntu version do you use?

 This will help us to find and resolve the problem.

[Oliver (t.raum)]

I am running Intrepid 64bit on a Thinkpad R60.

I can always mount the entries in fstab in/by my console and the related icons appear in the diskmounter.
When unmounting them either by the disk mounter or in/by the console the related icons in the disk mounter disappear.

So this is always the case, I can reproduce this as I want....I will never see an unmounted icon for nfs or webdav and I tried now also fuse(curlftpfs) and iso9660 and it is the same here!

All in all the "disk mounter" applet makes in that state no sense, it is useless - except you call it "disk unmounter".

best regards
Oliver

[Jens Gräf (jgraef)]

I can confirm this.

OS: Intrepid amd64

Steps to reproduce:

fstab-entry:
nfs-server:/nfspath /mountpoint nfs user,noauto 0 0

Result:
Current version of drivemount-applet does not show an icon to mount that share.
Earlier versions (I think until hardy) did show an icon.

After mounting the share using
mount /mountpoint
an icon appears allowing me to unmount the share.

[Sebastien Bacher (seb128)]

could somebody having the issue and an opinion on what it should be doing open the bug on bugzilla.gnome.org?

[Sebastien Bacher (seb128)]

The bug has been sent on http://bugzilla.gnome.org/show_bug.cgi?id=572987

[Jens Gräf (jgraef)]

Now using Ubuntu 10.4, 64bit and drivemount-applet shows icons to mount nfs-shares again.

I'm not not sure when it was fixed, though.