Dbus error when clicking network icon in nautilus - Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply

[stop]

Binary package hint: dbus

When I click the network icon to browse the contents of the network I get maximum cpu usage by gvfsd-smb-brows and and the following error:
Could not display "network:///".
Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Please select another viewer and try again.

The process has to be killed manually, it does not seem to stop by itself. Also, I can't browse the network....

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: dbus 1.2.24-3ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Sep 6 18:38:45 2010
EcryptfsInUse: Yes
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: dbus

[exploder91 (d-cosner)]

Same error here clicking on "Network" in the "Places" menu.

Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Please select another viewer and try again.

CPU usage goes to 100% on one core and stays like that until I reboot.

[Jelmer Vernooij (jelmer)]

Reassigning - Samba does not provide any DBus interfaces, and gvfsd-smb-browse is part of gvfs.

While the latter uses libsmbclient (which is part of Samba) I have not seen any indication that this would in fact be a bug in libsmbclient.

[Robert Irelan (rirelan)]

For me, this bug started with the updates on Labor Day. As with the poster before, the gvfsd-smb and gvfsd-smb-browse processes spin at 100% CPU usage. On the other hand, mounting those same shares using mount.cifs works fine.

[Victor Vargas (kamus)]

Confirmed under Ubuntu Maverick with all updates to date (killall -HUP nautilus don't work for me as possible work around).

[Victor Vargas (kamus)]

ok, I have checked at /var/log/auth.log and I noticed that apparmor has output some interesting lines such:

dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.99" (uid=1000 pid=2177 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.6" (uid=0 pid=600 comm="/usr/sbin/console-kit-daemon))

Comparing apparmod.d/abstractions/dbus (dbus-session) between a Ubuntu Lucid version are differences. so I have added the missing line:

#Machine id
/var/lib/dbus/machine-id r,

looks like is working again for me.

[Sebastien Bacher (seb128)]

could be a duplicate of bug #631960

[Victor Vargas (kamus)]

too soon for speak, don't work any more after reboot the system :(

[Pedro Villavicencio (pedro)]

could somebody please try the new gvfs package( 1.6.3-0ubuntu2 ) which was upload just a few hours ago and see if you can reproduce the issue after installed it ? Please make sure to reboot your system after the installation, thanks in advance.

[Victor Vargas (kamus)]

update works fine for me too! Thanks.

[riltondigger (riltondigger)]

Now works fine to me

[igi (igor-cali)]

I cannot get the update running update-manager.

[igi (igor-cali)]

Now I did it. It works for me too now. I propose the mark as Fix Released.

[Robert Irelan (rirelan)]

Works for me.

[Oliver Joos (oliver-joos)]

I think I have this bug in Lucid LTS which would not be a surprise, because Lucid has gvfs 1.6.0+git20100414-0ubuntu1 at the moment. Can someone else confirm this bug in Lucid?

As I am pretty sure already, I opened bug 684286 to backport the fix to Lucid.

[Evan Broder (broder)]

Oliver, I'm a bit confused. As I understand it, the bug described here was the result of switching gconf to use gdbus, and that change was only introduced in Maverick. If I am understanding this correctly, then you could not be experiencing this particular bug on Lucid, even if you're experiencing the same symptoms. Can you please open a separate bug against the gvfs package in Ubuntu (not against lucid-backports) so that we can track it more appropriately?

[Oliver Joos (oliver-joos)]

You're right: only the symptoms I saw are the same as this bug shows. And bug 631960 sounds similar but I did not see excessive CPU load.

I only use NFS, so I am not affected. The bug I saw bites two of my friends (independently) who both use 10.04 and a NAS with samba. Next time I meet one of them we'll try to find out more details and then open a new bug.

Thanks for your clarification!