When I launch nautilus from terminal the following error is printed and nautilus doesn't open up.

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

(nautilus:25179): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Could not register the application: Timeout was reached

(nautilus:25179): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(nautilus:25179): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:25179): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

What could be the problem??

share|improve this question
up vote 52 down vote accepted

This answer by cortopy in ask.fedoraproject.org, worked for me.

I've been experiencing a similar problem today, only I couldn't open nautilus at all. So I'm wondering if this is due to some recent update clash.

This isn't a likely solution, but at least it allows me to carry on as normal.

First thing to try is sudo nautilus in a terminal. If it works, then it may mean that there is something wrong with active nautilus processess for your current user.

To be able to restart nautilus properly, do the following:

  1. See what nautilus processes are running :
    ps aux | grep nautilus
  2. Kill all nautilus processes you see :
    sudo kill PIDNUMBER
  3. Restart nautilus :
    nautilus -q
share|improve this answer
1  
Useful, but this is a workaround, but not a real answer... – Pisu Sep 27 '16 at 14:31

Please type in Terminal:

sudo killall nautilus && (nautilus &)

This command restarts the Nautilus app.

This bug has been reported here: Nautilus does not start

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.