Closed munnik closed 4 weeks ago
I'm afraid there isnt anything I can do to help you since, literally any program/command on the remote system could be hanging. You will need to log into it and debug the issue yourself. If you need pointers on how to get started, feel free to ask, I will provide.
Oh one suggestion I do have is, try chaning the interpreter to python, assuming python is available on the remote system. That might either work or give more useful debug data. https://sw.kovidgoyal.net/kitty/kittens/ssh/#opt-kitten-ssh.interpreter
I'm afraid there isnt anything I can do to help you since, literally any program/command on the remote system could be hanging. You will need to log into it and debug the issue yourself.
Normal ssh just works fine, but running it with the kitten wrapper does not show a shell prompt.
I just found out that Zellij is somehow causing the issue. If I run it directly from kitty I get a shell prompt after login, running it from within a Zellij workspace causes the issue.
If you need pointers on how to get started, feel free to ask, I will provide.
Are there any verbose options when running kitten ssh
?
On Wed, Apr 17, 2024 at 05:10:36AM -0700, Martijn de Munnik wrote:
I'm afraid there isnt anything I can do to help you since, literally any program/command on the remote system could be hanging. You will need to log into it and debug the issue yourself.
Normal ssh just works fine, but running it with the kitten wrapper does not show a shell prompt.
I just found out that Zellij is somehow causing the issue. If I run it directly from kitty I get a shell prompt after login, running it from within a Zellij workspace causes the issue.
Ah, well see the kitty FAQ about terminal multiplexers.
Describe the bug When using normal ssh I get a shell prompt after login, using the kitten ssh wrapper I don't see a login prompt. Even after waiting for a couple of minutes. This also happens when I try to log in to an Alpine Linux system.
To Reproduce
kitten ssh <host>
Screenshots
After waiting for a couple of minutes and finally pressing
CTRL-C
Environment details
Additional context Try to reproduce the problem with
kitty --config NONE
if you cannot then post a minimal kitty.conf that reproduces the problem. If the problem involves interaction with some other terminal program post a minimal config for that program to reproduce the problem as well.