Can't browse network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: gvfs
gil@UbNb:~$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
-------
gvfsd-smb-browse ID 1870
Could not display "network:///".
Error: DBus error org.freedesktop
Please select another viewer and try again.
-------
Networking has been broken in Ubuntu for at least a couple of years, in the sense that clicking on the Network item in Nautilus did not open up the network. It was possible to somewhat fix this by editing smb.conf, but it was quirky, and you could frequently see only Windows computers, not other Linux computers..
In the early Alpha versions of 10.10 this was entirely fixed, Network opened up instantly, all I would have to edit was the workgroup name and even that was not really required. I just downloaded Ubuntu 10.10 Beta [and a couple of later daily builds] and now it is even more broken, click on network and it hangs for a couple of minutes and gives a message that the wrong application is being used. BTW I have installed Samba. Also if I go to System/
So today I reinstalled the August 25 Daily build, and was ecstatic to see how nicely and instantly the network opened up,[several windows machines and two Ubuntu machines] but alas after I updated Ubuntu it was broken again.
I had just talked a small business client of mine into letting me put Ubuntu on two of his computers, but now I will have to put that on hold until this is fixed, as access to the network is essential to him.
Will someone PLEASE fix this.
Thanks
Gil Seward
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gvfs-backends 1.6.3-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Fri Sep 10 23:07:13 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100824)
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
SourcePackage: gvfs
This bug was fixed by an upgrade I was downloading as I sent this bug report.