wezterm
wezterm copied to clipboard
The multiplexing connection window automatically closes after a period of time
What Operating System(s) are you seeing this problem on?
Windows
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
wezterm 20240325-093507-e5ac32f2
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
as title.
To Reproduce
Use multiplexing to connect to the remote server in the panel
Configuration
{
name = "MyServer",
remote_address = "xxxx",
username = "xxx",
local_echo_threshold_ms = 500,
},
Expected Behavior
This pane (tab) should always exist and will not be closed automatically.
Logs
00:20:15.075 ERROR wezterm_client::client > Error while decoding response pdu: decoding a PDU: reading PDU length: EOF while reading leb128 encoded value
00:20:15.075 INFO wezterm_client::domain > detached domain 1
00:20:15.075 ERROR wezterm_client::client > wezterm cli --prefer-mux proxy: Exited with code 1
00:20:15.076 INFO mux > domain detached panes: [4]
00:28:15.298 ERROR wezterm_client::client > Error while decoding response pdu: decoding a PDU: reading PDU length: EOF while reading leb128 encoded value
00:28:15.298 INFO wezterm_client::domain > detached domain 1
00:28:15.298 INFO mux > domain detached panes: [20]
00:28:15.298 ERROR wezterm_client::client > wezterm cli --prefer-mux proxy: Exited with code 1
Anything else?
No response
Can you try to see if you have the TMOUT env var in your distant shell? https://www.cyberciti.biz/faq/linux-tmout-shell-autologout-variable/
Can you try to see if you have the TMOUT env var in your distant shell? https://www.cyberciti.biz/faq/linux-tmout-shell-autologout-variable/
I tried echo $TMOUT
, but there was no output. It should be that there is no such env var.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.