Could this be SRU'd to jammy (gnome-shell 42.9-0ubuntu2.3)? The same bug now affects Google Chrome on 22.04. Since recent versions, the official google-chrome / google-chrome-beta .debs ship a second, NoDisplay=true desktop file (com.google.Chrome[.beta].desktop, for the XDG portal app ID) with the same StartupWMClass as the visible google- chrome[-beta].desktop. On 42.9, scan_startup_wm_class_to_id() compares the full desktop ID (with .desktop) to the class, so the tie-break never fires. The window then gets whichever entry GIO lists first. With google-chrome-beta 155.0.8059.5 that's the hidden entry, so the browser shows up as a separate dock icon from the launcher it was started from.
The two commits from https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/2721 (e7a09946, 12bb3a60) touch only that function and apply to the 42 code, which still has the old comparison. Impact: When two desktop files share a StartupWMClass, windows can be attached to a hidden (NoDisplay/OnlyShowIn-excluded) entry, which gives duplicate dock icons and broken pinning. It currently affects the official Google Chrome .debs (stable, beta, dev) as well as gnome- system-monitor. Chrome-side report: https://issues.chromium.org/issues/568010371 Workaround: printf '[Desktop Entry]\nHidden=true\n' > ~/.local/share/applications/com.google.Chrome.beta.desktop ** Bug watch added: issues.chromium.org/issues #568010371 https://issues.chromium.org/issues/568010371 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012645 Title: Double icon in the dock starting system-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012645/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
