Intrepid Ibex: Cannot access samba share "Unable to mount location"

On Thu, Jun 19, 2008 at 01:01:50AM -0000, colinstark wrote:
> Running Intrepid Ibex in a Virtualbox VM.
> When trying to access a Samba share on a Windows machine by clicking Places->Network->Windows Network->MSHOME->windowsmachine->share and after the prompt which asks for the password to access the share, I am getting the error message:
> Unable to mount location
> DBus error
> org.freedesktop.DBus.Error.InvalidArgs:
> Mountpoint already registered

Are you able to access the remote share using smbclient from the command
line ?

  status incomplete

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

Yes, I am able to access it using smbclient from the command line.

To add to the first comment, I am not able to access any shares on the Windows machine. I am, however, able to access Samba shares that are on other Linux machines. I unfortunately only have one Windows machine in the house so I can't tell whether it's this one machine or whether it's all Windows shares that it can't connect to. Hopefully this helps narrow down the problem.

Reassigning to nautilus package as smbclient works correctly.

thank you for your bug report. did that work correctly in hardy? does using gvfs-mount smb://url works correctly?

same issue here, gvfs-mount works

It works correctly in Hardy.
gvfs-mount also works.

Same error here but gvfs-mount gives the same error message "Error mounting location: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered"

I can confirm this bug. I am on a university network, and I can say this error pops up randomly (ie. meaning that some shares will mount, while others will not).
First it gives an error "Unable to mount location", while still showing in the nautilus mounts list, with an "empty" directory list.
Trying to mount again give the obvious "Mountpoint Already registered" error, which is ok.

So, the first mount attempt fails somewhere in the middle.

There is a duplicate bug #249733, which I have marked as a dup of this one. The error seems to be independent of nautilus, as it occurs when using gvfs-mount and not invoking nautilus at all.

The use of gvfs-mount smb://server/share appears to mount the share - it appears in the nautilus mount list, and an icon is placed on the desktop. However, attempts to access the share fail both using nautilus and using gvfs-ls, showing that this is an error in gvfs, which is not allowing the "mounted" share to be accessed.

The share is accessible using ~/.gvfs/"share on server"

Hope this additional information helps squash this very annoying bug in Intrepid, running on an HP Pavilion laptop, not in a virtual machine.

Everything works correctly in Hardy on the same machine, btw. This is new to Intrepid.

Adding gvfs to the list of affected packages since this really sounds like a gvfs issue rather than a nautilus issue.

Since Intrepid alpha3 (at least) none of the three methods works to mount a windows share: Nautilus sees the server, but no shares; smbclient sees no shares; gvfs-ls sees no shares. gvfs-mount says that "volume doesn't implement mount".

smbtree sees the Windows server, but times out waiting for details. nmblookup -S workgroup reports the (two - local and remote) members correctly, with the correct IP addresses.

Downgrading to gvfs-0.2.5-r1 from 0.99.3 in Gentoo helped solve the problem for me. Maybe a similar fix can be performed in Ubuntu.

same issue for me between an ubuntu 8.04 share and a my laptop on Intrepid

since the recent updates to gvfs (Intrepid, 64-bit) the Windows shares are now shown in Nautilus, but attempting to open them in Nautilus apparently fails, bringing up the password dialog twice; clicking OK the second time gives the dbus error message as above.

gvfs-ls smb://server/ lists the shares correctly, but sudo gvfs-mount smb://server/share returns the message:

Error mounting location: volume doesn't implement mount.

After this, gvfs-ls smb://server/share reports

Error: the specified location is not mounted.

The "share on server" entry does not appear in ~/.gvfs/

After attempting (and apparently failing) to mount using Nautilus, the "share on server" folder DOES appear in ~/.gvfs, and gvfs-ls smb://server/share lists the contents of the share correctly.

Hope this helps someone to track this down.......

I can confirm this bug too.
Trying to connect through "Places->Connect to server" gave me the same error message:
Could not display "smb://IP/shareddocs/".
Error: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered
Please select another viewer and try again.

However this command worked:
sudo mount -t cifs //ip/shareddocs /media/network

As for gvfs-mount, I don't know how to use it.

Just tried the commands indicated by Stephen Cradock.
I get the same for everything except for the end:
After attempting (and apparently failing) to mount using Nautilus, the "share on server" folder DOES NOT appear in ~/.gvfs, and gvfs-ls smb://server/share does NOT list the contents of the share correctly.

ii smbclient 2:3.2.0-4ubuntu3 a LanManager-like simple client for Unix
ii gvfs 0.99.4-0ubuntu1 userspace virtual filesystem - server
ii gvfs-backends 0.99.4-0ubuntu1 userspace virtual filesystem - backends
ii gvfs-bin 0.99.4-0ubuntu1 userspace virtual filesystem - binaries
ii gvfs-fuse 0.99.4-0ubuntu1 userspace virtual filesystem - fuse server
ii nautilus 1:2.23.6.1-0ubuntu1 file manager and graphical shell for GNOME
ii samba 2:3.2.0-4ubuntu3 a LanManager-like file and printer server for Unix
un samba-client <none> (no description available)
ii samba-common 2:3.2.0-4ubuntu3 Samba common files used by both the server and the client

I get this error only on secured shares. so it can be some seahorse problem or some thing like this. You can try some unsecure workaround and reconfigure your samba server with:
security=share
[your share]
guest ok=yes.

I get this on un-secured shares.

I am puzzled that samba has been updated today (August 18th) without any apparent change in the situation. It seems that this is not a samba bug, at any rate.

Is this a gvfs bug? Is it a seahorse bug (as suggested above by fishor)? Or is it something else? It is certainly, for me at least, unique to Intrepid - the same machines connect just fine using hardy.

zoidberg - that's right - you need to run gvfs-mount smb://server/share to get the folder to appear in ~/.gvfs

Once it is there you can cd into it and see, and copy, files. It still won't open using nautilus, though there is an icon on the desktop.

I did some dbus monitoring and here are some rusults. The difference betwene
working system (hardy) and not working (intrepid) ist like this:
-----------------------hardy---start---------------------------------
..............bla bla
method call sender=:1.4 -> dest=org.gtk.vfs.Daemon
path=/org/gtk/vfs/mounttracker; interface=org.gtk.vfs.MountTracker;
member=lookupMount
..............bla bla
method return sender=:1.5 -> dest=:1.4 reply_serial=23
---------------------------------end------------------------------------

------------------intrepid----start----------------------------------------
................bla bla
method call sender=:1.257 -> dest=org.gtk.vfs.Daemon
path=/org/gtk/vfs/mounttracker; interface=org.gtk.vfs.MountTracker;
member=lookupMount
................bla bla
error sender=:1.8 -> dest=:1.257
error_name=org.glib.GError.g_2Dio_2Derror_2Dquark.c16 reply_serial=43
   string "The specified location is not mounted"
-------------------------end----------------------------------------------

if i'm correct sender=:1.8 is gvfsd. So gvfsd send neutilus wrong respons.

Just throwing in a "ditto" here and subscribing...

This "seems" to be similar to a bug that started with Hardy, only now it is worse. With Hardy- while you couldn't browse shares through Nautilus, you could manually mount them using the "Connect to Server..." dialog in Places. You would get an error message about not being able to mount the volume, but the volume was actually mounted and you could then access it in Places. That doesn't seem to be possible in Intrepid Alpha 3.

After the volume shows mounted in "Places", if you double-click on it to open it- you get the following error message:

DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered

I also can't mount any authenticated shared using the "smb://server/share" syntax in nautilus.

I can't still mount my Windows shares with any of the methods.

Nautilus reports the "Mountpoint Already registered" thing. The Places menu has the same error than nautilus. And gvfs-mount (which wasn't installed by default) says this:

emilio@pcjuan:~/.gvfs$ LANG=en_US.UTF8 gvfs-mount -u 'smb:///pentium4/Documentos c'
Error finding enclosing mount: Could not find enclosing mount
emilio@pcjuan:~/.gvfs$ LANG=en_US.UTF8 gvfs-mount 'smb:///pentium4/Documentos c'
Error mounting location: La ubicación ya está montada

PS: "La ubicación ya está montada" means "The place is already mounted"

I have updated to Intreprid today and I experience exactly the same problem (DBUS error: mountpoint already registered).

However, I can access the shares from ~/.gvfs/share_folder on ip

Note, that this is not a Samba server problem since I'm accessing shares on a Windows machine. It looks like a communication problem between gvfs and nautilus. For some reason, it is trying to mount the share again instead of displaying it when using smb://ip/folder

I have the following problem, testing with Ubuntu 8.10 Alpha 4+, trying to connect to a company SMB network server share. Nautilus tells me:

----
Could not display "smb://servername/myshare$/" - Einhängen des Ortes nicht möglich.
----

This worked ok when I used 8.04. However, nautilus shows the share as mounted (gets a shortcut on the left side, as a cd would which has been inserted into a local drive). When I press the "eject" (unmount) button for this share, I sometimes get the following error message:

----
Could not display "smb://servername/myshare$/". Fehler: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered - Bitte wählen Sie einen anderen Betrachter und versuchen Sie es erneut.
----
I entered my account data the first time I tried to connect. Strangely enough, in the properties you can see how many files there are on this share and how much data there is all in all, but the file list cannot be displayed.

I reported this bug under https://bugs.launchpad.net/ubuntu/+source/samba/+bug/216465. However, going more into it, I think this was the wrong thread to report this to. Is this thread I am writing in now the right one, or should I open a new one?

#!/bin/bash
echo "Enter Server Name:"
read Server
echo "Enter Share Name:"
read Share
SMB="smb://$Server/$Share/"
DIR="$HOME/.gvfs/$Share on $Server"
/usr/bin/gvfs-mount "$SMB"
/usr/bin/nautilus "$DIR"

quick and dirty share mounting till a fix comes out.

Nice try - doesn't work for me. The script runs and leaves me with a mounted share icon, but doesn't open Nautilus. Trying to open the share by double-clicking the desktop share icon leads to the original error message - already mounted.

My apologies! After some messing around it DOES work for me.

At first running the script gave me the mount, but not the Nautilus window. I put in two extra lines to 'echo "$SMB"' and 'echo "$DIR"', and it worked.

Then I commented out (#) the two extra lines and it still worked....
Then I removed the extra lines and it still works.....!

I suspect timing - the gvfs-mount call may not generate the "$HOME/.gvfs/share on server" entry fast enough, so that Nautilus fails (silently) because the directory given doesn't appear to exist. But that's another bug......

#!/bin/bash
echo "Enter Server Name:"
read Server
echo "Enter Share Name:"
read Share
SMB="smb://$Server/$Share/"
DIR="$HOME/.gvfs/$Share on $Server"
/usr/bin/gvfs-mount "$SMB"
sleep 5
/usr/bin/nautilus "$DIR"

sleep 5 should prevent timing issues and ensure a proper mount before nautilus tries to open it

GUI version of the above script, used for mounting shares.
Workaround until an official fix is made

Put in /usr/bin

Interesting find..
The same location (share on server in Places) works 100% if accessed from a save as dialog in The GIMP.
Try to open in nautilus, and errors listed above, but no errors in save as dialog. Perhaps it is a nautilus problem, as the location appears to be mounted correctly in Places...

Same issue here. I can mount with command line but not in gnome. folder says it's mounted but I get:
DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered

:(

It works with smb4k (bad workaround, however, since it seems to have some problems with characters / encoding).

Different behaviour on my Interpid (updated today):
gfs-mount on commandline also doesn't work:
Though the nautilus shortcut will created the directory ~/.gvfs/ stays empty forever thereafter - without error message, neither on console nor in syslog.

I have this same problem. But if I use Gnome Commander rather than nautilus it works correctly.

I was very surprised when I saw above that importance is low for Nautilus, I see this as a big problem that should be fixed before 8.10 is shipped.

Assigning Milestone for gvfs, this can be considered as a blocker for intrepid.

I use fusesmb on gentoo as a workaround for the moment. Maybe something similar can be done on gentoo.

Hi, I have just marked the bug #267378 as a duplicate of this one. Agree with weaver4 that the importance of the bug is all but low. Bugs like these are the kind of things which make new users annoyed and disconcerted.
I have noticed something that might perhaps be of some use. The usual beginning: I do Places/Network/Morgenstern/E. I get the Unable to mount message, but a folder named "e on morgenstern" appears on my desktop. If I right click on that folder, the menu item "Paste into folder" is very quickly blinking.
Okay, if I can cooperate with some testing, just tell me.

I'm experiencing this on all SMB shares that I've tried to mount. Both on an upgrade from 8.04 and a fresh install of intrepid alpha-5 (and then updated).

stef@stef-laptop:~$ gvfs-mount smb://tv-tinos/Movies/
Error mounting location: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered

This bug seems to be fixed, probably by the gvfs updates today (Sep 16th 2008).

Shares on a Windows Vista server now open correctly in Nautilus.

Thank you all for the fix - whoever it was that finally fixed it!

Yeay, it actually works. Still slow as hell though, bug #259771 seems to be relevant for Intrepid as well.

Closing as Fixed

Maybe it works for Vista, but it broke every smb share on my 4 - 8.04.1 1 winXP pro SP2 network today. It also broke it on my home network with 2 ubuntu 8.04.1 and 1 WinXP sp2 machine. It was working perfectly until this morning. I have 6 Ubuntu machines and all 6 are affected.

I am curious which repositories Stephen Cradock and Thomas Novin have enabled. I did see there is something in Hardy proposed, but I don't have that one switched on my default as I tend to get unstable results with it. I have security, updates and backports enabled.

All my reports have concerned Intrepid Ibex. I have never had this problem with Hardy, even with Proposed enabled.

Same for me, this problem only existed in Intrepid. If you have this problem with Hardy I suggest you open up a new bug. Maybe it is a local problem with your installation because I have two Hardy with all updates and they both work OK.

This is an issue for me as well.

samba:
  Installed: 2:3.2.3-1ubuntu2
  Candidate: 2:3.2.3-1ubuntu2

I don't think this has ever worked in Intrepid. I don't think this is a Samba issue however, since Gnome Commander works just fine for me. Using the gvfs tools do not.

I never had this issue in Hardy, even if I enabled Hardy proposed in order to fix another bug. I agree it's not a samba issue since smbclient works fine.

I just update to 8.10 and I got the "Error: Failed to mount Windows share" again. Used to have this problem after Upgraded to Hardy. Then it was fixed. Now it is back again.

smbmount still work fine.

In my case, ~/.gvfs was made unwriteable during an upgrade. I logged out and made the directory writeable and now everything works.

I'm sorry to bother you, but I"m new to Linux, and have been using this
Ubuntu for about 1 month. This is a SERIOUS problem for me regarding
work... I must be able to browse samba shares.

Can you tell me how you 'made ~/.gvfs writeable" ? I'm sure it's CHMOD
something or other, but I just can seem to figure it out.

Thanks for your help.
-

David A. Winkley
Bowie Transportation Co
210-359-0001/210-359-0027 fax

On Mon, 2008-11-03 at 13:52 +0000, Wynand Winterbach wrote:

> In my case, ~/.gvfs was made unwriteable during an upgrade. I logged out
> and made the directory writeable and now everything works.
>

I don't think the folder protection is related to this bug.
Regards,
On Mon, 2008-11-03 at 16:50 +0000, dawinkley wrote:

> I'm sorry to bother you, but I"m new to Linux, and have been using this
> Ubuntu for about 1 month. This is a SERIOUS problem for me regarding
> work... I must be able to browse samba shares.
>
> Can you tell me how you 'made ~/.gvfs writeable" ? I'm sure it's CHMOD
> something or other, but I just can seem to figure it out.
>
> Thanks for your help.
> -
>
> David A. Winkley
> Bowie Transportation Co
> 210-359-0001/210-359-0027 fax
>
>
> On Mon, 2008-11-03 at 13:52 +0000, Wynand Winterbach wrote:
>
> > In my case, ~/.gvfs was made unwriteable during an upgrade. I logged out
> > and made the directory writeable and now everything works.
> >
>

Thanks for the response Tien. I appreciate it.
-

David A. Winkley
Bowie Transportation Co
210-359-0001/210-359-0027 fax

On Mon, 2008-11-03 at 17:08 +0000, Tien Nguyen wrote:

> I don't think the folder protection is related to this bug.
> Regards,
> On Mon, 2008-11-03 at 16:50 +0000, dawinkley wrote:
>
> > I'm sorry to bother you, but I"m new to Linux, and have been using this
> > Ubuntu for about 1 month. This is a SERIOUS problem for me regarding
> > work... I must be able to browse samba shares.
> >
> > Can you tell me how you 'made ~/.gvfs writeable" ? I'm sure it's CHMOD
> > something or other, but I just can seem to figure it out.
> >
> > Thanks for your help.
> > -
> >
> > David A. Winkley
> > Bowie Transportation Co
> > 210-359-0001/210-359-0027 fax
> >
> >
> > On Mon, 2008-11-03 at 13:52 +0000, Wynand Winterbach wrote:
> >
> > > In my case, ~/.gvfs was made unwriteable during an upgrade. I logged out
> > > and made the directory writeable and now everything works.
> > >
> >
>

@dawinkley: You'd have to do a 'sudo chmod' command, it is very unlikely that is related to the problem itself, and it is always a very-bad idea to mess with file permissions on system-created files like this. You would likely create a stability or security issue.