microsoft / microsoft/vscode-remote-release

Extension icons present but not visible

Open
#11,684 15 comments 18 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

  • VSCode Version 1.123.0 (user setup)
    Commit: 6a44c352bd24569c417e530095901b649960f9f8
    Date: 2026-06-03T11:29:03+02:00
    Electron: 42.2.0
    ElectronBuildId: 14159160
    Chromium: 148.0.7778.97
    Node.js: 24.15.0
    V8: 14.8.178.14-electron.0
  • Local OS Version: Windows_NT x64 10.0.19045
  • Remote OS Version: Ubuntu 22.04 LTS
  • Remote Extension/Connection Type: VS Code Server
  • Logs: Remote ssh log: remote-ssh.log

Steps to Reproduce:

  1. Open folder by ssh to a linux server
  2. See icons not visible

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

After the latest update, when I ssh into my usual workspace I am seeing empty squares or nothing where the usual icons for the extensions would be. The icons are visible on a local session.
e.g. on the left is the remote window and local on the right. Both have gitlens installed but the icon or remote is a simple rectangle.

Image Other missing extensions icons that i have (not) seen are python, code rabbit, atlassian.

Default/microsoft extensions seem to be unaffected.
I have tried

  • reloading the windows
  • restarting vscode
  • disabling and uninstalling all the extensions and reinstalling them.
  • restarting the remote server
  • cleaning up vscode on the remote with
kill -9 `ps -auxf | grep vscode-server | grep mahmad | grep -v grep | awk '{print $2}'`
rm -rf ~/.vscode*

Not a frequent poster here so maybe I am missing some information to add here, please let me know.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reviewing the attached remote-ssh.log and reproducing the difference between local and SSH windows with third-party extensions; done means extension icons render normally in the remote window while default extensions remain unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, ubuntu, vscode
Domain
devtools, networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.