Nautilus has problems mounting network locations when nautilus-open-terminal is installed

[Bruno Nova]

At least in Ubuntu 13.10, when this extension (nautilus-open-terminal) is installed, Nautilus has some serious problems when mounting SFTP locations, and possibly other protocols like Samba as well (haven't tested that).
These problems occur, more specifically, when trying to mount the same SFTP location a second time (after having mounted and unmounted it before).

The culprit seems to be this extension because, when the extension is not installed or disabled, these problems don't occur.
I disabled the extension temporarily by renaming the file /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so.
I also tested this using a Live DVD (Nautilus worked fine before installing the extension).

More information below.

---

To test this problem, the ssh server must be installed and running, and the nautilus-open-terminal extension must be installed (and not disabled).

TEST CASE

1. Open Nautilus
2. Go to the location "sftp://localhost", for example (Press Ctrl+L, write the location and press enter)
3. Enter the ssh credentials if asked
4. The SFTP location should be mounted. Unmount it by pressing the respective unmount "arrow" button in the sidebar
5. Try to mount it again by repeating step 2 (and maybe 3)

WHAT WAS EXPECTED

The SFTP location was mounted successfully again

WHAT HAPPENED

Nautilus crashed.
This is the error displayed in the terminal (when Nautilus is started from the terminal):
ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))

---

I also tested something else.

I configured avahi to publish my computer as an SSH and SFTP server.
The following commands should be enough to do this:
$ sudo cp /usr/share/doc/avahi-daemon/examples/s* /etc/avahi/services/
$ sudo restart avahi-daemon

My computer then appears in Nautilus Network "folder".
The first time my computer is double-clicked, it is mounted successfully through SFTP.
But, on the second time (after unmounting), the following error message is displayed in a dialog:

Could not display "".
The file is of an unknown type

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nautilus-open-terminal 0.20-1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Feb 20 23:14:53 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-01 (111 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: nautilus-open-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

[Bruno Nova (brunonova)]

This problem also affects FTP in Nautilus.
On the second time I tried to connect to ftp://ftp.mozilla.org, Nautilus crashed.
So, this problem probably affects all supported protocols.

[Scott Deagan (scott-deagan)]

I have this problem too on Ubuntu 14.04 desktop. I do not have nautilus-open-terminal installed. It occurs for me quite frequently - about every third or fourth time after mounting then unmounting a samba share within Nautilus.

I have to killall -9 nautilus before I can try to mount the Samba share again, although sometimes Nautilus just crashes (completely disappears, no error messages) and when I restart it the shares are accessible again.

With log level set to 2, this is what my Samba server outputs when the problem occurs:

[2014/04/26 02:43:50.234486, 2] ../source3/auth/auth.c:278(auth_check_ntlm_password)
  check_ntlm_password: authentication for user [scott] -> [scott] -> [scott] succeeded
[2014/04/26 02:43:50.248441, 1] ../source3/param/loadparm.c:2936(lp_idmap_range)
  idmap range not specified for domain '*'
[2014/04/26 02:43:50.253839, 1] ../source3/param/loadparm.c:2936(lp_idmap_range)
  idmap range not specified for domain '*'
[2014/04/26 02:43:50.256085, 2] ../source3/smbd/service.c:848(make_connection_snum)
  i5-desktop (ipv4:192.168.1.22:60151) connect to service Personal initially as user nobody (uid=65534, gid=65534) (pid 14419)

I have not, as yet, experienced this problem when accessing my share using an IP address instead (i.e. smb://192.168.1.1/MyShare instead of smb://HomeServer/MyShare).

@Bruno Nova: you might want to correct the title of this bug report if you can - you've mispelt "mounting" (was difficult to find this bug report).

[Bruno Nova (brunonova)]

Thanks Scott! I hadn't noticed that spelling error.

I have uninstalled the extension (and replaced it with a custom Nautilus Action), and I've also seen this problem happen.
But it happens randomly. With the extension installed, it always happens on the 2nd time.

I think I'll add "nautilus" as affected too.

[Scott Deagan (scott-deagan)]

Just to add to my previous post, I have now experienced this issue when accessing a Samba share using IP addresses.

[Scott Deagan (scott-deagan)]

In my opinion this is quite a serious bug as the file manager is a core component of the operating system. Not being able to reliably mount and unmount SFTP and/or Samba resources makes performing every day computing tasks (copying files to and from network shares) a hassle. When this issue does occur, the only way to re-mount the resource is:

1. Unmount the SFTP or Samba share in Nautilus by clicking the "eject" button.
2. Open a terminal and run: killall -9 nautilus
3. Re-open Nautilus and re-mount the share (even then, sometimes this will fail and you'll have to start again).

The only reliable workaround I've found so far is to install and use the Dolphin file manager.