Nautilus does not start on 16.04

Using stock Nautilus after a dist-upgrade from the latest Daily, I am unable to replicate this. The same error output indicated by the original post of the bug shows, but Nautilus pops up without issue.

The only difference between what is filed in this bug and the 'default' I have is that in the .desktop file at `/etc/xdg/autostart/nautilus-autostart.desktop`, I have `display=true` where the OP has `display=false`.

Try editing `/etc/xdg/autostart/nautilus-autostart.desktop` to have `display=true` just to test the 'default' setup, and see if it works then?

Correction, I have 'NoDisplay=true' in the default, not 'display=true'. However, the default install "just works", so I'm not able to do any confirmation on the issue. (Marking Incomplete though as it needs more information or people to test to confirm)

sudo apt-get update && sudo apt-get upgrade and a reboot fixxed the issue, nautilus back in action...

Temporarily fix it by Restart or by:
sudo killall nautilus && setsid nautilus

I am experiencing the same issue on an up-to-date Ubuntu 16.04 install.

It seems to happen randomly. Nautilus doesn't launch and gives the error previously reported if launched via command line. A restart fixes it temporarily.

GNOME nautilus 3.14.3
Linux 4.4.0-45-generic

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

(nautilus:18396): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Could not register the application: Timeout was reached

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

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

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

I tried killing/ending the nautilus process and the whole X/unity session froze.

Fixed for me after sudo apt-get update && sudo apt-get upgrade and a reboot

If you are experiencing this bug after upgrading the package, please set status back to "confirmed".

Ups. It just happened again after the upgrade. So it's not solved by the upgrade

It still happens from time to time, and my system is up to date.

Happens to me too (Ubuntu 16.10, updated from 16.04 whit worked fine. System is up to date).
I can use nautilus on my local PC but cannot acces my network devices/shares.
nautils just 'hangs' (= keeps showing the spinning mouse pointer)

After closing nautilus is saw the nautilus process is still running

ps -aux |grep nautilus shows:
<user> 9446 6.2 0.4 1193092 75000 ? Sl 02:22 0:06 /usr/bin/nautilus --gapplication-service

now starting nautilus in the terminal shows:
(nautilus:9576): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
(nautilus:9576): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
(yep, twice)

killing nautilus and starting from the terminal gives:
(nautilus:9639): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist

I do not know if that is related.

My nautilus version is:
nautilus:
  Installed: 1:3.20.3-1ubuntu3.1

Resetting to "Confirmed", because Richard and Daniele stated to get this issue with updated systems.

Just found out, that I am lacking the rights to do so. Sorry.

I'm using up-to-date ubuntu 16.04

I've seen this issue for the first time, after upgrading to 4.8 HWE kernel, including xorg-xserver hwe. Kernel is 4.8.0-36-generic

Syslog says:

Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

Bug still present after applying said fix.

Still happening randomly on an up-to-date Ubuntu 16.04.

Now killing the nautilus process solves the issue temporarily, but it takes some time for nautilus to start again even after killing the process.

I am running 17.04 for a few month and do not have this problem anymore.
My current version is: nautilus (1:3.20.4-0ubuntu2)

Bug exist on Ubuntu 16.04 (fully updated as at 21 July 2017),

File Manager opens fine but shows bug in terminal after running : gksu nautilus

Bug message is same as above:

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

Bug exists on Ubuntu 16.04:

(nautilus:3909): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
(nautilus:3909): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
(nautilus:3909): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
(nautilus:3909): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(nautilus:3909): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

nautilus --version
GNOME nautilus 3.14.3
nautilus is already the newest version (1:3.18.4.is.3.14.3-0ubuntu6).

Using updated ubuntu 16.04

When using nautilus /media/user_name/drive_name
to access drive_name I get

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

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

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

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

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

Version: GNOME nautilus 3.14.3

Just checked my `/etc/xdg/autostart/nautilus-autostart.desktop`
The default and current value for NoDisplay is:
NoDisplay=true

However with the same problem, still trying to figure out the possible causes.

This bug also affects

lsb_release -a
    LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
    Distributor ID: Ubuntu
    Description: Ubuntu 16.04.5 LTS
    Release: 16.04
    Codename: xenial

apt policy nautilus
    nautilus:
      Installed: 1:3.18.4.is.3.14.3-0ubuntu6
      Candidate: 1:3.18.4.is.3.14.3-0ubuntu6