[Bug]: GNOME Wayland: T3 Code cannot be pinned to the dash because its app id resolves to the hidden URL handler entry #32482

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. On GNOME Shell 50 (Wayland), install t3code-nightly-bin from the AUR.
2. Launch T3 Code.
3. Right-click the running T3 Code icon in the dash.

Expected behavior

The menu offers "Pin to Dash", and the pinned launcher groups the running window.

Actual behavior

"Pin to Dash" is missing from the menu. The running window can't be pinned.

This is the part of #13975 that was left open when it was closed ("the window can still appear as a separate dock entry ... please open a new issue for that part only"). Here it shows up as a missing pin option rather than a second icon.

Cause:

1. On every Linux startup, the app calls setDesktopName("com.t3tools.T3Code.desktop") (DesktopPreReadyPlatform.ts#L137, name from DesktopEarlyElectronStartup.ts#L33-L34). That makes the window's Wayland app id com.t3tools.T3Code.
2. Also on every startup, the app writes ~/.local/share/applications/com.t3tools.T3Code.desktop with NoDisplay=true (DesktopPreReadyPlatform.ts#L116-L134, DesktopLinuxUrlHandler.ts#L79-L96).
3. The AUR package installs its visible launcher as t3code.desktop with StartupWMClass=t3code (packaging/aur/t3code-nightly-bin/PKGBUILD#L89-L98). Neither the file name nor StartupWMClass matches com.t3tools.T3Code, so GNOME falls back to the desktop file whose name matches the app id, which is the hidden entry.
4. GNOME Shell only shows "Pin to Dash" when parentalControlsManager.shouldShowApp(appInfo) is true (appMenu.js _updateFavoriteItem()). That function returns false when appInfo.should_show() is false (parentalControlsManager.js), and NoDisplay=true makes should_show() false. appFavorites.js uses the same check, so adding the id to favorite-apps by hand doesn't work either.

Related:

• [Bug]: .deb install on Wayland shows a second, generic dock icon #13975: same root cause on the .deb; closed with the dock-entry part left open.
• [Bug]: Linux Wayland (GNOME, Noctalia) overview shows a placeholder icon after AppImage reinstall #10894: same setDesktopName root cause on the AppImage (icon part fixed in fix(desktop): Install Linux theme icons named after the app id #14471).
• [Bug]: Gnome activities launcher triggers notification instead of switching to the app #27257: GNOME launcher shows a notification instead of switching windows, probably the same app-id mismatch.
• fix(desktop): Group Linux windows under the installed launcher #10895 (open): sets StartupWMClass=com.t3tools.T3Code in the electron-builder and AUR launchers. This should fix GNOME, since GNOME checks StartupWMClass first.
• fix(desktop): Stop hiding an installed Linux launcher with the URL handler entry #31405 (open): skips or removes the hidden entry when $XDG_DATA_DIRS already has com.t3tools.T3Code.desktop. For AUR users this only helps if the AUR launcher is also renamed to com.t3tools.T3Code.desktop; with the current t3code.desktop name, the PR changes nothing for this setup.

Either fix needs a matching change in packaging/aur/t3code-nightly-bin/PKGBUILD (and t3code-bin): set StartupWMClass, rename the launcher to com.t3tools.T3Code.desktop, or both.

Impact

Minor bug or occasional failure

Version or commit

0.1.8-nightly.20261107.4314. The relevant files are unchanged on main @ e455200.

Environment

Manjaro Linux (kernel 7.2.9), GNOME Shell 50.5, Wayland session, installed from the AUR package t3code-nightly-bin

Logs or stack traces

$ echo $XDG_CURRENT_DESKTOP $XDG_SESSION_TYPE
GNOME wayland

# Visible launcher installed by the AUR package
$ grep -E '^(Name|StartupWMClass)=' /usr/share/applications/t3code.desktop
Name=T3 Code Nightly
StartupWMClass=t3code

# Hidden entry the app rewrites on every launch (same id as the window)
$ cat ~/.local/share/applications/com.t3tools.T3Code.desktop
[Desktop Entry]
Type=Application
Name=T3 Code (Nightly)
Exec=/opt/t3code-nightly-bin/t3code %U
Icon=~/.local/share/icons/com.t3tools.T3Code.desktop.png
Terminal=false
NoDisplay=true
StartupNotify=false
MimeType=x-scheme-handler/t3code;

Screenshots, recordings, or supporting files

No response

Workaround

Local PKGBUILD edit in the t3code.desktop heredoc: change StartupWMClass=t3code to StartupWMClass=com.t3tools.T3Code (the #10895 direction). GNOME then matches the window to the visible launcher.

Alternative: patch resources/app.asar in prepare() to blank out the "NoDisplay=true", line in renderUrlHandlerDesktopEntry with 17 spaces (same length, so asar offsets stay valid; EnableEmbeddedAsarIntegrityValidation is disabled), and install the launcher as com.t3tools.T3Code.desktop. The user-local entry the app writes then becomes visible and can be pinned.