Skip to content

OpenCode Favorite on Dash to Dock results in non-merged instances after upgrade #62918

Open

Description

@jrmcpeek

Description

Related to (but is not a duplicate of) #61096.

I upgraded from 2.2.5 to 2.2.6.

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.

Plugins

N/A

OpenCode version

2.2.6

Steps to reproduce

  1. Install the previous stable version of OpenCode
  2. Be running the Dash to Dock gnome-shell extension
  3. Add OpenCode as a favorite
  4. [If OpenCode does not merge with Favorite in Dash to Dock #61096 is not addressed] Remediate favorite merge issue
  5. Launch OpenCode
  6. Observe that opening OpenCode shows an activity pip on the favorite and does not create a second icon
  7. Close OpenCode
  8. Upgrade from the previous stable version to the current stable version of OpenCode
  9. Launch OpenCode
  10. Observe that there are two OpenCode icons on the Dash to Dock toolbar
  11. Close OpenCode
  12. Remove OpenCode as a favorite
  13. Add OpenCode as a favorite
  14. Launch OpenCode
  15. Observe that there is only one OpenCode icon on the Dash to Dock toolbar, where the favorite icon is placed

Screenshot

No response

Operating System

RHEL 9.6

Terminal

bash

Activity

  1. opencodejr commented on Nov 9, 2026

    @opencodejr

    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 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.

  2. jrmcpeek commented on Nov 9, 2026

    @jrmcpeek
    Author

    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.

  3. opencodejr commented on Nov 9, 2026

    @opencodejr

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions