After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331311 - smb:// location is empty
smb:// location is empty
Status: RESOLVED FIXED
Product: gnome-vfs
Classification: Deprecated
Component: Module: smb
2.12.x
Other All
: Normal major
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-15 19:06 UTC by Sam Morris
Modified: 2006-03-05 16:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
packet dump while running gnomevfs-ls (4.14 KB, application/octet-stream)
2006-02-15 20:35 UTC, Sam Morris
Details

Description Sam Morris 2006-02-15 19:06:39 UTC
Please describe the problem:
(forwarded from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352473>)

No servers appear in the smb:// location. There are no errors from
nautilus/gnomevfs-info/gnomevfs-ls.

Network browsing with other means (smbclient/nmblookup, smbnetfs and network
browsing from within Windows itself) works fine.

Steps to reproduce:
$ gnomevfs-ls smb://
$

Actual results:


Expected results:


Does this happen every time?


Other information:
This is on Debian with gnome-vfs 2.12.2 and both libsmbclient 3.0.21a and 3.0.21b.
Comment 1 Josselin Mouette 2006-02-15 20:03:47 UTC
This is certainly because the user has forgotten to install the libgnomevfs2-extras package.
Comment 2 Sam Morris 2006-02-15 20:35:20 UTC
Created attachment 59428 [details]
packet dump while running gnomevfs-ls

I used tcpdump to capture the packets sent out from my machine while running "gnomevfs-ls smb://". It seems that gnome-vfs on my machine is not bothering to ask me for authentication details.

When I try to browse the network from an Ubuntu machine (gnome-vfs 2.12.1; libsmbclient 3.0.14a) I am asked for my logon details as usual.
Comment 3 Sam Morris 2006-02-15 20:39:27 UTC
Downgrading libsmbclient to version 3.0.14a fixed this problem, so the bug lies either within a later version of libsmbclient itself, or in gnome-vfs and its interaction with that library.
Comment 4 Federico Mena Quintero 2006-02-20 21:15:49 UTC
This is a bug in libsmbclient.  Versions close to 3.0.21a made the default workgroup not be propagated correctly to the smbcctx structure.  This is fixed in the newer versions.

[You don't see anything in "smb://" because that URI queries for machines in the the default workgroup.]
Comment 5 Federico Mena Quintero 2006-02-20 21:38:11 UTC
Sorry, got confused with another bug.

Can you please try the patch I sent to the mailing list?  It is here:
http://mail.gnome.org/archives/gnome-vfs-list/2006-February/msg00033.html
Comment 6 Sam Morris 2006-02-20 22:45:25 UTC
Will the patch apply to 2.12.2?

 $ patch -p0 --dry-run < debian/patches/20_fix_smb.patch
 patching file modules/smb-method.c
 Hunk #29 FAILED at 929.
 Hunk #37 FAILED at 1164.
 2 out of 116 hunks FAILED -- saving rejects to file modules/smb-method.c.rej

I've skimmed over the affected hunks but can't spot what is screwing the process up. Maybe whitespace stuff?
Comment 7 Sebastien Bacher 2006-02-21 08:25:39 UTC
Federico, the patch doesn't fix that issue ...
Comment 8 Stef Walter 2006-02-28 15:56:19 UTC
I've just looked into this, and it seems to be a problem with the dapper packages for libgnomevfs2 (and related). I experienced the same problem on my dapper box: Listing smb:// returned nothing. 

This is with libsmbclient 3.0.21b (which seems to be the latest in dapper).

After I built and installed a stock gnome-vfs CVS HEAD, (and restarted gnome-vfs-daemon) everything worked again. I didn't touch libsmbclient, only gnome-vfs. 

What are the patches that Ubuntu includes in the libgnomevfs2 package? It's likely one of them is breaking this functionality. If you post them, I can look them over. 

Comment 9 Stef Walter 2006-02-28 15:58:17 UTC
(In reply to comment #2)
> I used tcpdump to capture the packets sent out from my machine while running
> "gnomevfs-ls smb://". It seems that gnome-vfs on my machine is not bothering to
> ask me for authentication details.

The gnomevfs-* don't ask for authentication. Which should probably be fixed by someone... It would need to prompt via the console, since gnome-vfs can't depend on the whole libgnomeui and gnome-keyring authentication system.
Comment 10 Sebastien Bacher 2006-02-28 17:16:29 UTC
In fact it seems that alex commit from this morning fixes the issue:

2006-02-28  Alexander Larsson  <alexl@redhat.com>

	* modules/smb-method.c:
	Try to log in anonymously when possible.
	This fixes problems browsing workgroups and gives
	a lot less auth dialogs. However, it means you must put
	the username in the uri if you want to log in with a username
	on a share where anon login is allowed.
	Patch from Nate Nielsen

With it smb:// browsing works fine again
Comment 11 Sam Morris 2006-03-05 16:05:57 UTC
Is there an easy way for me to test this? Can I install just the CVS version of gnome-vfs and its minimal dependancies somewhere to find out?
Comment 12 Sam Morris 2006-03-05 16:12:07 UTC
Oh, and why _did_ this work with libsmbclient 3.0.14? And is it possible for Nautilus to log in anonymously by default, but prompt the user for authentication once he runs into an 'access denied' error?
Comment 13 Stef Walter 2006-03-05 16:52:30 UTC
(In reply to comment #11)
> Is there an easy way for me to test this? Can I install just the CVS version of
> gnome-vfs and its minimal dependancies somewhere to find out?

Yup.

(In reply to comment #12)
> And is it possible for
> Nautilus to log in anonymously by default, but prompt the user for
> authentication once he runs into an 'access denied' error?

Yup, that's what happens.

Marking as fixed. If you continue to have problems feel free to reopen with more information.