I'm getting the same issue in 11.04 (nautilus:12445): Unique-DBus-WARNING **: Error while sending message: 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.
I can run nautilus as sudo... none of the chatter looks to be related, but maybe someone wiser than I will see something. sudo nautilus Initializing nautilus-gdu extension Initializing nautilus-dropbox 0.6.9 ** (nautilus:17320): WARNING **: Failed to get the current CK session: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '17320' (nautilus:17320): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory Please ask your system administrator to enable user sharing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/379183 Title: nautilus Unique-DBus-WARNING Status in “nautilus” package in Ubuntu: Invalid Bug description: Binary package hint: nautilus When launching nautilus after mounted remote nfs drives have been severed from the network I get the following error message on the command line: "(nautilus:27393): Unique-DBus-WARNING **: Error while sending message: 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." The message is repeated 2 times, then the program quits. The GUI is never seen. I generally encounter this when I suspend my laptop, then move to another network where the original NFS are not available. It is possible that the act of suspension or a combination of the two is doing this. More investigation is needed. An auto unmount parameter in fstab would be kinda cool for these situations. If we have have auto mount, then why shouldn't we have auto unmount too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/379183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
