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
{{ message }}
Repository navigation
OpenCode Favorite on Dash to Dock results in non-merged instances after upgrade #62918
I removed /usr/share/applications/opencode-desktop/desktop.
When running the freshly upgraded application, I noticed that the pinned favorite was no longer merged with the running instance, causing two icons to be displayed.
Removing the favorite, then re-adding the favorite post-upgrade resolved the issue.
I think this is a duplicate of #61096. Nothing in the Linux packaging changed between 2.2.5 and 2.2.6. Both versions still install the hidden legacy launcher /usr/share/applications/opencode-desktop.desktop, which uses the same StartupWMClass=ai.opencode.desktop as the main ai.opencode.desktop.desktop launcher. An rpm upgrade normally puts back package files that were deleted, so the upgrade most likely restored that launcher and brought back the conflict from #61096. GNOME may also have kept the old window-to-launcher match cached, which would explain why you had to re-pin even after deleting the file again. If #61096 is fixed by removing or changing that legacy launcher, both symptoms should go away.
Possible duplicates and related issues, ordered from most to least likely:
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. For example, if you can confirm that /usr/share/applications/opencode-desktop.desktop was not present after the upgrade and the favorite still didn't merge until you re-pinned it, that would point to a separate problem.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. For example, if you can confirm that /usr/share/applications/opencode-desktop.desktop was not present after the upgrade and the favorite still didn't merge until you re-pinned it, that would point to a separate problem.
As noted, I removed the opencode-desktop.desktop after the upgrade, so it was not present when launching the first time.
Thanks for confirming that opencode-desktop.desktop was already gone before the first launch on 2.2.6. That means this isn't just #61096, so I've kept it open.
I couldn't reproduce it here. It needs the desktop app installed from rpm in a real GNOME Shell session with Dash to Dock, and this sandbox can't provide that. A maintainer on GNOME will need to look at it.
What I could check in the code:
The Linux packaging is identical between 2.2.5 and 2.2.6.
The main launcher is still ai.opencode.desktop.desktop, with the same StartupWMClass=ai.opencode.desktop.
The packaging config defines no rpm upgrade scripts.
So nothing in the packaging explains why the favorite stopped matching. GNOME Shell or Dash to Dock may have kept stale app info after the package upgrade, but that's a guess.
If it happens again on a future upgrade, these would help:
Before re-pinning, does logging out and back in (or restarting GNOME Shell) make the favorite merge again?
Does sudo update-desktop-database /usr/share/applications fix it without re-pinning?
Related: #61096, the legacy launcher sharing the window class.
Activity
opencodejr commentedon Nov 9, 2026
Thanks for the follow-up and the detailed steps!
I think this is a duplicate of #61096. Nothing in the Linux packaging changed between 2.2.5 and 2.2.6. Both versions still install the hidden legacy launcher
/usr/share/applications/opencode-desktop.desktop, which uses the sameStartupWMClass=ai.opencode.desktopas the mainai.opencode.desktop.desktoplauncher. An rpm upgrade normally puts back package files that were deleted, so the upgrade most likely restored that launcher and brought back the conflict from #61096. GNOME may also have kept the old window-to-launcher match cached, which would explain why you had to re-pin even after deleting the file again. If #61096 is fixed by removing or changing that legacy launcher, both symptoms should go away.Possible duplicates and related issues, ordered from most to least likely:
opencode-desktop.desktoplauncher shares the window class, so Dash to Dock doesn't merge the running app with the favorite.The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. For example, if you can confirm that
/usr/share/applications/opencode-desktop.desktopwas not present after the upgrade and the favorite still didn't merge until you re-pinned it, that would point to a separate problem.jrmcpeek commentedon Nov 9, 2026
As noted, I removed the
opencode-desktop.desktopafter the upgrade, so it was not present when launching the first time.opencodejr commentedon Nov 9, 2026
Thanks for confirming that
opencode-desktop.desktopwas already gone before the first launch on 2.2.6. That means this isn't just #61096, so I've kept it open.I couldn't reproduce it here. It needs the desktop app installed from rpm in a real GNOME Shell session with Dash to Dock, and this sandbox can't provide that. A maintainer on GNOME will need to look at it.
What I could check in the code:
ai.opencode.desktop.desktop, with the sameStartupWMClass=ai.opencode.desktop.So nothing in the packaging explains why the favorite stopped matching. GNOME Shell or Dash to Dock may have kept stale app info after the package upgrade, but that's a guess.
If it happens again on a future upgrade, these would help:
sudo update-desktop-database /usr/share/applicationsfix it without re-pinning?Related: #61096, the legacy launcher sharing the window class.