GNOME Bugzilla – Bug 519347
opening network:/// after login doesn't work at first try
Last modified: 2008-03-04 15:05:43 UTC
1. login 2. open network:/// via the panel's menu bar (places) 3. receive this funny little message: 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. 4. do 2. again 5. see it work weird.
btw, i'm using gvfs 0.1.8, nautilus 2.21.92 and i have nothing connected to my network besides my router. quote: <awalton__> open away. my thinking is that for some people, that initial smb enumeration just takes a while and it makes it hang before it sends the dbus reply <baze> hm, i don't have any smb shares here that could be enumerated ;) in fact i don't have anything connected to my network besides my router <awalton__> that doesn't stop smb:// from taking a while... <baze> ok <awalton__> in fact, it very well might be the cause of it.
This one's strange. Does it happen from Nautilus on the first try, or just the panel? Any more insight I can get on this problem is going to solve it as it's not happening here reliably (only had it happen twice while trying a few ways to solve it).
i just tried from within nautilus and it happens there aswell. and it's every first try after a login. after that, it works.
I think the problem is rather in nautilus than in gvfs; Björn please try this command in a termaink just after accessing your session "gvfs-ls network://" and paste the output here
2008-03-04 Alexander Larsson <alexl@redhat.com> * client/gdaemonvfs.c (_g_daemon_vfs_get_mount_info_async): Bump timeout to standard gvfs time. Patch from Matthias Clasen