Browsers expose only chrome UI over AT-SPI — org.a11y.Bus is never registered on the session bus

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, linux

调研方向

Start with the Pelorus init path that launches the AT-SPI registry and ComputerUse backend, and check whether org.a11y.Bus is ever registered on the session bus. Then reproduce by calling GET /api/desktop/explore/{pid} on a browser window with PELORUS=true and confirming that [document web] nodes have no children. Done means browser page content appears in the tree and org.a11y.Bus.GetAddress answers on the session bus, with AT_SPI_BUS_ADDRESS exported to the desktop session.

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

描述

Summary

With PELORUS=true, the accessibility trees returned by GET /api/desktop/explore/{pid} for browser windows contain only the browser chrome (tab strip, navigation toolbar). [document web] nodes are present but have no children, so page content is invisible to the text-based agent loop. Root cause appears to be that the AT-SPI registry Pelorus starts is never registered on the session bus as org.a11y.Bus — the contract browsers use to decide whether platform accessibility (and therefore DOM a11y trees) is on.

Environment
  • lscr.io/linuxserver/webtop:ubuntu-kde with PELORUS=true (registry + ComputerUse backend start fine; aarch64 host)
  • Affected browsers: Chromium 156 (Ubuntu deb, with --force-renderer-accessibility) and Firefox (distro build and linuxserver proot-apps build, with/without MOZ_ACCESSIBILITY=1) — i.e. not browser-specific
  • Consuming via the Pelorus REST API (response_format: default, stdio-free setup)
What happens
  • explore/{pid} on a Chromium or Firefox window returns only chrome UI, e.g. [page tab list], [tool bar] "Navigation", and [document web] (x, y, 0, 0) nodes with zero-size/empty subtrees, regardless of the loaded page.

  • Firefox logs this at startup:

    AT-SPI: Error retrieving accessibility bus address:
    org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
    
  • Native KDE/GTK apps (Konsole, Dolphin, systemsettings) expose proper trees, so the registry itself and the explore pipeline work.

Root cause analysis
  • org.a11y.Bus does not exist on the container's session bus: org.freedesktop.DBus.ListNames shows no such name, and org.a11y.Bus.GetAddress fails with ServiceUnknown/UnknownMethod.
  • Browsers consult that contract to locate the accessibility bus and decide whether to build content accessibility trees; when it is absent they treat platform accessibility as off.
  • Manually running /usr/libexec/at-spi-bus-launcher --launch-immediately with DBUS_SESSION_BUS_ADDRESS set restores org.a11y.Bus.GetAddress on the session bus — pointing at the same bus Pelorus' registry uses ($XDG_RUNTIME_DIR/at-spi/bus_1) — but the launcher build in the image does not implement org.a11y.Bus.Status (GetIsEnabled/SetIsEnabled → UnknownMethod), and content trees remained gated off even with the browser-specific force flags mentioned above.
Suggested fix

Start at-spi-bus-launcher (a build that implements org.a11y.Bus.Status) with the session bus address during Pelorus/selkies init, before desktop apps launch — or otherwise provide org.a11y.Bus (GetAddress + IsEnabled) on the session bus and export AT_SPI_BUS_ADDRESS into the desktop session environment.

Happy to test a patch or run additional diagnostics.

主要语言
Python
星标
19
派生
1
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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