Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TMUX killing all windows processes for an executable in all TMUX sessions when first TMUX WSL terminal is closed #11258

Open
1 of 2 tasks
0xfMel opened this issue Mar 7, 2024 · 2 comments

Comments

@0xfMel
Copy link

0xfMel commented Mar 7, 2024

Windows Version

Microsoft Windows [Version 10.0.22621.3155]

WSL Version

2.1.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1

Distro Version

Ubuntu 22.04

Other Software

TMUX 3.2a

Repro Steps

  1. Open a wsl terminal
  2. Run tmux to get inside a tmux session
  3. Run a windows executable, tested issue happening with /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe
  4. Open a second wsl terminal and do the same
  5. close the first terminal
  6. powershell exists on the second terminal too!

Expected Behavior

I would expect the executable to continue to run in the second terminal, as this is what happens with linux executables such as fish shell, and this is what happens when running outside of tmux.

Actual Behavior

powershell exits for every instance running inside of tmux created after the first.
you can close any other instance of tmux and it will work as expected, only when the first is closed do the rest exit too.
only happens when running the executable in tmux.
only happens for windows executables.
you can detach from the first tmux session and it will continue to run on the rest, but will still kill the rest when that terminal is closed.
tested happening with powershell terminal & alacritty.

I've been trying to find a work around but I could only get the other instances to stay alive if the first terminal is still alive, opening background tmux sessions which run the executable doesn't work.

Diagnostic Logs

WslLogs-2024-03-07_00-23-21.zip

Copy link

github-actions bot commented Mar 7, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@pedrohgmacedo
Copy link

pedrohgmacedo commented Apr 23, 2024

It happens on WSL1 too, and it was supposed to have been fixed:
#709, #1007, #1511, #2252, #2391, #11157, #2138,#11237,#11112,#6242,#4690
All issues were marked as fixed by @therealkenc or @benhillis, but I just can't get it working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants