Spawns another shell (only one term) with WSL2

[OlivierMary]

Hi there,

Just try the new release 3.0.6.

And with WSL2 I have another tmux client.

I had this code at the end of my .zshrc :

if [[ -z "$TMUX" ]]; then
  tmux new-window -n "DIR $(basename $PWD)" -t TMUX
  nbTerm=$(tmux list-clients | grep TMUX | wc -l)
  if [[ $nbTerm -eq 0 ]]; then
    tmux attach -t TMUX || tmux new -s TMUX -n MAIN
  else
   #exit 0;
  fi
fi

I commented the exit 0; to debug why the wsltty windows exited.

So with only one terminal I got a zsh term (not the needed tmux session) and I see a tmux client connected :

if I attach the session I got this:

So another unknow tmux term with low size connected.

That explain why my term exited with the exit 0; but that code work since a long time.
I can change the code to keep 2 clients but that broke the size of all automatic initialized tmux sessions. I have to kill 'TMUX' session and recreate it, not a good deal...

[Biswa96]

Does it also happen with WSL1? What does happen in CMD and wsl.exe?

[mintty]

What exactly do you claim about the terminal? I see smaller font size in the screenshot but it could simply be a matter of presentation. Whatever behaviour you are reporting, is it different with a previous version of mintty/wsltty? Can you demonstrate it without zsh please, and maybe even isolate it from using tmux? Otherwise at least a screen log would be helpful.
Please understand it is really hard to deal with fuzzy incident reports that would require to create a certain test environment first...

[OlivierMary]

Does it also happen with WSL1? What does happen in CMD and wsl.exe?

WSL1 and wsltty 3.0.5 no problem with same code.

@mintty
Same with chsh /bin/bash

and no .bashrc

PID 34 ?

[Biswa96]

WSL2+CMD: I appended the code in .zshrc file and use chsh -s /usr/bin/zsh to change zsh as default. tmux list-session shows TMUX: 1 windows. But ps -aef | grep tmux shows two tmux processes. Any special config in .minttyrc file?

[OlivierMary]

So you reproduce, 2 process, when you attach to current session you get the low resolution tmux ?
No special config in .myttyrc

[OlivierMary]

Hum on my WSL 1 and wsltty 3.0.5 I got this:

2 process but 1 client and in good tmux session.

I didn't say it but no problem on WSL2 without wsltty

[OlivierMary]

In my .zshrc I test list-clients not list-sessions

[OlivierMary]

• add the code at the and of your .zshrc
• chsh /bin/zsh
• exit all term + restart lxmanager service if you want to be sure.
• start a terminal
• you must be in tmux session named TMUX with one window called MAIN and you must be the only one client

on WSL 1 + wsltty 3.0.5 you must have that:

I got the same on WSL 2 without wsltty

and this issue, so on WSL 2 + wsltty 3.0.6 I got
you got an zsh promt not in tmux and if you connect/attach to tmux session you get

[Biswa96]

Understand. I did every steps that you have provided but can not see any defect in case of WSL2+wsltty.

[OlivierMary]

Ok,

Cannot now (no wsl2 on this PC), will try it at home later

[mintty]

In the video, I see you have a full-screen terminal, later start another terminal window, and resize it to full-screen.
I am asking, AGAIN:
What is actually wrong? From a mere terminal point of view, without any background about tmux or whatever you may do, what do you claim about mintty behaviour?
If you do not clarify on this basic question, I can only close the issue.

[OlivierMary]

the video it's on WSL 1, I said on WSL 2 I got this:

that can only happen if another client is running with lower size than my terminal.
And this client it's not a visible terminal/client/pts/tty

[mintty]

How do you leave the initial tmux session? With ^D/exit or by closing the terminal window?

[OlivierMary]

When I do the test I reset lxmanager so I kill all wsl process

[mintty]

Which may well cause zombie processes to remain.
So why do you do that? What happens if you simply exit tmux normally in all test steps, to compare?