2

Following the answers here I can open nautilus from terminal, but not without a litany of errors.

nautilus .

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

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


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


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


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

Note that I'm running Xenial and these are a different set of errors than those reported for Trusty and Wily

Community
  • 1
Jeff Puckett
  • 1,821

1 Answers1

5

The answer was graciously provided in the comments. This only happens when Nautilus is already running. So the warning messages amount to nothing more than the obvious fact that nautilus can't be started because it's already been started.

To quit nautilus with nautilus -q and then to start it with nautilus . will cleanly open the current directory folder without the warning messages.

Note that this will launch the process from within the current shell which is usually undesirable because the console will hang until you kill the process with Ctrl+C which will in turn close the window. To avoid that mess, launch it as a detached process:

nautilus . &

Also note that if nautilus is already running, then there's no need to launch it as a separate process. This is why the warning messages appear with nautilus .

Jeff Puckett
  • 1,821