vscode: Broken font icons in terminal

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.67
OS Version: Arch Linux x86_64 & macOS 12

I’m using powerlevel10k theme for my zsh shell. Up until now everything was fine. My MacBook has the same configuration (oh-my-zsh plugin manager, powerlevel10k theme, MesloLGS NF font) and after update the problem appeared.

How it was (1.66)

How it is now (1.67)

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 15
Comments: 24 (8 by maintainers)

Commits related to this issue

fix #148857 — committed to microsoft/vscode by meganrogge 2 years ago
fix #148857 (#148923) — committed to microsoft/vscode by meganrogge 2 years ago
fix #148857 (#148923) — committed to code-oss-dev/code by meganrogge 2 years ago

Most upvoted comments

I used “MesloLGS NF” font with the same issue on insiders as well.

P.S: "terminal.integrated.gpuAcceleration": "canvas": this setting seems to fix it temporarily until a fix is issued.

+18

ViaxCo on May 13, 2022

P.S: "terminal.integrated.gpuAcceleration": "canvas": this setting seems to fix it temporarily until a fix is issued.

I’m still on the stable (non-insider) build and can confirm, that the issue goes away when setting GPU acceleration to “canvas”. Somewhere, I read this before, but it was pointing to another settings option that doesn’t seem to exist anymore.

Version: 1.67.1
Commit: da15b6fd3ef856477bf6f4fb29ba1b7af717770d
Date: 2022-05-06T12:39:22.915Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.17.6-1-MANJARO

fiechr on May 13, 2022

For me this issue is fixed now.

terminal.integrated.gpuAcceleration is set to “auto” and symbols in the terminal are still looking fine.

Version: 1.68.0
Commit: 4af164ea3a06f701fe3e89a2bcbb421d2026b68f
Date: 2022-06-08T11:49:57.055Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.17.9-1-MANJARO

fiechr on Jun 11, 2022

To clarify my above comment, this is fixed in the webgl renderer but not the DOM renderer (tracked in https://github.com/xtermjs/xterm.js/issues/3807#issuecomment-1135035551). If you moved to canvas I recommend switching back to auto or on when this lands in stable as you’ll get much better performance.

Tyriar on May 23, 2022

Just updated Insiders v1.68 to 113287ccc3be52dc3409d451a9b3416d133dca1a and the issue isn’t yet fixed

yn4v4s on May 13, 2022

@fiechr I am confident this will fix it. It would be helpful if you could verify that it’s fixed once this issue gets the label insiders-released in a few days.

meganrogge on May 6, 2022