starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Warning: Unable to find the selected font "Ubuntu Mono". (Also Fixsys Excelsior 3.01) #18858

New Issue
Closed
opened 2026-01-31 06:26:24 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 06:26:24 +00:00
Owner
Copy Link

Originally created by @darth-crunchus on GitHub (Nov 10, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22621.819

Other Software

No other software is affected.

Steps to reproduce

Select "Ubuntu Mono" or "Fixedsys Excelsior 3.01" as fonts for terminal profiles.

Expected Behavior

I expected to be able to set a font that matches the profile I'm running and have it set it without issue.

Actual Behavior

Terminal cannot find the font(s) (but I can):
image

Problem persists if you change settings in the JSON file to be more specific; Change 'Fixedsys Excelsior 3.01' to 'Fixedsys Excelsior 3.01 Regular', as it shows up in C:\Windows\Fonts, and you get this:
image
Same behavior as above for specifying 'Ubuntu Mono Regular' in place of 'Ubuntu Mono':
"Unable to find the selected font "Ubuntu Mono Regular".
"Ubuntu Mono" has been selected instead.
Please either install the missing font or choose another one."
Fonts are installed, dude. Neither repairing Terminal nor restarting is a known fix anymore. The problem persists after a reboot. Problem also persists after resetting Terminal.

Originally created by @darth-crunchus on GitHub (Nov 10, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22621.819 ### Other Software No other software is affected. ### Steps to reproduce Select "Ubuntu Mono" or "Fixedsys Excelsior 3.01" as fonts for terminal profiles. ### Expected Behavior I expected to be able to set a font that matches the profile I'm running and have it set it without issue. ### Actual Behavior Terminal cannot find the font(s) (but I can): ![image](https://user-images.githubusercontent.com/27889886/201084595-c918de37-82f4-4390-8eb7-808758cec2e0.png) Problem persists if you change settings in the JSON file to be more specific; Change 'Fixedsys Excelsior 3.01' to 'Fixedsys Excelsior 3.01 Regular', as it shows up in C:\Windows\Fonts, and you get this: ![image](https://user-images.githubusercontent.com/27889886/201088184-4536c98f-e4fc-434b-9f48-26e61e1ada84.png) Same behavior as above for specifying 'Ubuntu Mono Regular' in place of 'Ubuntu Mono': "Unable to find the selected font "Ubuntu Mono Regular". "Ubuntu Mono" has been selected instead. Please either install the missing font or choose another one." Fonts are installed, dude. Neither repairing Terminal nor restarting is a known fix anymore. The problem persists after a reboot. Problem also persists after resetting Terminal.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:26:24 +00:00
claunia commented 2026-01-31 06:26:25 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 10, 2022):

Could you follow these instructions and let us know if that solves your issue? https://github.com/microsoft/terminal/issues/14231#issuecomment-1280827973

@lhecker commented on GitHub (Nov 10, 2022): Could you follow these instructions and let us know if that solves your issue? https://github.com/microsoft/terminal/issues/14231#issuecomment-1280827973
claunia commented 2026-01-31 06:26:25 +00:00
Author
Owner
Copy Link

@darth-crunchus commented on GitHub (Nov 10, 2022):

Yeah, I'll try it. Edit: So far so good. On both fonts. Took a while to reinstall all 840 fonts, but hopefully this fixed it. Whether it sticks or not remains to be seen.

@darth-crunchus commented on GitHub (Nov 10, 2022): Yeah, I'll try it. Edit: So far so good. On both fonts. Took a while to reinstall all 840 fonts, but hopefully this fixed it. Whether it sticks or not remains to be seen.
claunia commented 2026-01-31 06:26:26 +00:00
Author
Owner
Copy Link

@darth-crunchus commented on GitHub (Nov 11, 2022):

Just don't close it yest, as not sure if it's going to rear its ugly little head again lol

@darth-crunchus commented on GitHub (Nov 11, 2022): Just don't close it yest, as not sure if it's going to rear its ugly little head again lol
claunia commented 2026-01-31 06:26:26 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 11, 2022):

I'll tag it as Needs-Author-Feedback. That way this issue gets automatically closed as fixed in about a week, helping us manage our many issues. That should be enough time to see if it breaks again, right? (Otherwise it's fine to keep this issue open for longer of course.)

@lhecker commented on GitHub (Nov 11, 2022): I'll tag it as `Needs-Author-Feedback`. That way this issue gets automatically closed as fixed in about a week, helping us manage our many issues. That should be enough time to see if it breaks again, right? (Otherwise it's fine to keep this issue open for longer of course.)
claunia commented 2026-01-31 06:26:26 +00:00
Author
Owner
Copy Link

@lynnewu commented on GitHub (Nov 11, 2022):

Could you follow these instructions and let us know if that solves your issue? #14231 (comment)

Same problem in Terminal v1.15.2874.0 with Google Fonts - IBM Plex Mono.

Doing "Install for all users" worked.

@lynnewu commented on GitHub (Nov 11, 2022): > Could you follow these instructions and let us know if that solves your issue? [#14231 (comment)](https://github.com/microsoft/terminal/issues/14231#issuecomment-1280827973) Same problem in Terminal v1.15.2874.0 with [Google Fonts - IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono). Doing "Install for all users" worked.
claunia commented 2026-01-31 06:26:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 11, 2022):

thanks for confirming!

/dup #3257

@zadjii-msft commented on GitHub (Nov 11, 2022): thanks for confirming! /dup #3257
claunia commented 2026-01-31 06:26:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2022):

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 (Nov 11, 2022): 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 Issue-Bug 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#18858
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?