ssh-tunnels icon indicating copy to clipboard operation
ssh-tunnels copied to clipboard

Starting a tunnel hangs on message "Tunneling..."

Open kisp opened this issue 2 years ago • 2 comments

Hi,

I am experiencing a regression: Starting a tunnel doesn't work for me anymore after I updated.

I in the minibuffer I see the message "Tunneling..." and then emacs hangs. Interrupting and seeing the stacktrace showed me that emacs is in the function call-process within ssh-tunnels--command.

I did a git bisect and found this to be the problematic commit: https://github.com/death/ssh-tunnels/commit/d3a7402d467ac14e0ba994d540c363f29de1ae3a

I am running Arch Linux.

16:28 $ uname -r
5.18.3-arch1-1
✔ ~ 
16:28 $ emacs --version
GNU Emacs 28.1
Copyright (C) 2022 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
✔ ~ 
16:28 $ ssh -V
OpenSSH_9.0p1, OpenSSL 1.1.1o  3 May 2022

kisp avatar Jun 21 '22 14:06 kisp

The relevant change in the above commit seems to be:

Changing the destination arg of call-process from nil to (list (current-buffer) t).

kisp avatar Jun 21 '22 14:06 kisp

Hey, I am on a similar system (archlinux, recent emacs and ssh) but not noticed anything out of the ordinary. Note that current HEAD passes t for destination. The flag -f is passed to ssh so that it should daemonize (parent forks a child and exits) after authentication. Possibly you could debug the issue by using a non-temporary buffer and ssh verbosity flags to collect and view ssh output, or trying to trace the command in the terminal.

death avatar Jun 21 '22 15:06 death