Browsers expose only chrome UI over AT-SPI — org.a11y.Bus is never registered on the session bus
まだ誰も着手していません。
評価
- 難易度
- 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-kdewithPELORUS=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/withoutMOZ_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.Busdoes not exist on the container's session bus:org.freedesktop.DBus.ListNamesshows no such name, andorg.a11y.Bus.GetAddressfails withServiceUnknown/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-immediatelywithDBUS_SESSION_BUS_ADDRESSset restoresorg.a11y.Bus.GetAddresson 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 implementorg.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 ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
mohanraj00/entelos#200 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 68/100
-
sweep
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
bketelsen/truenas-mcp#77 ·
メンテナーはふだん 1 日以内に返信
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskオープン
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
sandbox-quantum/switch#2163 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
openedx/xblock-lti-consumer#765 ·
メンテナーはふだん 1 日以内に返信