11

Nautilus won't start. When I try to launch it from a terminal, I get the following messages:

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

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

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

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

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

Could anyone suggest a way to fix this?


EDIT: Running nautilus -c produces the following output:

running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory
running nautilus_self_check_file
running nautilus_self_check_canvas_container
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory
running nautilus_self_check_file
running nautilus_self_check_canvas_container
  • Did you try turning it off and on again? – s3lph May 27 '15 at 23:01
  • try to run some tests using nautilus -c and list down the output – Maythux May 28 '15 at 6:26
  • did you do something with nautilus-scripts? – Maythux May 28 '15 at 6:28
  • @the_Seppi Yes, I've restarted. – d3pd May 28 '15 at 7:35
  • @Maythux Thanks for the suggestion. I've added that output to the question above. – d3pd May 28 '15 at 7:36
11

After killing all nautilus proccesses, the problem is fixed for me:

$ killall nautilus

It is not a great soution either but it is easier than reboot :)

3

Got the same problem (today), with the same output with nautilus -c. And as far as I know, nothing to do with nautilus-scripts.

Tried to logout, which seemed to be wrong solution. As I tried to login again, all I got was nice ubuntu background image and mouse cursor. No launcher, no top bar.

Then: CTRL+ALT+F1 (at least this worked), did login and then sudo reboot.

After reboot & login everything seems to work normally (although I got some problems with NAS NFS mounts during shutdown and restart, but I think that's another problem - probably with systemd).

Somehow this reminds me of Windows and Explorer... maybe someone knows how to handle this without reboot (I wouldn't accept reboot as a solution).

  • 1
    Agreed on all counts. Reboot "worked" for me too, but is not a solution. – Aman May 29 '15 at 22:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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