Duplicate Entry for Samba Mounts in Places

See also: https://bugzilla.gnome.org/show_bug.cgi?id=603628

Something interesting happened today,
I booted my Desktop machine while my nas box (Unicorn-NAS) was off...
I opened up nautilus and Unicorn-NAS was listed as an option, when I clicked on it I got the same error message as before: http://i4.photobucket.com/albums/y105/basskozz/Ubuntu/Screenshot-UntitledWindow.png
So I booted up my nas box (Unicorn-NAS) and issued "sudo mount -a" from terminal on my desktop once the nas box was up, and now in Nautilus there is still only 1 listing for Unicorn-NAS in Nautilus, and it WORKS!!!
*odd* ?

This might be related to Bug #490676

I have had this problem all through my use of Karmic (my external device is a Thecus N2200 NAS, sharing files across the network via SAMBA).

I wanted to add the comment that just tonight I did a fresh install of Lucid Lynx 10.04 BETA. The problem is still present.

Curious thing, with Lucid and likewise with Karmic ... I have two shares mounted, called 'shared' and 'media'. It was only ever the MEDIA one that was showing up twice.

I'll try changing the order of the fstab entries and see what effect this has.

This bug started to affect me after updating to maverick. It did so on both my machines, when I'm mounting the same SAMBA shares on my NAS.

My shares are not mounted on startup. A while after I have clicked on the initially existing drive symbol, I'm getting the error message "Timeout waiting for mount to appear", but a second symbol has long since appeared, and the share is accessible through that second symbol.

Interestingly enough, one of my shares is also called "media", but I have a second one with different name which also shows this odd behavior.

> This bug started to affect me after updating to maverick. It did so on
> both my machines, when I'm mounting the same SAMBA shares on my NAS.
>
> My shares are not mounted on startup. A while after I have clicked on
> the initially existing drive symbol, I'm getting the error message
> "Timeout waiting for mount to appear", but a second symbol has long
> since appeared, and the share is accessible through that second symbol.

Hi Bernhard,

Are you running Maverick 32- or 64-bit?

In my situation, I have multiple machines on Maverick 64-bit all with
the problem, however my netbook which is Maverick 32-bit does NOT have
this problem.

Interested to hear your feedback?

Cheers
Callan

I think this is something to do with the fstab line containing both "user" and "auto". I had this problem, I removed "user" from the line (no big loss in my opinion) and the issue has gone away.

This bug still exists in Natty 64-bit.

My symptoms are identical. I do have the user option in my fstab lines, however they are required to open the shares so I can't remove it.