Nautilus (Files) Doesn't Launch When Clicked

[Michael Murphy]

When in gnome-shell, nautilus appears as already opened, but clicking on it does not open the file manager, but instead goes back to the active workspace. In other words, it is as if gnome shell is treating the background nautilus session as if it is a normal nautilus window. The only way to get nautilus to open in a window is to right click Files and select New Window.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jan 18 07:59:20 2014
DisplayManager: lightdm
GsettingsChanges:
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'icon-theme' b"'fs-icons-ubuntu-sky-light'"
 b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
 b'org.gnome.desktop.interface' b'gtk-theme' b"'Flattastic-Blue-Light'"
InstallationDate: Installed on 2014-01-17 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140115)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Harry (harry33)]

I can confirm this to be true in gnome-shell session in trusty with all the official updates installed.

Also this appears to be the case when using the Gnome3 Staging PPA, where
 - gnome-shell is v. 3.11.4-0ubuntu1~trusty1
 - mutter is v. 3.11.4-0ubuntu1~trusty1
 - nautilus is v. 3.11.3-0ubuntu1~trusty1

[Harry (harry33)]

This is an upstream issue with the new gnome-shell.
This concerns version 3.10.3 and also development version 3.11.4 of the gnome-shell.
See here this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=722510

[Harry (harry33)]

This issue is now fixed with the gnome-shell-3.10.3-0ubuntu2.
See bug #1274453.