When I run the command nautilus &, the file browser opens correctly, but prints the following errors and doesn't return control to the terminal (e.g. what the & should do):

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

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

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

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

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

What's going on?

EDIT: To clarify, the issue is that gedit doesn't get detatched when I use the &.

  • 2
    You can ignore these warnings. But remember to never run sudo nautilus!
    – edwinksl
    Sep 21, 2016 at 7:22
  • 1
    Right @edwinksl, instead use gksudo nautilus for root access
    – Benny
    Sep 21, 2016 at 7:51
  • 2
    For admim level stuff in nautilus there's a plugin for than, nautilus-admin , so that can be an alternative as well Sep 21, 2016 at 7:56
  • @edwinksl, why not sudo nautilus, and use gksudo nautilus instead? Cheers, Al
    – heynnema
    Sep 21, 2016 at 16:55
  • @heynnema Because there's a serious risk of breaking userspace permissions.
    – user589808
    Oct 2, 2016 at 23:25

2 Answers 2


Nautilus is running fine , there are some warnings but they are not a problem.

If you want it to detatch when you run it stick an & on the end

nautilus &
  • But that's the issue, when I stick an & at the end it doesn't detatch!
    – Edoardo
    Sep 21, 2016 at 7:39
  • It probably has detached, hit enter and the prompt will appear
    – Amias
    Sep 21, 2016 at 7:40
  • Oh. Fair enough
    – Edoardo
    Sep 21, 2016 at 7:42
  • Use nohup nautilus 2>&1 > /dev/null & . This sends command line output to black hole and returns control to terminal Sep 21, 2016 at 7:55
  • Nohup is a bad idea , it will try to keep it running after the terminal or xsession closes. Only use nohup for remote CLI not local GUI apps.
    – Amias
    Sep 21, 2016 at 10:06

You can also add the following to your .bash_alias

alias nautilus='nautilus >/dev/null 2>&1'

so that all the output is no longer visible on the command line when you call nautilus.

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.