Blue lines trailing output #7450

Closed
opened 2026-01-31 01:04:25 +00:00 by claunia · 2 comments
Owner

Originally created by @TapeWerm on GitHub (Apr 17, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.207]
Windows Terminal version (if applicable): 0.10.781.0

Any other software?
Windows 10 2004, WSL 1, Ubuntu 18.04

Steps to reproduce

I updated to Windows 10 2004 (Insider release preview), and in WSL 1 distro Ubuntu 18.04, there were blue lines trailing the last character of almost every line of output. Specifically the blue lines were rectangle characters of blue, about the same shade as the default Windows 10 accent color. Upgrading to WSL 2 fixed this.

Expected behavior

No lines of blue characters trailing most lines.

Actual behavior

Wish I had a screenshot, I'm in a hurry so I upgraded to WSL 2 before thinking of making an issue on GitHub. Got to study for a quiz tomorrow. My Surface Pro 1 (backup) is updating right now since my ThinkPad is back to normal after the move to WSL 2. If that also has the same issue I'll add a screenshot.

Originally created by @TapeWerm on GitHub (Apr 17, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Microsoft Windows [Version 10.0.19041.207] Windows Terminal version (if applicable): 0.10.781.0 Any other software? Windows 10 2004, WSL 1, Ubuntu 18.04 ``` # Steps to reproduce I updated to Windows 10 2004 (Insider release preview), and in WSL 1 distro Ubuntu 18.04, there were blue lines trailing the last character of almost every line of output. Specifically the blue lines were rectangle characters of blue, about the same shade as the default Windows 10 accent color. Upgrading to WSL 2 fixed this. <!-- A description of how to trigger this bug. --> # Expected behavior No lines of blue characters trailing most lines. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Wish I had a screenshot, I'm in a hurry so I upgraded to WSL 2 before thinking of making an issue on GitHub. Got to study for a quiz tomorrow. My Surface Pro 1 (backup) is updating right now since my ThinkPad is back to normal after the move to WSL 2. If that also has the same issue I'll add a screenshot. <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-Repro labels 2026-01-31 01:04:25 +00:00
Author
Owner

@TapeWerm commented on GitHub (Apr 17, 2020):

Well my Surface just finished updating and WSL 1 is fine on that, not sure what the difference is. Considering that has 4GB of RAM I think I'll stay on WSL 1 for that potato, will update this issue if it ever crops up again. It happened multiple times until I went WSL 2 on my ThinkPad, not sure what is different. Maybe a dotfile is different.
Edit: Moving my Surface to WSL 2 as well cause traceroute works on that. Worth the precious RAM.

@TapeWerm commented on GitHub (Apr 17, 2020): Well my Surface just finished updating and WSL 1 is fine on that, not sure what the difference is. Considering that has 4GB of RAM I think I'll stay on WSL 1 for that potato, will update this issue if it ever crops up again. It happened multiple times until I went WSL 2 on my ThinkPad, not sure what is different. Maybe a dotfile is different. Edit: Moving my Surface to WSL 2 as well cause `traceroute` works on that. Worth the precious RAM.
Author
Owner

@zadjii-msft commented on GitHub (Apr 17, 2020):

Okay since there's not really any repro steps for this issue, and the original issue isn't reproing any longer, I'm going to close this. If you can get this to start happening again, we can re-open and investigate. There's just not really anything we can do with this issue at the moment.

Thanks!

@zadjii-msft commented on GitHub (Apr 17, 2020): Okay since there's not really any repro steps for this issue, and the original issue isn't reproing any longer, I'm going to close this. If you can get this to start happening again, we can re-open and investigate. There's just not really anything we can do with this issue at the moment. Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7450