[Bug] Panel icon no longer displaying

[IrateRedKite]

Discord Account

irateredkite

Operating System

Kubuntu 24.10

Linux Only ~ Desktop Environment

KDE Plasma on Wayland

Package Type

Deb

What happens when the bug or crash occurs?

After updating to the latest version of Vesktop via the autoupdater, the panel icon no longer displays when vesktop is launched with the default args. (--enable-blink-features=MiddleClickAutoscroll --enable-features=UseOzonePlatform --ozone-platform=wayland %Uves)

Launching without these args displays the old icon, but results in GBM-DRV errors

Reverting to previous versions of Vesktop does not seem to fix this issue. The deb install also seems to have some issues with permissions
for opt/Vesktop/chrome-sandbox that had to be resolved by setting the mode to 4755 before I could launch the application after reinstall, it's not clear if this is related to the icon issue.

What is the expected behaviour?

The panel icon displays with the rather pretty Vesktop icon (or any icon at all for that matter)

How do you recreate this bug or crash?

1. Launch Vesktop with vesktop --enable-blink-features=MiddleClickAutoscroll --enable-features=UseOzonePlatform --ozone-platform=wayland %Uves
2. Observed the lack of icon

Debug Logs

Vesktop (no args)
Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: deb
Checking for update
Vesktop v1.5.5
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

Update for version 1.5.5 is not available (latest version: 1.5.5, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is null


Vesktop (default args --enable-blink-features=MiddleClickAutoscroll --enable-features=UseOzonePlatform --ozone-platform=wayland %Uves)

Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: deb
Checking for update
Vesktop v1.5.5
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
Update for version 1.5.5 is not available (latest version: 1.5.5, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is null

Request Agreement

• I have searched the existing issues and found no similar issue
• I am using the latest Vesktop and Vencord versions
• This issue occurs on an official release (not just the AUR or Nix packages)

[IrateRedKite]

This seems as if it might have been an issue with KDE's application launcher, as after fiddling with the menu editor to remove a duplicate entry, as the problem seems to have resolved itself.

I will however leave this open as the default .deb install setting up chrome-sandbox with incorrect permissions to run the app doesn't seem intended. Happy to make a separate issue for this if appropriate.

[Vendicated]

#991