WSL console black-on-black cursor in 17713.rs5 #340

Closed
opened 2026-01-30 21:49:27 +00:00 by claunia · 3 comments
Owner

Originally created by @bbulkow on GitHub (Aug 8, 2018).

I tried loading this bug in the WSL area... they summarily closed and told me to go here. I don't know exadtly where you think WSL stops and console begins, and it's a little frustrating to do free QA for you when I can't even tell where bug reports go.

I installed 17713.rs5 off the early access program, and it's difficult to use with WSL because the cursor is black instead of grey. I can see the cursor is there, because it occludes a few bits of the font.

This is true on the three WSLs I have loaded - Ubuntu 18.04, Ubuntu 16.04, and Debian.

I have an LS_COLORS set of ow=01;36;40 , if that makes a difference. I am not using any of the techniques to change the cursor. Until .rs5 I saw a cursor just fine.

You're welcome for the bug report!

Originally created by @bbulkow on GitHub (Aug 8, 2018). I tried loading this bug in the WSL area... they summarily closed and told me to go here. I don't know exadtly where you think WSL stops and console begins, and it's a little frustrating to do free QA for you when I can't even tell where bug reports go. I installed 17713.rs5 off the early access program, and it's difficult to use with WSL because the cursor is black instead of grey. I can see the cursor is there, because it occludes a few bits of the font. This is true on the three WSLs I have loaded - Ubuntu 18.04, Ubuntu 16.04, and Debian. I have an LS_COLORS set of ow=01;36;40 , if that makes a difference. I am not using any of the techniques to change the cursor. Until .rs5 I saw a cursor just fine. You're welcome for the bug report!
claunia added the Product-ConhostResolution-Fix-CommittedResolution-Duplicate labels 2026-01-30 21:49:27 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Aug 8, 2018):

This is a dupe of #193, #200, #225, etc.

Various fixes are inbound or already in Insiders.

@zadjii-msft commented on GitHub (Aug 8, 2018): This is a dupe of #193, #200, #225, etc. Various fixes are inbound or already in Insiders.
Author
Owner

@bbulkow commented on GitHub (Aug 10, 2018):

That bug is claimed to be fixed in

"This is fixed in Insiders 17683 and higher"

As quoted in the title, I am running higher.

Request re-open to determine why this isn't in

@bbulkow commented on GitHub (Aug 10, 2018): That bug is claimed to be fixed in "This is fixed in Insiders 17683 and higher" As quoted in the title, I am running higher. Request re-open to determine why this isn't in
Author
Owner

@DHowett-MSFT commented on GitHub (Aug 10, 2018):

We found a couple more issues in this area. The fix for the last of those issues will probably be in the next insider build.

@DHowett-MSFT commented on GitHub (Aug 10, 2018): We found a couple more issues in this area. The fix for the last of those issues will probably be in the _next_ insider build.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#340