Unable to launch Nautilus

[Cerin]

Nautilus refuses to launch by any means.

When I launch it from the command line, I see the error:

localhost:~$ nautilus
GDBus.Error:org.freedesktop.DBus.Error.NotSupported: Application does not handle command line arguments

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

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

I recently upgraded from 14.04 to 16.04. Under 14.04, Nautilus worked fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.5-0ubuntu1~xenial1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep 18 14:04:34 2016
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'geometry' b"'1312x855+303+87'"
 b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2015-10-20 (333 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: nautilus
UpgradeStatus: Upgraded to xenial on 2016-09-16 (2 days ago)

[Cerin (chrisspen)]

This seems to be related to this bug https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1327002

Running `ps aux|grep -i nautilus|grep -v grep` showed there was a process running called `nautilus -n`. This instance seemed to somehow be blocking additional instances from launching. After I killed this, I was able to launch Nautilus as normal via the Gnome launcher and via the command line.

[Novecento (alexander-doelz)]

Seems to be the same bug as in #1593988