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

Resetting WSLv1 shell does not start from terminal top #9613

New Issue
Closed
opened 2026-01-31 01:59:14 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:59:14 +00:00
Owner
Copy Link

Originally created by @vadimkantorov on GitHub (Jul 14, 2020).

Version: 1.0.1811.0

After typing reset in my WSLv1 shell, I get this. Unfortunately, I do not have a stable repro. Stumbled on this in a long-running Terminal session.
image

Originally created by @vadimkantorov on GitHub (Jul 14, 2020). Version: 1.0.1811.0 After typing `reset` in my WSLv1 shell, I get this. Unfortunately, I do not have a stable repro. Stumbled on this in a long-running Terminal session. ![image](https://user-images.githubusercontent.com/1041752/87479266-75c59d80-c62b-11ea-95a8-7bef304e08e8.png)
claunia added the Resolution-Duplicate label 2026-01-31 01:59:14 +00:00
claunia commented 2026-01-31 01:59:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 14, 2020):

I'd bet that @j4james magically knows exactly what this is. If he doesn't, then I'm not really sure what we can do to investigate this without some sort of stable repro...

@zadjii-msft commented on GitHub (Jul 14, 2020): I'd bet that @j4james magically knows exactly what this is. If he doesn't, then I'm not really sure what we can do to investigate this without some sort of stable repro...
claunia commented 2026-01-31 01:59:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2020):

Thanks for the report! This was fixed in PR #6763, and is a /dup of #6545

@DHowett commented on GitHub (Jul 14, 2020): Thanks for the report! This was fixed in PR #6763, and is a /dup of #6545
claunia commented 2026-01-31 01:59:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2020):

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 (Jul 14, 2020): 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!
claunia commented 2026-01-31 01:59:16 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Jul 14, 2020):

In general it may be cool to somehow enable « tracing » mode that would collect information about current state of terminal and could record characters/events. Then this trace/log could be uploaded here for cases when a repro is hard to find.

Maybe there can be a limited, but still useful scope of this idea

@vadimkantorov commented on GitHub (Jul 14, 2020): In general it may be cool to somehow enable « tracing » mode that would collect information about current state of terminal and could record characters/events. Then this trace/log could be uploaded here for cases when a repro is hard to find. Maybe there can be a limited, but still useful scope of this idea
claunia commented 2026-01-31 01:59:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2020):

So, we do actually have something like that! It's the "debug tap", and it shows what's coming out of the PTY infrastructure.

If you set the global setting debugFeatures to true and then hold own left+right Alt while opening a new tab, you'll get this:

image

(the red on the right is the input stream -- right now, i'm running in win32 input mode where each key is transformed into an entire sequence capturing scancode/vkey/repeat/modifiers (#4999), so it's a little verbose.)

@DHowett commented on GitHub (Jul 14, 2020): So, we do actually have something like that! It's the "debug tap", and it shows what's coming out of the PTY infrastructure. If you set the global setting `debugFeatures` to `true` and then hold own left+right <kbd>Alt</kbd> while opening a new tab, you'll get this: ![image](https://user-images.githubusercontent.com/189190/87480715-c369e800-c5e2-11ea-8f70-ee787b61a9f0.png) (the red on the right is the input stream -- right now, i'm running in win32 input mode where each key is transformed into an entire sequence capturing scancode/vkey/repeat/modifiers (#4999), so it's a little verbose.)
claunia commented 2026-01-31 01:59:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2020):

There's also local tracing accessible through a wprp file in our source folder. 😄

@DHowett commented on GitHub (Jul 14, 2020): There's also local tracing accessible through a `wprp` file in our source folder. :smile:
claunia commented 2026-01-31 01:59:16 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Jul 14, 2020):

Wow. I think it would be super-cool to make it more accessible to users (with an instruction how to record and view/upload such a trace?) :) Probably many more "stable repro"-less bugs would be less frustrating to report.

What is "source folder"? (I didn't build terminal from source)

@vadimkantorov commented on GitHub (Jul 14, 2020): Wow. I think it would be super-cool to make it more accessible to users (with an instruction how to record and view/upload such a trace?) :) Probably many more "stable repro"-less bugs would be less frustrating to report. What is "source folder"? (I didn't build terminal from source)
claunia commented 2026-01-31 01:59:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 15, 2020):

Ah, I definitely meant "the folder with the source code in it". The tracing tools that ship with windows are not particularly user-friendly, and as such neither is our wprp file. 😦

@DHowett commented on GitHub (Jul 15, 2020): Ah, I definitely meant "the folder with the source code in it". The tracing tools that ship with windows are not particularly user-friendly, and as such neither is our wprp file. 😦
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#9613
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?