You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When opening VSCodium, the application does not set the correct icon for the window under Wayland sessions. Instead it uses the default Wayland icon.
Please confirm that this problem is VSCodium-specific
This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
Please confirm that the issue/resolution isn't already documented
Additional context
This issue does not occur under X11 sessions or when using Microsoft's Visual Studio Code. The issue seems specific to Wayland and VSCodium.
I encountered a similar issue in a pull request for SDR++ and was able to resolve it by explicitly setting the application ID for GLFW using the GLFW_WAYLAND_APP_ID window hint, which had to match the .desktop file. It might be worth investigating whether a similar approach can be applied to Electron (the framework used by VSCodium) to ensure that the correct application ID is set for Wayland sessions.
The text was updated successfully, but these errors were encountered:
Describe the bug
When opening VSCodium, the application does not set the correct icon for the window under Wayland sessions. Instead it uses the default Wayland icon.
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The application should display the correct VSCodium icon in the titlebar/window as expected.
Screenshots
What it currently looks like (from vs codium):
What it should actually look like (from vs code):
Desktop (please complete the following information):
OS: [Arch Linux]
Architecture [x64]
Version: 1.96.0
Commit: 138f619c86f1199955d53b4166bef66ef252935c
Date: 2024-12-16T11:38:33.840Z
Electron: 32.2.7
ElectronBuildId: undefined
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.12.4-arch1-1
App Manager: [yay]
Sandboxed [N/A]
Additional context
This issue does not occur under X11 sessions or when using Microsoft's Visual Studio Code. The issue seems specific to Wayland and VSCodium.
I encountered a similar issue in a pull request for SDR++ and was able to resolve it by explicitly setting the application ID for GLFW using the GLFW_WAYLAND_APP_ID window hint, which had to match the .desktop file. It might be worth investigating whether a similar approach can be applied to Electron (the framework used by VSCodium) to ensure that the correct application ID is set for Wayland sessions.
The text was updated successfully, but these errors were encountered: