nautilus Unique-DBus-WARNING

[Darryl Moore]

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?

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * Do you get the issue when not using nfs disks?

 This will help us to find and resolve the problem.

[no!chance (ralf-fehlau)]

same problem here. My System is unusable. Even after a reboot, no nautilus window opens.

Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

with all updates. Nautilus does not open my personal folder!

[no!chance (ralf-fehlau)]

Now, Nautilus does not start again. No error message is seen in terminal. The wait cursor is the only one I see for some time. And then, nothing.

[blairfancy (blairfancy)]

i have the same configuration and same problem:

i have setup at home nsf share with autofs, but when i m out share are not available and nautilus can't but when i disable autofs nautilus work perfectly

blairfancy

[Victor Vargas (kamus)]

Can you try to reproduce this issue in latest version of nautilus (2.28.1 ships in Karmic)? Thanks!

[PabloRQ (pablo-romeroquinteros)]

Same bug on jaunty.

(nautilus:27232): 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.

Nautilus is frozen. If I terminated it, on restart, nautilus works for a while and froze again.

[Ondřej Buriánek (zerem)]

I have successfully reproduced (and also resolved). In my case bug appeared when using application called Ubuntu Tweak by unchecking option "Show desktop icons" in "Desktop Icon Settings" section. Reverting original settings resolved this issue.
--- not using NFS, niter AutoFS
--- reporting to https://bugs.launchpad.net/ubuntu-tweak

[Brainz (me-paul-thomson)]

I can reproduce this with home directory on NFS4 (OpenSolaris server) and no problems with the mount, nautilus will hang indefinitely...

paul@pundit:~$ pwd
/data/paul
paul@pundit:~$ echo ~paul
/data/paul
paul@pundit:~$ df -h ~paul
Filesystem Size Used Avail Use% Mounted on
opensolaris:/data/paul
                      550G 21G 529G 4% /data/paul
paul@pundit:~$ egrep /data/paul /etc/fstab
opensolaris:/data/paul /data/paul nfs4 rw,soft,intr,rsize=8192,wsize=8192 0 0
paul@pundit:~$ mount | egrep /data/paul
opensolaris:/data/paul on /data/paul type nfs4 (rw,soft,intr,rsize=8192,wsize=8192,clientaddr=192.168.4.100,addr=192.168.4.3)
paul@pundit:~$ time nautilus

(nautilus:31200): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

(nautilus:31200): 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.

[Brainz (me-paul-thomson)]

A few more details on versions...

paul@pundit:~$ nautilus --check
(nautilus:31370): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory
<--- hangs indefinitely --->

paul@pundit:~$ nautilus --version
GNOME nautilus 2.28.1

paul@pundit:~$ uname -a
Linux pundit 2.6.31-9-rt #152-Ubuntu SMP PREEMPT RT Thu Oct 15 05:01:14 UTC 2009 i686 GNU/Linux

[Sebastien Bacher (seb128)]

could you try if that's still an issue in lucid?

[Martin Sin (martin-sin)]

I have the same problem in lucid version of Ubuntu. I have mounted samba shares and after resume from hibernation to disk, I cannot run Nautilus. If I try hibernation and resume without delay, it works ok, but if the time between hibernation and resume is much longer (from evening to morning next day, for example) nautilus doesn't work again. :-(

[Yuriy Voziy (yuretsz)]

This bug affects me too in Lycid
Nautilus only works with desktop icons disabled.

[Jeff (jdorenbush)]

I'm getting dbus errors with nautilus in Ubuntu 10.04. I've posted more here https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/329146

I have problems with desktop icons not showing up on startup. If I run "$ nautilus -q" I receive:
"(nautilus:2060): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)"

When trying to connect to an FTP site through nautilus I get:
"Sorry, could not display all the contents of "/ on ftp.SITENAME.com": 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."

OR

"Sorry, could not display all the contents of "/ on ftp.SITENAME.com": Cannot open data connection. Maybe your firewall prevents this?"

[Beltshassar (danieldamm)]

I got the same error, with, frozen icons and nautilus crashing, throwing the DBus-error.

The problem was solved when i removed a .svg-file (inkscape) and a few large tiff images.
The svg preview was never generated, so the problem might be connected to that.

Setup: 32bit, Ubuntu 10.04 updated from 9.10

[David Robert Lewis (afrodeity)]

I Getting this message too. I did a debug with valgrind and there is a memory leak

http://paste.ubuntu.com/437412/

20,864 bytes in 1 blocks are still reachable in loss record 3,996 of 3,996
==8805== at 0x402425F: calloc (vg_replace_malloc.c:467)
==8805== by 0x501FFB0: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.1.0)
==8805== by 0x5022E5B: xcb_connect_to_display_with_auth_info (in /usr/lib/libxcb.so.1.1.0)
==8805== by 0x502314B: xcb_connect (in /usr/lib/libxcb.so.1.1.0)
==8805== by 0x49B4102: _XConnectXCB (in /usr/lib/libX11.so.6.3.0)
==8805== by 0x499BF0E: XOpenDisplay (in /usr/lib/libX11.so.6.3.0)
==8805== by 0x45226B3: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.2000.0)
==8805== by 0x44F0654: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.2000.0)
==8805== by 0x423BC3E: ??? (in /usr/lib/libgtk-x11-2.0.so.0.2000.0)
==8805== by 0x47C9BDF: g_option_context_parse (in /lib/libglib-2.0.so.0.2400.1)
==8805== by 0x80814AC: main (nautilus-main.c:420

Nautilus fails to start properly in gnome session.

Top shows that it is maxing out the CPU

[David Robert Lewis (afrodeity)]

Can't get a full backtrace

Program received signal SIGSEGV, Segmentation fault.
0x00ed1935 in gtk_range_set_value () from /usr/lib/libgtk-x11-2.0.so.0
(gdb) backtrace full
#0 0x00ed1935 in gtk_range_set_value () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
Cannot access memory at address 0xbf940bb0
(gdb) info registers
eax 0x9e7c400 166183936
ecx 0x0 0
edx 0x0 0
ebx 0x1123ff4 17973236
esp 0xbf940bb0 0xbf940bb0
ebp 0xbf940bd8 0xbf940bd8
esi 0xfdf 4063
edi 0x0 0
eip 0xed1935 0xed1935 <gtk_range_set_value+37>
eflags 0x210202 [ IF RF ID ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51

[cybernet (cybernet2u)]

who the hack made this as low importance, sometimes i can't open nautilus as sudo, and you consider this as LOW???

[David Robert Lewis (afrodeity)]

Here is a full backtrace of sigsev problem, which also reports as the above issue.

[David Robert Lewis (afrodeity)]

Program received signal SIGSEGV, Segmentation fault.
0x002cf189 in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
(gdb) backtrace full
#0 0x002cf189 in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#1 0x080aee96 in nautilus_window_push_status (window=0x96381f0, text=0x0) at nautilus-window.c:234
        slot = 0x9846aa0
        __PRETTY_FUNCTION__ = "nautilus_window_push_status"
#2 0x080aef14 in nautilus_window_sync_status (window=0x96381f0) at nautilus-window.c:248
No locals.
#3 0x080ab679 in real_active (slot=0x9846aa0) at nautilus-window-slot.c:115
        window = 0x96381f0
#4 0x002bddcc in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#5 0x002ae92a in ?? () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#6 0x002b0252 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#7 0x002c45e6 in ?? () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#8 0x002c5db4 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#9 0x002c6085 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#10 0x080af22e in nautilus_window_constructor (type=157933840, n_construct_properties=3, construct_params=0x98a7fd8) at nautilus-window.c:694
        object = 0x96381f0
        slot = 0x2
#11 0x002b6c4c in g_object_newv () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#12 0x002b790c in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#13 0x011a7535 in gtk_widget_new () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#14 0x0806def5 in create_window (application=0x1305ff4, window_type=157933840, startup_id=0x0, screen=0x963c0c8) at nautilus-application.c:1234
        window = <value optimized out>
        __PRETTY_FUNCTION__ = "create_window"
#15 0x0806e240 in nautilus_application_present_spatial_window_with_selection (application=0x966a6c8, requesting_window=0x96a0050, startup_id=0x0, location=0x9873c98, new_selection=0x0, screen=0x963c0c8) at nautilus-application.c:1328
        window = <value optimized out>
        l = 0x0
        uri = <value optimized out>
        __PRETTY_FUNCTION__ = "nautilus_application_present_spatial_window_with_selection"
#16 0x080a5a9c in nautilus_window_slot_open_location_full (slot=0x96a6108, location=0x9873c98, mode=NAUTILUS_WINDOW_OPEN_ACCORDING_TO_MODE, flags=0, new_selection=0x0) at nautilus-window-manage-views.c:538
        window = 0x96a0050
        target_window = 0x96b5fb0
        target_slot = 0x0
        do_load_location = 158572160
        old_location = 0x96bb420
        old_uri = <value optimized out>
        new_uri = <value optimized out>
        l = <value optimized out>
        __PRETTY_FUNCTION__ = "nautilus_window_slot_open_location_full"
#17 0x08163425 in nautilus_window_slot_info_open_location (slot=0x96a6108, location=0x9873c98, mode=NAUTILUS_WINDOW_OPEN_ACCORDING_TO_MODE, flags=0, selection=0x0) at nautilus-window-slot-info.c:115
        __PRETTY_FUNCTION__ = "naut...

[Fabián Rodríguez (magicfab)]

It seems complex or unsupported thumbnail-generation of files on the desktop may be causing this. As a workaround, can anyone affected by this trying to erase/move all their desktop files to a separate directory and see if this problem persists ?

[Josh Lunsford (joshlunsford)]

I am having the same issue - I emptied my Desktop directory and still have the same issue.

(nautilus:9785): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)

[broe (erich-rupp)]

didn't work for me either

[DerekSaw (dstl1128)]

I am having the same issue as well for quite sometime.

However I accidentally 'fix' it by removing winbind. Hope it helps.

[Alex Munroe (x-launchpad-veekun-com)]

I've had the same problem with sshfs, referring to the remote machine by its winbind name. If I try to browse the mount while the machine is off the network, nautilus freezes, and any attempts to restart it give me the Unique-DBus-WARNING. I tried using Thunar instead, and it too froze as soon as I navigated to the directory /containing/ the mountpoint.

To fix it I had to:
- fusermount -uz the mountpoint
- Kill nautilus
- Stop winbindd
- Restart nautilus

Then I can restart winbindd and carry on my merry way. Still, this was extremely unobvious, and made more complicated because I didn't know the mounted machine was down (and thus causing the problem). From the sound of things, desktop thumbnails are a different problem; this is about nautilus blowing up when a network mount dies.

Using up-to-date Lucid. Had it happen a couple times over the past few months, now.

[Launchpad Janitor (janitor)]

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

[max (maxozilla)]

Can confirm I'm also experiencing this problem. Nautilus does not properly handle uncleanly disconnected sshfs mounts.

Linux version 2.6.35-27-generic (buildd@palmer) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #48-Ubuntu SMP Tue Feb 22 20:25:29 UTC 2011

[Benjamim Gois (benjamim-gois)]

This bug is happening here. When i try to load nautilus it doesn't run. I have the latest 11.04 updates. Here is the message it shows in terminal.

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.

[William Tyler Sontag (wtsontag)]

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.

[DRUNK SOB (sweatyoldballs)]

!!!!!!!!!! HOW TO FIX THIS ISSUE !!!!!!!!!! (in ubuntu desktop only)

#1 NAVIGATE TO SYSTEM>ADMINISTRATION>SYSTEM MONITOR
#2 IN THE PROCESSES TAB THERE WILL BE 2 INSTANCES OF NAUTILUS END THEM BOTH
#3 REOPEN NAUTILUS

p.s. please linux users practice giving proper instructions to save people time.
example:
I wrote this in all caps so people scrolling down can see this quickly.
I wrote handy-capable instructions so people new to linux get it, like how to get to system monitor not just open system monitor

another p.s. if you are a linux pro and had to come here to find this solution from a windows developer extend you arm all the way and slap your self :P

[macdogdaddy (macdogdaddy)]

I finally fixed this problem for myself, hopefully my experience will help others.

I've had the multi-window spawning problem with nautilus in the past (on this host/instance of ubuntu 10.04) but fixed it. And now, late last night I had this problem start up seemingly out of the blue.

     $ nautilus -q
(nautilus:28778): 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.

As with you guys I had no desktop and no ability to browse with nautilus, and the 'places' menu worked but would not initiate a nautilus browsing session when selecting 'Home Folder' (obviously). Only way to use nautilus for browsing was
     $ sudo nautilus (dont' do this!--use thunar or dolphin or something)

CPU use was running very high and I tried everything I could think of and read every post I could find. What finally ticked in my mind where the references to 'thumbnail-generation' on this thread and it dawned on me that I had used "ubuntu-tweak" to clear my thumbnail cache very near to the time that nautilus started going haywire. So I re-launched "ubuntu-tweak" and cleared my thumbnail cache once more. The results were instantaneous. Nautilus is working fine and my desktop is restored.

Things I tried that didn't work include:
     1. 'ps aux |grep nautilus' & then 'kill -KILL pid' (resulted in instant respawn with new pid)
     2. removing all files from ~/Desktop
     3. clear contents of /home/user/.local/share/gvfs-metadata
     4. reinstall gnome-session, nautilus, ubuntu-desktop, etc.
     5. sudo umount -a -t nfs

I haven't restarted the machine yet but am confident my fix will be persistent. Somewhere in the back of my cobweb filled mind is a notion that my previous multi-spawning nautilus issue on this machine was related to nautilus thumbnail cache also, but it's been a while so don't quote me on that.

While trying to find a solution it was very helpful to run
     $ ps aux |grep nautilus (observe the pid of nautilus)
     $ kill -STOP pid (enter the pid from above command)
This causes nautilus to sleep and stop maxing out the CPU.

     $ uname -a
        Linux hostname 2.6.32-47-generic #109-Ubuntu SMP Tue May 7 02:02:22 UTC 2013 x86_64 GNU/Linux
     $ cat /etc/*release
        DISTRIB_ID=Ubuntu
        DISTRIB_RELEASE=10.04
        DISTRIB_CODENAME=lucid
        DISTRIB_DESCRIPTION="Ubuntu 10.04.4 LTS"

P.S. Post #29 was very condescending and immediately unhelpful. Sober up DrunkSOB, and don't be such a dork.