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

Font rendering makes icons look flattish #22480

New Issue
Open
opened 2026-01-31 08:14:37 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:14:37 +00:00
Owner
Copy Link

Originally created by @dias-yelgonov on GitHub (Oct 31, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.22631.0

Other Software

  1. Oh-my-posh 23.17.0 - 23.20.3
  2. Windows Terminal 1.20.11781.0 - 1.21.2911.0
  3. MesloLGM Nerd Font.
    I've tried it with all sizes of fonts in that font-family.
    Downloaded from same portal, installed in the same way, using settings -> Personalization -> Fonts -> Browse and Install Fonts.
    Clear fonts cache.
    Restart machine on each step.
    Moving all fonts from "good" to "bad" machines

Steps to reproduce

Not sure how to properly describe my issue. And haven't found anything similar.

Three Windows machines, same OS, identical configs for terminal & oh-my-posh theme file.
Two of them have the issue with theme's icons in terminal. They are looking flattish (?) The Windows OS icon looks like a simple square, but on the second machine same icon looks a little bit different due to different angle?

To reproduce:

  1. Run the Windows Terminal with PowerShell session.

Expected Behavior

  1. "Good Machine No 3". Intel based (i7-8750h). That's how it should look like.

Correct rendered version by default, from first session, first run:
Image

Actual Behavior

  1. "Bad Machine No. 1". AMD based (7800x3d). Completely flat, almost fresh system,
    Image
    On this machine, the render issue can be temporarily fixed:
  1. just open the terminal's settings tab (can close it or keep it open, doesn't make sense). Doing nothing there.
  2. Re-open or open new PowerShell session
  3. As long as this terminal's instance (process) is working, all new sessions in existing instance and new instances will be rendered correctly.

But as soon as I close that "fixed" instance (i.e. all active Windows terminals) and open a new one, the same render issue appears.

  1. "Bad Machine No. 2". Intel Based (Core Ultra 5 125h). Different angle of icon, fresh system:
    Image

For this system, the temporary fix doesn't work at all. Nothing works.

Originally created by @dias-yelgonov on GitHub (Oct 31, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.22631.0 ### Other Software 1) Oh-my-posh 23.17.0 - 23.20.3 2) Windows Terminal 1.20.11781.0 - 1.21.2911.0 3) MesloLGM Nerd Font. I've tried it with all sizes of fonts in that font-family. Downloaded from same portal, installed in the same way, using settings -> Personalization -> Fonts -> Browse and Install Fonts. Clear fonts cache. Restart machine on each step. Moving all fonts from "good" to "bad" machines ### Steps to reproduce Not sure how to properly describe my issue. And haven't found anything similar. Three Windows machines, same OS, identical configs for terminal & oh-my-posh theme file. Two of them have the issue with theme's icons in terminal. They are looking flattish (?) The Windows OS icon looks like a simple square, but on the second machine same icon looks a little bit different due to different angle? To reproduce: 1. Run the Windows Terminal with PowerShell session. ### Expected Behavior 1. "Good Machine No 3". Intel based (i7-8750h). That's how it should look like. Correct rendered version by default, from first session, first run: ![Image](https://github.com/user-attachments/assets/5c81bb2f-7ee4-429b-87c1-bd0fcb90609a) ### Actual Behavior 1. "Bad Machine No. 1". AMD based (7800x3d). Completely flat, almost fresh system, ![Image](https://github.com/user-attachments/assets/ec96fbae-d384-42dd-8c65-3cbfdee2d0ac) On this machine, the render issue can be temporarily fixed: 1) just open the terminal's settings tab (can close it or keep it open, doesn't make sense). Doing nothing there. 2) Re-open or open new PowerShell session 3) As long as this terminal's instance (process) is working, all new sessions in existing instance and new instances will be rendered correctly. But as soon as I close that "fixed" instance (i.e. all active Windows terminals) and open a new one, the same render issue appears. 2. "Bad Machine No. 2". Intel Based (Core Ultra 5 125h). Different angle of icon, fresh system: ![Image](https://github.com/user-attachments/assets/40e17cac-283d-49df-bcb7-f93b7f513b44) For this system, the temporary fix doesn't work at all. Nothing works.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:14:37 +00:00
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 Needs-Triage
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#22480
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?