The Font Family is INVALID when WSL2 Connected

[zhang-stephen]

Type: Bug

as the title said, I have installed Nerd Font, and configured them as default font family of editor in user settings(windows 11 local).

{
    "editor.fontFamily": "FiraCode Nerd Font Mono, LXGW WenKai Mono"
}

Then I connected to WSL2, openSUSE Tumbleweed here. The configuration of font family has not been applied if I did not copy it into remote user settings(on WSL2).

You can see it in the following screenshot, the right one opened a local folder, its font is expected(FiraCode Nerd Font Mono). And the left one opened a file on WSL2 via remote-wsl, the font is unexpcted, seems to fallback to the windows default font(Microsoft YaHei).

VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z) OS version: Windows_NT x64 10.0.22631 Modes: Remote OS version: Linux x64 5.15.153.1-microsoft-standard-WSL2

System Info

|Item|Value| |---|---| |CPUs|12th Gen Intel(R) Core(TM) i5-12490F (12 x 2995)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|31.82GB (17.60GB free)| |Process Argv|--crash-reporter-id e2d9c286-6e6f-4325-9431-3c2e100e1d4d| |Screen Reader|no| |VM|0%| |Item|Value| |---|---| |Remote|WSL: openSUSE-Tumbleweed| |OS|Linux x64 5.15.153.1-microsoft-standard-WSL2| |CPUs|12th Gen Intel(R) Core(TM) i5-12490F (12 x 0)| |Memory (System)|7.76GB (6.84GB free)| |VM|0%|

Extensions (25)

Extension|Author (truncated)|Version ---|---|--- doxdocgen|csc|1.4.0 todo-tree|Gru|0.0.226 vscode-clangd|llv|0.1.28 vscode-catch2-test-adapter|mat|4.12.0 git-graph|mhu|1.30.0 vscode-language-pack-zh-hans|MS-|1.91.2024071009 debugpy|ms-|2024.8.0 isort|ms-|2023.10.1 python|ms-|2024.10.0 vscode-pylance|ms-|2024.7.1 cmake-tools|ms-|1.18.43 markdown-preview-enhanced|shd|0.8.13 cmake|twx|0.0.17 Bookmarks|ale|13.5.0 spellright|ban|3.0.134 output-colorizer|IBM|0.1.2 fluent-icons|mig|0.0.18 jupyter-keymap|ms-|1.1.2 remote-ssh|ms-|0.113.2024070816 remote-ssh-edit|ms-|0.86.0 remote-wsl|ms-|0.88.2 remote-explorer|ms-|0.4.3 material-icon-theme|PKi|5.4.2 vscode-icons|vsc|12.8.0 material-theme|zhu|3.17.2

[chrmarti]

Check in the Remote tab of the settings editor if you changed this setting for WSL.

[sandy081]

I believe settings are being read correctly in general in local / remote. This setting is not a special one. Hence @hediet Please investigate this first from the editor perspective that if you are getting the setting value in the editor or not. Hence assigning it to you.

[hediet]

@zhang-stephen can you check the font properties in the dev tool? It is unlikely that the editor does not apply the font family setting it receives. So I suspect something else is wrong.

[zhang-stephen]

Check in the Remote tab of the settings editor if you changed this setting for WSL.

the settings of WSL side is default. I had confirmed it when I raised this issue.

@zhang-stephen can you check the font properties in the dev tool? It is unlikely that the editor does not apply the font family setting it receives. So I suspect something else is wrong.

I could have a try, but how to?