Multiple Top Bar Icons
As pictured. Started normal with just the regular icon, i went for a walk, came back and saw 2. This morning there were 2 of each type of icon, 4 total. Only one instance of the app is open.
I'm running OpenDeck v2.4.2 (93c40ad) on x86_64-unknown-linux-gnu, on Pop OS
I'm running OpenDeck v2.4.2 (93c40ad) on x86_64-unknown-linux-gnu, on Pop OS
14 Replies
May I ask whats the left icon?
It's my issue, seems to be a second icon for open deck. i can open or quit it using this and the normal icon.
I have 3 now
Locking my OS (using loginctl lock-session) and unlocking it triggered the first, weird icon. Opening Opendeck from my 'Show Applications' page, even though it was already open triggered the 3rd icon.
i have 6 now in my testing. at least its repeatable
If you close opendeck on one icon, does it close all icons? Is autostart turned on in Opendeck?
If its turned on, does this still happens when you turn it off?
disabling autostart doesnt fix it. closing one icon closes a second icon. if i have more than 2 icons, closing one doesnt close them all. i did some troubleshooting with chatgpt and had it write a bug report for me:
🐛 Bug Report: Duplicate Top Bar Icons for Opendeck After Lock/Unlock on GNOME (Pop!_OS)
Environment:
OS: Pop!_OS 22.04 (GNOME-based)
App: Opendeck
Trigger: loginctl lock-session followed by unlocking the session
Desktop: GNOME Shell (Wayland)
Issue:
Each time the session is locked and unlocked, a new Dock/top bar icon appears for the same running instance of Opendeck. This leads to multiple duplicate icons in the GNOME top bar or Dock.
Steps to Reproduce:
Launch Opendeck normally.
Run loginctl lock-session in a terminal.
Unlock the session.
Observe: a new top bar icon for Opendeck appears alongside the existing one.
Repeat the lock/unlock cycle to see more duplicates.
Expected Behavior:
Only one icon should represent the running Opendeck instance, regardless of session locking/unlocking.
Workaround:
Creating a custom .desktop file with the correct StartupWMClass matching the app's WM_CLASS value (from xprop) stops the duplicate icons, but only if the app is launched through that desktop entry. This suggests a window-to-launcher association issue.
WM_CLASS Output:
xprop | grep WM_CLASS
Example output:
WM_CLASS(STRING) = "opendeck", "Opendeck"
Possible Cause:
Opendeck may be:
Not setting a stable or expected WM_CLASS, or
Not matching its runtime window identity to a .desktop launcher GNOME can recognize, or
Re-adding a tray component in a way GNOME misinterprets as a new app window
This is a common issue with Electron/JavaScript-based apps that don’t fully register or persist their session state properly.
Suggested Fix:
Ensure that:
The app sets a consistent WM_CLASS that matches the .desktop entry.
The app launches itself in a way GNOME can tie to its launcher entry, even after session unlocks.
Avoid re-registering the app indicator/tray icon as a new instance on unlock, if applicable.
it's alot, but hopefully it helps.
You said you use gnome as your Desktop Environment?
What way did you install Opendeck?
Because the Issue isn't reproducible for my on my System or my current testing VMs.
and please, don't let Chatgpt create bug reports. Often they are missing something or trying to do the wrong workaround since they don't know the software they are writing a bug report.
interesting, but no one has reported this before, it's probably a bug in gnome or something
anyway, I just use the tauri tray functionality so if there's a bug, it's a bug in that, so if you want to do some further investigation look into any similar issues reported to tauri
Ok. I just tried to reproduce the bug on PopOS with Flatpak installed Opendeck. Couldn't reproduce the Bug. The Thing with the second Icon seems to be a PopOS Specific thing.
Yes there are known issues with pop os and tauri tray. Apparently there are tweaks you can make to tauri.conf.json that may resolve these issues.
If you do, ping me and i'd be happy to test
well, what are they, lmao
oh man im 5 days into linux here, so im not going to pretend to know what im talking about. that being said....
Possible Causes:
Multiple Tray Icon Instances: Tauri v2 can create multiple tray icons if the TrayIconBuilder instance isn't managed properly.
Fix: Ensure that only one instance of the TrayIconBuilder is used, or manage tray icons carefully to prevent duplicates.
Reference: https://github.com/tauri-apps/tauri/issues/10912
Improper Tray Icon Cleanup: Failing to remove tray icons before the app exits can lead to orphaned icons after the app restarts.
Fix: Call TrayIcon.close() in your exit routine to prevent residual icons.
Reference: https://github.com/tauri-apps/tauri/discussions/4668
Changes in Tauri v2: Tauri v2 changes tray icon handling, and the trayIcon setting in tauri.conf.json is no longer used.
Fix: Remove the trayIcon configuration and handle tray icon creation programmatically.
Reference: https://github.com/tauri-apps/tauri/issues/10012
Recommendation: Ensure the app checks for an existing tray icon before creating a new one and implement proper cleanup using TrayIcon.close() before exit.
Mm, none of those look right.