Nautilus misbehaviour under "unity-session" in Ubuntu 17.10

[blue239]

When the first opened instance of Nautilus is on Home folder and you try to open a second instance with the middle click on the Nautilus icon, nothing happens.

Under "ubuntu-session" there is no such deviation - another Nautilus instance is normally opened
with the middle click no matter first one being opened at the Home folder.

Under "unity-session" with the first instance being opened on the Home folder, second instance can
be repeatedly opened only in two ways:
- by right clik on Nautilus icon and selecting something from context menu
- when the first open instance is opened in any other folder than Home, midlle click
  opens second instance of Nautilus normally

[Sebastien Bacher (seb128)]

thank you for your bug report, that seems a behaviour of the unity launcher rather than from nautilus though

[blue239 (blue239)]

One member had given an explanation and suggested temporary workaround.

"When a desktop launcher uses ‘DBusActivatable=true’, it will skip exec line and send a signal to to dbus to launch an application. On Unity for some reason dbus-activation is failing and causing time out."

1. sudo apt-get install gksu
2. gksudo gedit /usr/share/applications/org.gnome.Nautilus.desktop

And then comment out DBusActivatable=true like this
#DBusActivatable=true

3. save and exit. Kill nautilus. nautilus -q
4. Now it will work.

[Khurshid Alam (khurshid-alam)]

@Sebastien

I can reproduce it without unity launcher.

1) Create a shortcut for 'org.gnome.Nautilus.desktop' on the desktop. (just drag it from dash)

2) Now middle click it twice. It won't launch

3) Also if change the highlighted folder on one nautilus window, then middle click will work again.

4) I can also reproduce under gnome-shell, until I ran `nautilus --gapplication-service`,

So this may have something to do with middle-click action when it tries to launch same location twice with dbus.

Als