Recentemente, meu navegador nautilus se recusou a iniciar com o erro:
vincent@fitzroy:~$ nautilus --browser ~
(nautilus:18049): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
(nautilus:18049): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Could not register the application: Timeout was reached
(nautilus:18049): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(nautilus:18049): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus:18049): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
A verificação do nautilus não retorna erros:
vincent@fitzroy:~$ nautilus -c
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
Como recomendado aqui , eu reinstalei o nautilus e o nautilus-data, mas o problema permanece. Eu posso correr nautilus bem com sudo.
Outras informações que podem ser úteis ...
vincent@fitzroy:~$ echo $DISPLAY
:0
vincent@fitzroy:~$ ps -ef | grep X
root 16719 1280 4 Mar10 tty7 04:13:44 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Resolvido: Acontece que eu só precisava matar o nautilus existente processo . Irritante.