Repository navigation
Cascadia Mono Font not found: Release fix to stable #12879
Description
Windows Terminal version
1.12.10732.0
Windows build number
10.0.19044.1586
Other Software
No response
Steps to reproduce
Start the terminal.
Expected Behavior
No error messages, font works fine.
Actual Behavior
Error message
"Warning: The selected font "Cascadia Mono" was not found.
"Consolas" was selected instead
Install missing fonts or choose a different one.
Most suspiciously, looking in the Microsoft Windows Store, it shows that an update has been executed just today, so it heavily suggests that an update broke it.
#12420 (comment) says this was fixed in the release version more than 2 weeks ago, can this land in the stable release?
Reacted by Colin Ingram
Activity
csi-lund commentedon Apr 11, 2022
Interesting that seems to affect VS as well
restarting doesnt fix.
maxgerhardt commentedon Apr 11, 2022
The terminal in the preview version works for me (https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-13-release/) and when you look on disk where the preview terminal is there is also that font file. Maybe just installing the preview version fixes VisualStudio too?
zadjii-msft commentedon Apr 11, 2022
Alas, that's actually how this issue occurs. Something about the update process leaves the font file locked in a way such that we can't read the file any longer.
As mentioned, this is already fixed in Preview, hopefully. I think we're gonna let this one bake there for a little while to make sure it A. actually worked and B. doesn't make things worse somehow.
... Though, looking at #12554, I think we ended up servicing that to a 1.12 version, but I'm not sure which. Dustin L. Howett (@DHowett) we may want to push the latest 1.12 release actually to GH.
[-]Cascidia Mono Font not found: Release fix to stable[/-][+]Cascadia Mono Font not found: Release fix to stable[/+]srdjanjovcic commentedon Apr 13, 2022
This issue is reproducible in Preview 1.13.10983.0 for me.