nautilus Couldn't display "smb://HOST/folder/". Error: Connection timed out Please select another viewer and try again (sporadic)

[muzzamo]

Binary package hint: nautilus

In Hardy when trying to browse Windows network using places--> network nautilus hangs for a while until I get the message:

"Couldn't display "smb://myhost/myfolder/".
Error: Connection timed out
Please select another viewer and try again"

It does this only sporadically, and it only does this on only one of my 4 pcs at home, when accessing the same smb server. Only occurred after upgrading from gutsy to hardy (all other pcs have been upgraded to hardy successfully). Note that it allows you to browse at the level smb://myhost/ (ie get a list of shares) but not go any deeper (although as i said this is sporadic, sometimes it works)

I thought that this was potentially a duplicate of bug #139971, but i'm not using ldap or anything like that and also this seems to be a new regression for hardy

However, like #139971 If i right click a folder and then click "open in konquerer" the samba share can be browsed just fine.

Following a technique used in bug #139971 I did a gnomevfs-ls smb://myhost/myfolder and the contents of that folder displayed to the terminal just fine.

I Upgraded to hardy about a week ago and it has been doing it since then even as I have updated other packages. Currently using Nautlius 1:2.22.1-0ubuntu1 .

[muzzamo (murray-waters)]

I also tried adding a new user to the system (and hence getting new gnome settings) and this didn't work either.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you run "/usr/lib/gvfs/gvfsd -r" on a command line? Is the share an anonymous one? In which case could you run "/usr/lib/gvfs/gvfsd-smb host=hostname share=sharename" and note errors displayed? Does gvfs-mount smb://hostname/sharename works correctly? What about gvfs-ls on the share?

[muzzamo (murray-waters)]

Thanks Sebastien,
Output given below. It appears gvfs-mount is not yet installed. I didn't go ahead and install it as I await further instructions from you. gvfsd -r hangs.

phillip@phillip-desktop:~$ /usr/lib/gvfs/gvfsd-smb host=echelon share=TVEPS4
setting 'host' to 'echelon'
setting 'share' to 'TVEPS4'
Added new job source 0x807ac18 (GVfsBackendSmb)
Queued new job 0x807b400 (GVfsJobMount)
send_reply, failed: 1
Mount failed: Invalid mount spec

phillip@phillip-desktop:~$ gvfs-mount smb://echelon/TVEPS4
The program 'gvfs-mount' is currently not installed. You can install it by typing:
sudo apt-get install gvfs-bin
bash: gvfs-mount: command not found

phillip@phillip-desktop:~$ /usr/lib/gvfs/gvfsd -r
** hangs!! **

[muzzamo (murray-waters)]

Also it is an anonymous share, and /usr/lib/gvfs/gvfsd -r hung indefinitely (was still hung 3 hours later).

[muzzamo (murray-waters)]

let me know if you want gvfs-mount installed.

[muzzamo (murray-waters)]

Well i went ahead and installed gvfs-mount from the package gvfs-bin, and from the command line it seems to mount:

phillip@phillip-desktop:~$ gvfs-mount smb://echelon/TVEPS4
phillip@phillip-desktop:~$

But then when i click on it from the places menu, it takes quite a while then gives the above error message "Error: Connection timed out Please select another viewer and try again".

If there is any other information i can provide please let me know

[Sebastien Bacher (seb128)]

the gvfsd -r call is supposed to hang, it replaces the server so you can read the log on the command line. Is there anything displayed when you run the mount and then try to use nautilus?

[muzzamo (murray-waters)]

I ran gvfsd -r, then clicked through to one of the shares. The output below came up instantly, but nautlius gave me the "opening TVEPS4. You can stop this any time by clicking cancel" message for a while (it did this as per my original bug report too) before repeating the same message as per my original report. Nothing further showed in the output of gvfsd -r.

phillip@phillip-desktop:~$ /usr/lib/gvfs/gvfsd -r
Added new job source 0x807ac18 (GVfsBackendSmb)
Queued new job 0x807b400 (GVfsJobMount)

[Sebastien Bacher (seb128)]

could you attach gdb to gvfsd-smb and then try to open the share?

[muzzamo (murray-waters)]

Sure. How do I do that? I did a bit of googling but could you please provide precise instructions as to what needs to be done?

Thanks

[Sebastien Bacher (seb128)]

you can mount any smb share so gvfsd-smb is ran, use 'gdb --pid $(pidof gvfsd-smb)' to attach gdb to it and then type 'continue' on the gdb prompt and note gdb stops on an error then while using the share

[muzzamo (murray-waters)]

Following your instructions i did (as before):

output:
phillip@phillip-desktop:~$ /usr/lib/gvfs/gvfsd-smb host=echelon share=TVEPS4
setting 'host' to 'echelon'
setting 'share' to 'TVEPS4'
Added new job source 0x807ac18 (GVfsBackendSmb)
Queued new job 0x807b400 (GVfsJobMount)
send_reply, failed: 1
Mount failed: Invalid mount spec
phillip@phillip-desktop:~$

Once this had completed there was no gvfsd-smb process running anymore, so i cant attach gdb to it?

Instead I tried running gdb then running the program, as per my attachment. I hope this is what you were after.

[Sebastien Bacher (seb128)]

the mount doesn't work that's why there is no gvfsd-smb running where you can attach gdb. Could you mount it using nautilus, attach gdb to the running gvfsd-smb and then try to use it in nautilus?

[muzzamo (murray-waters)]

output is attached. I did this by double clicking the network share, then while nautilus was waiting for it to open (it taking a long time before timing out is a symptom of the bug) ran "gdb --pid 10531" where 10531 is the pid of the gvfsd-smb process that had just been started.

It immediately spat out most of the attached log, then after typing "continue" it went for a few more seconds before outputting the single line "[Thread 0xb7530b90 (LWP 10532) exited]".

Hope this is what you are after. If not, please let me know :-)

[Sebastien Bacher (seb128)]

there is no error displayed there

[Sebastien Bacher (seb128)]

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.