-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[1.22] Terminal stops functioning after closing last window with "compatibility.allowHeadless" enabled and "windowingBehavior" set to "useExisting"/"useAnyExisting" #18827
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
Comments
Hi @nickamante. I'm struggling to get a repro on this bug. I've been trying it out with the following parameters:
Could you share a copy of your settings.json and state.json please /? (Just in case) The state.json is stored right next to the settings.json. Thanks in advance! |
Here you go - I've got the same issue on both my older Dell Windows 10 laptop and a brand new Windows 11 Lenovo. Aside from the out of the box software I've installed the following on the Lenovo machine (via winget): WSL/Ubuntu, Powershell 7, Gsudo, Git, TortoiseGit, Beyond Compare 5, OhMyPosh, Clink, GrepWin, Visual Studio Code, Firefox, Spotify. It's largely just dev/terminal focused apps at the point when I discovered the issue. I'd think it might be related to one of them, except Terminal fails to launch for all shells and yet the shells themselves have no issues once taking Terminal out of the picture. |
Thanks! Got a repro! Looks like the minimal repro is this: "windowingBehavior": "useExisting",
"compatibility.allowHeadless": true, Looks like this got fixed |
Actually, re-opening. It'll be good to have a hotfix for this on 1.22 since we have a lot of windowing changes in 1.23. Just to be safe. |
Windows Terminal version
1.22.10730.0
Windows build number
10.0.26100 (Windows 11)
10.0.19045 (Windows 10)
Other Software
No response
Steps to reproduce
Settings > Compatibility > Allow Windows Terminal to run in the background
Expected Behavior
Terminal remains running in the background and launching new Terminal windows continues to work.
Actual Behavior
WindowsTerminal.exe
remains running in Task Manager.Appearance > Always display an icon in the notification area
is enabled, left-clicking the icon or right-click Focus Terminal has no effect. UnderWindows >
the last window to be closed remains listed.WindowsTerminal.exe
process is killed in Task Manager.Allow Windows Terminal to run in the background
causes theWindowsTerminal.exe
process to exit after the last window is closed and allows re-launchThe text was updated successfully, but these errors were encountered: