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 597060 - The list of hosts under network:/// is often out of date
The list of hosts under network:/// is often out of date
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: network backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-10-02 01:08 UTC by Francesco Negri
Modified: 2018-09-21 16:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Francesco Negri 2009-10-02 01:08:18 UTC
The list of hosts under network:/// is often out of date, containing hosts that no longer exist and missing some hosts that have recently joined the smb network.

I can see an updated list going to smb:///, where I see a "workgroup" icon, and then under smb://workgroup/, where I see the full list of available hosts.

I'm reporting this bug upstream from Ubuntu's bugtracker:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/248839
Comment 1 James 2009-12-07 23:26:24 UTC
Seems similar to the Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=525875 . Does killing the gvfsd-network and -dnssd processes help?
Comment 2 Francesco Negri 2010-07-08 14:06:04 UTC
Hi James, sorry for the very long delay in answering, I changed job and had no longer access to the machine & network where I first noticed the issue.

I've recreated a similar situation and your suggestion seems to do the trick: after I killall gvfsd-network && killall gvfsd-dnssd, the list in network is updated.
Comment 3 James 2010-07-26 10:00:01 UTC
(In reply to comment #2)
> I've recreated a similar situation and your suggestion seems to do the trick:
> after I killall gvfsd-network && killall gvfsd-dnssd, the list in network is
> updated.

Killing these two no longer seems to do the trick for me. I have to re-negotiate the connection with Network Manager before the correct list of hosts appears in network:///.
Comment 4 James 2011-12-03 13:58:12 UTC
This is still present, as far as I can tell in GNOMEs 3.0 and 3.2. Killing the gvfsd bits still no longer works, and as far as I can tell this isn't an Avahi problem as avahi-discover always picks up new hosts.

Any progress in fixing this? It's over two years old. Surely it's not difficult to accurately re-query the Avahi-daemon as it's native tools do.
Comment 5 GNOME Infrastructure Team 2018-09-21 16:54:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/118.