starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal crashes in WSL2 when typing exit directly after a sudo statement in second tab #5376

New Issue
Closed
opened 2026-01-31 00:11:57 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:11:57 +00:00
Owner
Copy Link

Originally created by @mwidmann on GitHub (Dec 4, 2019).

Environment

Windows build number: Version 10.0.19033.1
Windows Terminal version (if applicable): 0.7.3291.0


Any other software?
Ubuntu 18.04.3 LTS running in WSL2

Steps to reproduce

I have the Ubuntu installation in WSL2 set up as the default profile

  1. open terminal (or have it running)
  2. open a second tab
  3. execute any command as sudo, e.g. sudo hwclock -s for synchronizing the clock
  4. enter the sudo password
  5. type exit

Expected behavior

the tab closes, the other sessions stay open.

Actual behavior

the terminal crashes.

https://i.imgur.com/nbg76pn.gifv

Originally created by @mwidmann on GitHub (Dec 4, 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: Version 10.0.19033.1 Windows Terminal version (if applicable): 0.7.3291.0 Any other software? Ubuntu 18.04.3 LTS running in WSL2 ``` # Steps to reproduce I have the Ubuntu installation in WSL2 set up as the default profile 1. open terminal (or have it running) 2. open a second tab 3. execute any command as sudo, e.g. `sudo hwclock -s` for synchronizing the clock 4. enter the sudo password 5. type `exit` # Expected behavior the tab closes, the other sessions stay open. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior the terminal crashes. [https://i.imgur.com/nbg76pn.gifv](https://i.imgur.com/nbg76pn.gifv)
claunia added the Resolution-Duplicate label 2026-01-31 00:11:57 +00:00
claunia commented 2026-01-31 00:11:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 4, 2019):

I believe this is the same as #3801 ...
but will you send us some /feedback

@DHowett-MSFT commented on GitHub (Dec 4, 2019): I believe this is the same as #3801 ... but will you send us some /feedback
claunia commented 2026-01-31 00:11:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 4, 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 (Dec 4, 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-31 00:11:58 +00:00
Author
Owner
Copy Link

@mwidmann commented on GitHub (Dec 5, 2019):

I guess, the issue is the same as in #3801 Here's my feedback https://aka.ms/AA6r4za

@mwidmann commented on GitHub (Dec 5, 2019): I guess, the issue is the same as in #3801 Here's my feedback https://aka.ms/AA6r4za
claunia commented 2026-01-31 00:11:58 +00:00
Author
Owner
Copy Link

@krisavi commented on GitHub (Dec 5, 2019):

I guess, the issue is the same as in #3801 Here's my feedback https://aka.ms/AA6r4za

Linking to 3rd party feedback seems to be a bad practice as not everyone can read the response there:
image
That for example with a company account.

@krisavi commented on GitHub (Dec 5, 2019): > I guess, the issue is the same as in #3801 Here's my feedback https://aka.ms/AA6r4za Linking to 3rd party feedback seems to be a bad practice as not everyone can read the response there: ![image](https://user-images.githubusercontent.com/1912568/70253549-b438d700-1783-11ea-9947-419a960b77f3.png) That for example with a company account.
claunia commented 2026-01-31 00:11:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 5, 2019):

@krisavi thanks for the info. This feedback workflow does suffice for our purposes as Microsoft, but it can be somewhat annoying for others 😄

@DHowett-MSFT commented on GitHub (Dec 5, 2019): @krisavi thanks for the info. This feedback workflow does suffice for our purposes as Microsoft, but it can be somewhat annoying for others :smile:
claunia commented 2026-01-31 00:11:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 5, 2019):

Confirmed as a /dupe of #3801. Thanks for the feedback item!

@DHowett-MSFT commented on GitHub (Dec 5, 2019): Confirmed as a /dupe of #3801. Thanks for the feedback item!
claunia commented 2026-01-31 00:11:59 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 5, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 5, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#5376
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?