After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 704972 - Cannot open remote terminal
Cannot open remote terminal
Status: RESOLVED OBSOLETE
Product: gnome-terminal
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-07-27 08:40 UTC by Daniel Preston
Modified: 2013-07-28 17:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Custom action to open remote terminal in current directory (39.89 KB, image/png)
2013-07-28 17:06 UTC, Daniel Preston
Details

Description Daniel Preston 2013-07-27 08:40:12 UTC
Whilst in Nautilus I can connect to a remote host, it fails to do so in Terminal.

Steps to reproduce:

1. Open a remote host in Nautilus, i.e. sftp://username@domain.com/directory
2. Once switched to domain.com/directory, in Nautilus select "Open in remote terminal" from context menu.
3. Gnome Terminal will open but will remain empty (see screenshot [1]). Nothing more will happen.

Note:

It cannot be a permission problem since I can access the remote host in Nautilus without entering a passphrase.

[1] Screenshot: http://i.imgur.com/3LyGag9.png
Comment 1 Christian Persch 2013-07-27 09:08:04 UTC
Are you absolutely certain you're using the gnome-terminal nautilus extension (which isn't supported on version 3.8), and not the standalone nautilus-open-terminal (which is unmaintained and broken) ?
Comment 2 Daniel Preston 2013-07-27 09:26:33 UTC
Hi Christian,

At least I have `nautilus-open-terminal 0.20-1` installed. But how can I check whether clicking on "Open in remote terminal" from context menu uses `nautilus-open-terminal` or `gnome-terminal nautilus extension`?
Comment 3 Christian Persch 2013-07-27 09:33:56 UTC
$ cat /proc/$(pidof nautilus)/maps | grep terminal

If it contains 'libnautilus-open-terminal' the it's nautilus-open-terminal; it it contains 'libterminal-nautilus' then it's gnome-terminal's own one.

In any case, would be useful to try gnome-terminal 3.9's one to see if it has the same problem.
Comment 4 Daniel Preston 2013-07-27 09:52:58 UTC
$ cat /proc/$(pidof nautilus)/maps | grep terminal
7f95efdfb000-7f95efdff000 r-xp 00000000 fe:00 266407                     /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so
7f95efdff000-7f95efffe000 ---p 00004000 fe:00 266407                     /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so
7f95efffe000-7f95effff000 r--p 00003000 fe:00 266407                     /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so
7f95effff000-7f95f0000000 rw-p 00004000 fe:00 266407                     /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so

So it's the open-terminal one. Since it is unmaintained I guess I should uninstall it and rather use Gnome-Terminal's own one?

I would like to test gnome-terminal 3.9 but it is not available on Arch. I will then wait until it is released, test it and report again.
Comment 5 Daniel Preston 2013-07-27 09:55:58 UTC
I just saw, uninstalling `nautilus-open-terminal` removes the context menu entry `Open in terminal`. So, how do I use gnome-terminal's own implementation in the context menu instead?
Comment 6 Christian Persch 2013-07-27 10:42:58 UTC
Build gnome-terminal using the --with-nautilus-extension configure switch.
Comment 7 Daniel Preston 2013-07-28 17:06:30 UTC
Created attachment 250318 [details]
Custom action to open remote terminal in current directory
Comment 8 Daniel Preston 2013-07-28 17:07:44 UTC
Nice, with the help of `Nautilus Actions` I created a custom action with path `/usr/bin/gnome-terminal` and working directory `%d/%b`.

Whilst having opened a remote directory in Nautilus and then running the custom action, Gnome Terminal opens a remote terminal session.