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

Aperta
#1 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, linux

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
19
Fork
1
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.