VSCodium Wayland using Wayland icon instead of app icon

[y0nei]

Describe the bug
This issue popped up just recently, not sure which update but this wasnt the case before.
This doesnt happen with code-oss, package installed via pacman and AUR, both have same issue.

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

• I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. Run KDE Wayland
2. Install vscodium
3. Run "vscodium - Wayland"

Expected behavior
App having the previous assigned icon.

Screenshots

Desktop (please complete the following information):

• OS: Linux 6.12.1-1-cachyos-eevdf GNU/Linux
• Architecture: x86_64
• Version: 1.95.3
• App Manager: pacman, yay
• Sandboxed: no

Additional context
Add any other context about the problem here.

[daiyam]

vscodium-bin isn't managed by us.

@crueter @Icelk Can you help?

[y0nei]

vscodium-bin isn't managed by us.

@crueter @Icelk Can you help?

The vscodium-git AUR package also has this issue

[Icelk]

That's odd. The icon doesn't seem to be changed 🤔 . Made it copy to the "normal" icon place in linux now too. @y0nei can you try the new version in the AUR?

[y0nei]

That's odd. The icon doesn't seem to be changed 🤔 . Made it copy to the "normal" icon place in linux now too. @y0nei can you try the new version in the AUR?

Yea now it has the correct icon lol, but why is the desktop file named codium-wayland instead of vscodium-wayland in /usr/share/applications now? I installed the vscodium-bin package that was the newly updated one.

[Icelk]

Lol great

[Icelk]

Ehrm ill investigate the naming thing tomorrow

[crueter]

Wayland requires icons to be in the standard XDG directory as far as I can tell, its icon spec is weird and doesn't at all follow X11's.

Not sure about the naming thing because I haven't touched the package in a while, totally forgot I was even the maintainer

[Icelk]

@y0nei
Regarding the naming, it has been like that for at least half a year. But either way .desktop file naming is pretty arbitrary right?

[y0nei]

@y0nei Regarding the naming, it has been like that for at least half a year. But either way .desktop file naming is pretty arbitrary right?

Hmm that's funny, just now from that update that fixed the icon issue had the .desktop file names changed for me.
Anyway, should i close this issue now or should i wait till the same fix gets pushed to the regular vscodium packages' PKGBUILD too?

[crueter]

@daiyam manages those two packages, and it doesn't seem to be fixed just yet.

[noonsleeper]

@daiyam I think this is a problem that I fixed on flatpak by a patch https://github.com/flathub/com.vscodium.codium/blob/master/patches/package.json.patch the problem is that the app is reporting a different desktopName then gnome/kde or another wayland compositor try to use that name to match the icon.

[noonsleeper]

if you use gnome you can use looking glass to inspect the window properties https://wiki.gnome.org/Projects/GnomeShell/LookingGlass

wmclass needs to match with the desktopName in order to load the correct icon