Opening nautilus from command line produces errors, doesn't return control to terminal

Question

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 &.

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

score 2 · Accepted Answer · answered Sep 21 '16 at 07:20

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 &

answered Sep 21 '16 at 07:20

Amias

5,246

But that's the issue, when I stick an & at the end it doesn't detatch! – Edoardo Sep 21 '16 at 07:39
It probably has detached, hit enter and the prompt will appear – Amias Sep 21 '16 at 07:40
Oh. Fair enough – Edoardo Sep 21 '16 at 07:42
Use nohup nautilus 2>&1 > /dev/null & . This sends command line output to black hole and returns control to terminal – Sergiy Kolodyazhnyy Sep 21 '16 at 07: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 '16 at 10:06

score 0 · Answer 2 · answered Jan 19 '18 at 21:07

0

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.

answered Jan 19 '18 at 21:07

FvD

526

Opening nautilus from command line produces errors, doesn't return control to terminal

2 Answers2

Linked