error when browsing an empty workgroup on smb

I've raised the priority to match upstream's, which I agree with.

I also experience broken shares browsing, with Jaunty alpha 3 updated. Here's my output.

magicfab@edgar:~$ LANG=C /usr/lib/gvfs/gvfsd -r
### SMB-BROWSE: g_vfs_backend_smb_browse_class_init - default workgroup = '(null)'
Added new job source 0x8629868 (GVfsBackendSmbBrowse)
Queued new job 0x862bc20 (GVfsJobMount)
lp_load_ex: refreshing parameters
Initialising global parameters
params.c:OpenConfFile() - Unable to open configuration file "/home/magicfab/.smb/smb.conf":
 No such file or directory
pm_process() returned No
lp_load_ex: refreshing parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
doing parameter workgroup = WORKGROUP
doing parameter server string = %h server (Samba, Ubuntu)
doing parameter dns proxy = no
doing parameter log file = /var/log/samba/log.%m
doing parameter max log size = 1000
doing parameter syslog = 0
doing parameter panic action = /usr/share/samba/panic-action %d
doing parameter encrypt passwords = true
doing parameter passdb backend = tdbsam
doing parameter obey pam restrictions = yes
doing parameter unix password sync = yes
doing parameter passwd program = /usr/bin/passwd %u
doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
doing parameter pam password change = yes
doing parameter map to guest = bad user
doing parameter usershare allow guests = yes
pm_process() returned Yes
lp_load_ex: refreshing parameters
params.c:OpenConfFile() - Unable to open configuration file "/home/magicfab/.smb/smb.conf.append":
 No such file or directory
pm_process() returned No
added interface eth0 ip=fe80::207:e9ff:fe54:d8b4%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.25.110 bcast=192.168.25.255 netmask=255.255.255.0
Using netbios name EDGAR.
Using workgroup WORKGROUP.
### SMB-BROWSE: do_mount - URI = smb://
### SMB-BROWSE: do_mount - try #0
parsed path: fname='smb://' server='' share='' path='' options=''
SMBC_check_options(): server='' share='' path='' options=''
name_resolve_bcast: Attempting broadcast lookup for name
__MSBROWSE__<0x1>
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb: No such file or directory
tdb(unna...

Same problem here. It works if a windown machine is in the network. From 3 computers, 1 ubuntu, 1 eeebuntu and 1 vista. ubuntu <->vista works, eeebuntu->ubuntu works, but ubuntu or vista -> eeebuntu doesn't work with error "Failed to retrieve share list from server" and vista with 0x80070035. same mount error on both ubuntu and eeebuntu in absence of vista pc.
Ubuntu 8.10 and eeeBuntu 2.0 with all updates.

I cannot browse shares on vista pc without a password, although I set up vista to permit blank passwords.

Update: After reboot, Ubuntu failed to browse any share with "Failed to retrieve share list from server". Previous it was wake from standby.

Seeing the same overhere

I have experienced the same issue with Latest Jaunty update. I first noticed that when I opened Windows netwroks, it contains no items although I do have one window 2000 in the network and in the same workgroup. After I rebooted my machine, I saw the error about failed to mount the location. Right now, I either encounter the error, or no error, but 0 items listed. However, if I go to Places->connect to Server, and type in my windows 2000 machine name, shared drive, I can successfully connect to the remote server and see all the files. I can also transfer files without problem. So it looks like Samba is still working, but just the windows network browse is broken.

When I first installed Jaunty alpha 3, it worked and I could even see files in windows 7 beta shares. It broke in the recent update (happened in last week or two).

Correction from my previous post. When I first installed Jaunty Alpha 4 (not 3), I could browse Windows network. This was broken from one of the updates a few days back.

Additional information. I now cannot see ubuntu SAMBA share from a Windows 2000 machine in the workgroup.

I am getting "Failed to retrieve share list from server" with Intrepid

with gvfs (1.0.2-0ubuntu2)

have attached results of LANG=C /usr/lib/gvfs/gvfsd -r

Downgrading to version 1.0.2-0ubuntu1 solved my problem

sudo aptitude install gvfs=1.0.2-0ubuntu1

Downgrading is just a work-around, not a solution... this is a major show-stopper, guys.

Hello? Guys. Is anyone going to fix this MAJOR show stopper? This is a serious problem. Cannot browse windows networks from a modern operating system out of the box is a serious problem these days. Even trying to manually mount from gnome is a disaster. trying smb://servername/share does not even work. Something a basic as this? Come on guys.

Andy, we're all waiting for you tp provide the fix, come one guy !!!
Such comment are totally useless, so refrain next time.

no thanks

Downgrade had no effect for me and still problem about retrieving . By the way I can see my WORKGROUP at least...

Try the updates in Proposed section. It work for me. But i guess need more testing before releasing to public.

Hi Daniel, I think that it had affected my cups also... Anyway where is the Proposed section?

To enable the proposed archive for intrepid add the following line to /etc/apt/sources.list:

deb http://archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main multiverse universe

or go to System -> Administration -> Software sources and tick the intrepid-proposed box under the updates tab.

Then update system.

Hi Daniel, I've upgraded again gvfs and than installed proposed updating. Now I'm back to the retrieving error.

I've seen also cups&samba-updating in the proposed section, but still I have problem to connect to the Windows Printer via Samba. Some "updates" ago (two or three months ago) it was working fine.

Notice that: in the "New Printer" dialog box, it is very possible to browse the network up to the printer; then the verify process fails.

By browsing the network with Nautilus I got the retrieving error instead.

Thank you again for you support.

That update is for fixing other bug:

gvfs (1.0.2-0ubuntu3) intrepid-proposed; urgency=low

  * debian/patches/92_fix_davs_mounting.patch.dpatch:
    - Recover lost DAV over HTTPS mounting functionality. (LP: #222532)

Let's hope this bug will be fixed also! I notice a temporary solution by installing the fix, but I see it's only for the moment, i dont't know how it work after reboot, I used a live enviroment.

Hi Daniel,

1.0.2-0ubuntu3 from intrepid-propose does not improve the situation for me; I'm still seeing the same error message.

Cheers

With today's latest updates to jaunty, I'm no longer getting the "failed to retrieve share list from server" error when browsing "network" from nautilus and opening "windows network". Browsing my samba shares is now working correctly. I'm connecting to a buffalo linkstation running samba 2.2.8a-ja-1.1. The gvfs version listed in synaptic is 1.2.1-0ubuntu1.

Thanks

lowering the setting that's only a cosmetic issue when there is nothing to be listed

Same problem after upgrading to Jaunty.

Can't browse Windows/smb servers.
Can't connect to named servers: smb://servername/share
*Can* connect using explicit IP address: smb://<server ip address>

I'm glad I am not the only one experiencing this. Lets see, 1 Ubuntu PC (me), and four Windows PC's from the rest of my family. I can't connect via GUI, and haven't attempted via command line.

Sebastien, I agree that this may be a 'cosmetic' issue from the point of view that SMB connections still work, but the fact that most people will browse for servers and connect via network in Gnome makes it a VERY functional bug. This error happens regardless if there are servers to enumerate or not. I agree with many previous commenters that this is a show stopper. I'm not whining for a fix, just saying that ranking its importance as low is reducing its visibility for a fix.

Absolutely. I have been thinking I couldn't connect at all to my windows pc, but after a few months I discovered I can through command line.

I also spoke to someone who is pretty much anti-windows, but he still needs windows compatibility for his job as software installer on Windows machines. He told me he didn't like Linux very much as a replacement, because 'it is hard to be compatible with Windows'.

This is absolutely a showstopper, as many people have Windows pc's around in their network that need to be connected, even if they are not prepared to use the command line. Some just don't want to spend their time to learn using the command line, and just want it to work out of the box with a simple GUI. This is - if I'm right - one of the major goals of Ubuntu, and therefore this bug should be solved.

I think the importance should be high.