yazi: Yazi crashes under SSH after 25.2.26
I do not have in-person access to the machine the bug is occurring on at the moment.
In light of the #2421 plus the triage performed (and explained in the subsequent comments), this might not be an issue with SSH, and just a bad set of commits following from AsyncStdin with f25ef0f0.
What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
kitty v0.39.1
yazi --debug output
Yazi
Version: 25.2.26 (57ef8f9e 2025-03-01)
Debug : false
Triple : x86_64-unknown-linux-gnu (linux-x86_64)
Rustc : 1.84.1 (e71f9a9a 2025-01-27)
Ya
Version: 25.2.26 (Arch Linux 2025-02-27)
Emulator
TERM : Some("xterm-kitty")
TERM_PROGRAM : None
TERM_PROGRAM_VERSION: None
Brand.from_env : Some(Kitty)
Emulator.detect : Emulator { kind: Left(Kitty), light: false, cell_size: None }
Adapter
Adapter.matches: Kgp
Desktop
XDG_SESSION_TYPE : Some("tty")
WAYLAND_DISPLAY : None
DISPLAY : Some("localhost:15.0")
SWAYSOCK : None
HYPRLAND_INSTANCE_SIGNATURE: None
WAYFIRE_SOCKET : None
SSH
shared.in_ssh_connection: true
WSL
WSL: false
Variables
SHELL : Some("/bin/fish")
EDITOR : Some("nvim")
VISUAL : None
YAZI_FILE_ONE : None
YAZI_CONFIG_HOME: None
YAZI_ZOXIDE_OPTS: None
FZF_DEFAULT_OPTS: None
Text Opener
default : Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
block-create: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
block-rename: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
Multiplexers
TMUX : false
tmux version : No such file or directory (os error 2)
tmux build flags : enable-sixel=Unknown
ZELLIJ_SESSION_NAME: None
Zellij version : No such file or directory (os error 2)
Dependencies
file : 5.46
ueberzugpp : No such file or directory (os error 2)
ffmpeg/ffprobe: 7.1 / 7.1
pdftoppm : 25.02.0
magick : 7.1.1-44
fzf : 0.60.2
fd/fdfind : 10.2.0 / No such file or directory (os error 2)
rg : 13.0.0
chafa : 1.14.5
zoxide : 0.9.7
7zz/7z : No such file or directory (os error 2) / No such file or directory (os error 2)
jq : 1.7.1
Clipboard
wl-copy/paste: 2.2.1 / 2.2.1
xclip : 0.13
xsel : No such file or directory (os error 2)
Describe the bug
After upgrading to yazi-25.2.26-1.
opening Yazi within ssh ssh over Tailscale under Kitty SSH leads to a brief flicker of the Yazi TUI before the error:
Terminal response timeout: The request sent by Yazi didn't receive a correct response.
Please check your terminal environment as per: https://yazi-rs.github.io/docs/faq#trt
Downgrading back to yazi-25.2.11-1 and the corresponding issue was not to be had.
Furthermore, >|kitty(0.39.1)11;rgb:0000/0000/0000 is automatically written in the terminal prompt after yazi --debug.
The yazi debug output above is done by having build with cargo against 57ef8f9ebdf1.
Minimal reproducer
On a local and remote machine, running ArchLinux, install
- fish (v4.0.0-2)
tailscale (v1.80.2-1)- kitty (v0.39.1-1)
- kitty-terminfo (v0.39.1-1)
- kitty-shell-integration (v0.39.1-1)
SSH from the local machine to the remote machine through the Tailscale Proxy.
Open Yazi. The crash will occur. (Not sure if this belongs more so within Tailscale (https://github.com/tailscale/tailscale/issues/12827) as there seems to be ports/signals/things involved with them as a proxy.)
Anything else?
I will perform as in the checklist using a git bisect later and write into the comments.
Checklist
- I tried the latest nightly build, and the issue is still reproducible
- I updated the debug information (
yazi --debug) input box to the nightly that I tried - I can reproduce it after disabling all custom configs/plugins (
mv ~/.config/yazi ~/.config/yazi-backup)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (7 by maintainers)
@sxyazi Thank you so much. 🥰 The fix does work all the time now under any combination of SSH I have performed.
Tried and worked! Thank you!