• Nautilus tries to connect, but fails.


    Hello guys,
    I have been using this wonderful distro for quite some time now, one thing starts to annoy me though. Everytime I want to inspect my journal i see a lot of messages produced by nautilus. It seems like every second it tries to connect to something, but fails and logs the warning out to the logs. It is practically not a problem, just annoying to look at journalctl -f

    Jan 08 14:29:15 t440 dbus[444]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    Jan 08 14:29:15 t440 systemd[1]: Starting Network Manager Script Dispatcher Service...
    Jan 08 14:29:15 t440 dbus[444]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Jan 08 14:29:15 t440 systemd[1]: Started Network Manager Script Dispatcher Service.
    Jan 08 14:29:15 t440 nm-dispatcher[2298]: req:1 'dhcp6-change' [wlp3s0]: new request (1 scripts)
    Jan 08 14:29:15 t440 nm-dispatcher[2298]: req:1 'dhcp6-change' [wlp3s0]: start running ordered scripts...
    Jan 08 14:29:22 t440 dbus-daemon[755]: Activating service name='org.gnome.Nautilus'
    Jan 08 14:29:22 t440 dbus-daemon[755]: Successfully activated service 'org.gnome.Nautilus'
    Jan 08 14:29:22 t440 dbus[444]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    Jan 08 14:29:22 t440 systemd[1]: Starting Hostname Service...
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:22 t440 dbus[444]: [system] Successfully activated service 'org.freedesktop.hostname1'
    Jan 08 14:29:22 t440 systemd[1]: Started Hostname Service.
    Jan 08 14:29:23 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:24 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:25 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:26 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:27 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:28 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:29 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:30 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:31 t440 nautilus[2305]: connect() failed
    Jan 08 14:29:32 t440 nautilus[2305]: connect() failed
    

    This is the log after I start nautilus and then the log message nautilus[2305]: connect() failed appears every second in the journal.
    I don’t know how to fix it, I don’t know what nautilus tries to connect to. If anyone has any idea, please share your thoughts :blush:

    Best regards

  • Hi,

    What do you get if you run it from a terminal?

    Do you have some kind of connection established (a windows smb share, a nfs share, …) ?

  • Bild Text
    Do you have anything here?

    Normaly nautilus do not connect autmaticly to networks, if you do not do somethink to let nautilus do so…

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @karasu
    Thanks for your quick reply :blush:
    Starting nautilus from terminal gives me:

    (nautilus:3614): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
    
    (nautilus:3614): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
    

    Starting with sudo gives:

    (nautilus:3787): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
    
    (nautilus:3787): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed
    
    (nautilus:3787): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=b1a7e3b7da284c43baab46e6f4c6ba85 --binary-syntax --close-stderr': Child process exited with code 1
    
    (nautilus:3787): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=b1a7e3b7da284c43baab46e6f4c6ba85 --binary-syntax --close-stderr': Child process exited with code 1
    
    (nautilus:3787): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
    
    (nautilus:3787): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=b1a7e3b7da284c43baab46e6f4c6ba85 --binary-syntax --close-stderr': Child process exited with code 1
    
    ** (nautilus:3787): WARNING **: connect() failed
    
    ** (nautilus:3787): WARNING **: connect() failed
    
    ** (nautilus:3787): WARNING **: connect() failed
    
    ** (nautilus:3787): WARNING **: connect() failed
    
    ** (nautilus:3787): WARNING **: connect() failed
    
    ** (nautilus:3787): WARNING **: connect() failed
    
    ** (nautilus:3787): WARNING **: connect() failed
    

    I have no connection established. No network storage!

  • @joekamprad That’s the thing. I cannot remember telling nautilus to connect to anything.
    0_1483911894236_Screenshot from 2017-01-08 22-33-08.png

    The only thing I can find on the internet is this thing on fedora’s forum.

  • I think it is not network connection then it should be something failed with a system service like dbus e.t.c.

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

fails16 nautilus21 connect19 tries1 Posts 6Views 864
Log in to reply