Update: Solved thanks to comment by @NotTheDr01ds
Original question
(Details of the machines I'm using at end)
I connect to a my Uni's VPN using:
sudo /sbin/modprobe tun && sudo openconnect gucsasa1.cent.gla.ac.uk
I get this output:
POST https://gucsasa1.cent.gla.ac.uk/Got CONNECT response: HTTP/1.1 200 OKCSTP connected. DPD 30, Keepalive 20Connected as 172.20.183.165, using SSL, with DTLS in progressEstablished DTLS connection (using GnuTLS). Ciphersuite (DTLS1.2)-(ECDHE-RSA)-(AES-256-GCM).Unknown DTLS packet type 13, len 16Then I run the following command to connect via ssh:
ssh -X mymachineOnce connected, my .bashrc on the server tries to automatically launches tmux(version 2.6):
# Launch tmuxif command -v tmux>/dev/null; then [[ ! $TERM =~ screen ]] && [ -z $TMUX ] && tmux new-session -A -s mainfiBut it instantly crashes leaving my terminal display looking like this (here Ityped ls to show the problem, but it happens with all stdout):
I also can't see anything I'm typing into the terminal - i.e. it doesn't updatethe display until I hit enter on the command (having typed it 'blind').
When using the -X and -Y flags with ssh, I have no problems with GUIprograms. This is specific to stdout rendering in the terminal in tmux.
After googling, I found that typing reset brought back a 'normal' experience,but also killed the tmux server. Here is the result of typing ls:
As soon as I try to launch tmux, it crashes again and I'm back to the originalproblem.
I don't have this problem when I connect to other servers (running Debian 10,and Ubuntu 20.04, bash and tmux 2.8) using the same client machine and sameterminal.
Does anyone have any ideas of how I can troubleshoot this issue? I've beengoogling all day without success.
Client machine
- OS: lubuntu 20.04
- terminal: st
- shell: bash
- In tmux session:
echo $TERM: st-256color - Outside tmux session:
echo $TERM: screen-256color
Server machine
- OS: Ubuntu 18.04
- terminal: gnome-terminal
- shell: bash
- Outside tmux session:
echo $TERM: st-256color