starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

WSL-Tab immediately closing #3314

New Issue
Closed
opened 2026-01-30 23:18:26 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 23:18:26 +00:00
Owner
Copy Link

Originally created by @LarsBehl on GitHub (Aug 8, 2019).

Environment

Windows build number: 10.0.18362.239
Windows Terminal version: 0.3.2171.0

Additional Software: Ubuntu WSL1

Steps to reproduce

Unknown, happened on first launch after update to v0.3

Expected behavior

Open an Ubuntu WSL1-Tab

Actual behavior

Open an Ubuntu WSL1-Tab and immediately closing it

Originally created by @LarsBehl on GitHub (Aug 8, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.239 Windows Terminal version: 0.3.2171.0 Additional Software: Ubuntu WSL1 ``` # Steps to reproduce Unknown, happened on first launch after update to v0.3 <!-- A description of how to trigger this bug. --> # Expected behavior Open an Ubuntu WSL1-Tab <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Open an Ubuntu WSL1-Tab and immediately closing it <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-30 23:18:26 +00:00
claunia commented 2026-01-30 23:18:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 8, 2019):

What happens if you run WSL from CMD?

@DHowett-MSFT commented on GitHub (Aug 8, 2019): What happens if you run WSL from CMD?
claunia commented 2026-01-30 23:18:27 +00:00
Author
Owner
Copy Link

@LarsBehl commented on GitHub (Aug 8, 2019):

Performs normally; starting WSL

@LarsBehl commented on GitHub (Aug 8, 2019): Performs normally; starting WSL
claunia commented 2026-01-30 23:18:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2019):

Could you share your profiles.json and also:

@zadjii-msft commented on GitHub (Aug 9, 2019): Could you share your profiles.json and also:
claunia commented 2026-01-30 23:18:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 9, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Aug 9, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:18:27 +00:00
Author
Owner
Copy Link

@LarsBehl commented on GitHub (Aug 9, 2019):

Feedback via feedback hub is sent. I am currently using the same profiles.json file on another machine, where it works perfectly fine

profiles.zip

@LarsBehl commented on GitHub (Aug 9, 2019): Feedback via feedback hub is sent. I am currently using the same profiles.json file on another machine, where it works perfectly fine [profiles.zip](https://github.com/microsoft/terminal/files/3487033/profiles.zip)
claunia commented 2026-01-30 23:18:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 9, 2019):

That'll do it. Right now, and until we make a release with #2298 included, your settings will "roam" from machine to machine. The exact name of the Ubuntu distribution on your first machine probably doesn't match the one on your second.

Can you confirm that the name after wsl.exe -d matches the name of your distribution when you run wsl.exe -l?

@DHowett-MSFT commented on GitHub (Aug 9, 2019): That'll do it. Right now, and until we make a release with #2298 included, your settings will "roam" from machine to machine. The exact name of the Ubuntu distribution on your first machine probably doesn't match the one on your second. Can you confirm that the name after `wsl.exe -d` matches the name of your distribution when you run `wsl.exe -l`?
claunia commented 2026-01-30 23:18:28 +00:00
Author
Owner
Copy Link

@LarsBehl commented on GitHub (Aug 9, 2019):

Name did not match completely, wsl.exe -l showed up Ubuntu-18.04 (Standard). Currently I am wondering why it worked in the first place. Most important is, that it is fixed now, thanks

@LarsBehl commented on GitHub (Aug 9, 2019): Name did not match completely, ```wsl.exe -l``` showed up ```Ubuntu-18.04 (Standard)```. Currently I am wondering why it worked in the first place. Most important is, that it is fixed now, thanks
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Attention Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3314
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?