[Bug Report] Chromium WebApps display generic fallback gear icon in Wayland due to StartupWMClass / app_id mismatch

未关闭
#410 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
python
领域
desktop

调研方向

Start by locating the Chromium-based browser launcher generation logic in webapp-manager and tracing how it sets StartupWMClass and installs icon assets. Check how Chromium’s Wayland app_id and desktop icon lookup behave for the supported browsers and profiles. Done means the launcher groups with the running window and displays its chosen icon without creating duplicate app entries; the issue names no source files or tests.

由索引模型根据 Issue 内容生成。

描述

[Bug Report] Chromium WebApps display generic fallback gear icon in Wayland due to StartupWMClass / app_id mismatch

Environment

  • OS: Zorin OS 17/18 / Linux Mint (Wayland session)
  • Desktop Environment: GNOME Shell / Zorin Desktop
  • Application: webapp-manager (Ice SSB)
  • Browser: Google Chrome / Chromium (Ozone platform: Wayland)

Steps to Reproduce

  1. Open WebApp Manager.
  2. Create a new WebApp using Google Chrome (or Chromium/Brave) pointing to https://music.youtube.com/.
  3. Select an icon (custom or preset) and save.
  4. Add the WebApp to Favorites / Dash.
  5. Launch the WebApp.

Expected Behavior

The running window should group under the pinned WebApp launcher on the dock/taskbar with its designated icon.


Actual Behavior

The running window fails to group with the launcher and appears as a separate taskbar entry displaying a generic gear ("carenagem") placeholder icon.


Root Cause Analysis

  1. Wayland app_id Generation in Chromium:
    When running under Wayland (--ozone-platform=wayland), Chromium ignores the command line switch --class=WebApp-<name><id>.
    Instead, Chromium calculates the Wayland surface app_id via shell_integration_linux using the pattern:
    chrome-<host>__<path>-<profile> (e.g. chrome-music.youtube.com__-Default).

  2. Launcher Mismatch:
    webapp-manager writes:

    StartupWMClass=WebApp-MusicGoogle7059
    

    Because StartupWMClass does not match the Wayland app_id, the window manager (GNOME Shell / Mutter) cannot link the surface to the .desktop file and falls back to a generic window icon.


Proposed Fix

In webapp-manager launcher generation logic for Chromium-based browsers:

  1. Parse the WebApp URL to compute the expected Wayland app_id:
    from urllib.parse import urlparse
    parsed = urlparse(url)
    host = parsed.netloc or parsed.path
    wayland_app_id = f"chrome-{host}__-Default"
    
  2. Set StartupWMClass directly to the calculated wayland_app_id (chrome-<host>__-Default) instead of WebApp-<codename>.
    • Note on Best Practice: Do not create a secondary symlink like <wayland_app_id>.desktop in ~/.local/share/applications/, as doing so causes desktop environments (e.g. GNOME / Zorin Menu) to index and display duplicate application entries in the app launcher. Setting StartupWMClass alone is 100% sufficient for GNOME Shell / Mutter to map the surface window to the single existing .desktop launcher.
  3. Ensure the icon asset is copied to ~/.local/share/icons/hicolor/<size>/apps/ under the wayland_app_id name so the window manager reliably resolves it.
主要语言
Python
星标
1k
派生
132
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

linuxmint/webapp-manager 的其他 Issue

查看 linuxmint/webapp-manager 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。