When trying to open nautilus (from the Launcher or from the Dash pressing on Files), it does not open, and the desktop aren't responding.
The output of nautilus -q (without sudo):
(nautilus:12039): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
(nautilus:12039): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Could not register the application: Timeout was reached
(nautilus:12039): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(nautilus:12039): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus:12039): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
If i use gksu nautilus it opens but with an error:
(nautilus:18320): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Currently fixing this issue by restart my PC or by restart nautilus:
sudo killall nautilus && (nautilus &)
But is just a temporary fix.
This bug has been reported here: Bug report on Nautilus in 16.04.
sudofor Nautilus? – David Foerster Nov 01 '16 at 09:27sudofrom your post now, do you get the same results withnautilus -q(withoutsudo)? (Contact me in chat if you think this is going to lead to extended discussion unsuitable for the comment section.) – David Foerster Nov 01 '16 at 09:34sudo, that would explain the problem of its not launching. Please [edit] your question and clarify whether this only happens when usingsudo. Also explain how you try to open nautilus and when you are doing it. Is it after rebooting or after waking up from suspend? – terdon Nov 01 '16 at 09:51sudoto opennautilus. i am not suspend my PC, after rebootingnautilusalways working properly, it happens once or several times a day. – Benny Nov 03 '16 at 09:36