[Bug] Tray icon not spawning on Fedora 43 KDE

[martymarty004]

Content

After a recent update, Vesktop doesn't create the tray icon any more when it launches automatically.

I'm using the option integrated in the client, which creates the app-vesktop@autostart.service that KDE uses to launch the application.

If I open the app from the application launcher, the window would spawn, but the tray icon would not.
The tray icon appears only if I quit completely the program and then relaunch it, or if I disable it and enable it back from Vesktop' settings. If I open the KDE tray settings (for showing/hiding tray icons), the app doesn't appear to be registered.

I can't tell for sure how the issue started, because Vesktop, Plasma and Fedora were all updated together at the same time. Maybe something went wrong during the Fedora upgrade, but since you know what Vesktop should be doing behind the curtains, maybe it will be easier to diagnose the root cause.

System info:

• OS: Fedora 43 KDE
• kernel: 6.17.7
• Plasma: 6.5.2 (Wayland)
• Qt: 6.10.0
• Vesktop: 1.6.1-1 (RPM)

Autostart service logs:

journalctl --user-unit=app-vesktop@autostart.service -b
nov 18 08:25:30 DuckPC-2021v4 systemd[1630]: Starting app-vesktop@autostart.service - Vesktop...
nov 18 08:25:30 DuckPC-2021v4 systemd[1630]: Started app-vesktop@autostart.service - Vesktop.
nov 18 08:25:30 DuckPC-2021v4 vesktop[1968]: Checking for beta autoupdate feature for deb/rpm distributions
nov 18 08:25:30 DuckPC-2021v4 vesktop[1968]: Found package-type: rpm
nov 18 08:25:30 DuckPC-2021v4 vesktop[1968]: Checking for update
nov 18 08:25:30 DuckPC-2021v4 vesktop[1968]: Vesktop v1.6.1
nov 18 08:25:30 DuckPC-2021v4 vesktop[1968]: Enabled Chromium features: AcceleratedVideoEncoder, AcceleratedVideoDecoder, AcceleratedVideoDecodeLinuxGL, AcceleratedVideoDecodeLinuxZeroCopyGL
nov 18 08:25:30 DuckPC-2021v4 vesktop[1968]: Disabled Chromium features: WinRetrieveSuggestionsOnlyOnDemand, HardwareMediaKeyHandling, MediaSessionService
nov 19 00:51:26 DuckPC-2021v4 systemd[1630]: app-vesktop@autostart.service: Consumed 1min 51.918s CPU time, 662.4M memory peak.

[NatKarmios]

I have a similar issue on my Niri/DankMaterialShell setup; it seems like if Vesktop starts before the shell is ready, the tray icon doesn't appear.
I'll try adding a sleep to my launch script and see if that helps.

[ahydronous]

I have a similar issue on my Niri/DankMaterialShell setup; it seems like if Vesktop starts before the shell is ready, the tray icon doesn't appear. I'll try adding a sleep to my launch script and see if that helps.

With systemd unit files you can add a condition to only launch after another target has been launched.
For example After=graphical-session.target or, say if you have problems because you need it to register with D-bus before the graphical session starts, you can do Before=gnome-session-initialized.target or whatever your DE is.

Here Gnome has a bunch of targets, so you can kind of grok the initialization chain a DE goes through. Of course every DE is different so don't take Gnome as gospel.