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

Windows 10 WSL 1 Debian Terminal bug (text is being multiplied when re-scaling resolution) #8372

New Issue
Closed
opened 2026-01-31 01:27:52 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:27:52 +00:00
Owner
Copy Link

Originally created by @cijayh on GitHub (May 20, 2020).

# Environment

Windows build number: **Microsoft Windows 10 Version 1903 (OS Build version 10.0.18362.836)**
Windows Terminal version (if applicable): 
**Linux 4.4.0-18362-Microsoft #836-Microsoft Mon May 05 16:04:00 PST 2020 x86_64 GNU/Linux**

**Any other software?**
I just had installed WSL for Windows 10 and don't have that much software. 
I got software like VLC, VMware, Visual Studio 2019, CCleaner, Google Chrome, FireFox..

**# Steps to reproduce**

<!-- A description of how to trigger this bug. -->
Well, that I can explain. 
1. Start up a WSL distrubution shell, for an example I'm using Debian for Windows 10. 
2. Likely the shell will start in the working directory of the home profile folder something like 
"**<username>@<Device's name>:~$**" (most common of course after a new installation of WSL)
3. Now just try to rescale the shell resolution, just take the right bottom corner of the shell's window 
and try to drag it from right to left or from bottom right to top left and keep doing this. But make 
sure while re-scaling the "**<username>@<Device's name>:~$**" is hit, so get atleast the window 
size re-scaled until it's in the user's path. 

For example if this is the shell resolution with working directory:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-  "**<username>@<Device's name>:~$**"                                              -
-                                                                                                                  -
-                                                                                                                  -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Make sure the shell's resolution will become something like this and repeat the process 
of re-scaling a couple times, you'll see that the directory's 
and user's name is being multiplied:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-  "**<username>@<                                                                                 -
-   Device's name>:~$**"                                                                            -
-                                                                                                                  -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

**# Expected behavior**

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
What I'd like to expect in this situation is that, the remaning text of (for example) 
the working directory's name, will get to the next line and while re-scaling the resolution this will 
proceed until the minimum size is triggered, then of course I expect that the text won't go to 
another line or whatsoever and it will stay in the same position. 

**# Actual behavior**

<!-- What's actually happening? -->
What is actually happening is that the text is being multiplied, for example with user name and working directory:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-  <username>@<Device's name>:~$<username>@                              -
-  <Device's name>:~$ <username>@                                                     -
-  <Device's name>:~$<username>@<Device's name>:~$                     -
-                                                                                                                  -
-                                                                                                                  -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I hope you can fix this bug. Thank you in advance for the effort.
Originally created by @cijayh on GitHub (May 20, 2020). <!-- 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: **Microsoft Windows 10 Version 1903 (OS Build version 10.0.18362.836)** Windows Terminal version (if applicable): **Linux 4.4.0-18362-Microsoft #836-Microsoft Mon May 05 16:04:00 PST 2020 x86_64 GNU/Linux** **Any other software?** I just had installed WSL for Windows 10 and don't have that much software. I got software like VLC, VMware, Visual Studio 2019, CCleaner, Google Chrome, FireFox.. **# Steps to reproduce** <!-- A description of how to trigger this bug. --> Well, that I can explain. 1. Start up a WSL distrubution shell, for an example I'm using Debian for Windows 10. 2. Likely the shell will start in the working directory of the home profile folder something like "**<username>@<Device's name>:~$**" (most common of course after a new installation of WSL) 3. Now just try to rescale the shell resolution, just take the right bottom corner of the shell's window and try to drag it from right to left or from bottom right to top left and keep doing this. But make sure while re-scaling the "**<username>@<Device's name>:~$**" is hit, so get atleast the window size re-scaled until it's in the user's path. For example if this is the shell resolution with working directory: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "**<username>@<Device's name>:~$**" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Make sure the shell's resolution will become something like this and repeat the process of re-scaling a couple times, you'll see that the directory's and user's name is being multiplied: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "**<username>@< - - Device's name>:~$**" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - **# Expected behavior** <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> What I'd like to expect in this situation is that, the remaning text of (for example) the working directory's name, will get to the next line and while re-scaling the resolution this will proceed until the minimum size is triggered, then of course I expect that the text won't go to another line or whatsoever and it will stay in the same position. **# Actual behavior** <!-- What's actually happening? --> What is actually happening is that the text is being multiplied, for example with user name and working directory: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - <username>@<Device's name>:~$<username>@ - - <Device's name>:~$ <username>@ - - <Device's name>:~$<username>@<Device's name>:~$ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I hope you can fix this bug. Thank you in advance for the effort.
claunia added the Resolution-Duplicate label 2026-01-31 01:27:52 +00:00
claunia commented 2026-01-31 01:27:53 +00:00
Author
Owner
Copy Link

@cijayh commented on GitHub (May 24, 2020):

Dear Sir or Madam,

Have you checked this issue already? I didn't hear anything from you?

@cijayh commented on GitHub (May 24, 2020): Dear Sir or Madam, Have you checked this issue already? I didn't hear anything from you?
claunia commented 2026-01-31 01:27:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 25, 2020):

/dup #5450 thanks for the report! It’s a holiday weekend here in the US where most of the team is, so responses may have to wait until Tuesday or Wednesday (time in Redmond, US)

@DHowett commented on GitHub (May 25, 2020): /dup #5450 thanks for the report! It’s a holiday weekend here in the US where most of the team is, so responses may have to wait until Tuesday or Wednesday (time in Redmond, US)
claunia commented 2026-01-31 01:27:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 25, 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 (May 25, 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!
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#8372
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?