Browsers expose only chrome UI over AT-SPI — org.a11y.Bus is never registered on the session bus
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 22/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- docker, linux
- Bereich
- accessibility, desktop-dev
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Python
- Sterne
- 19
- Forks
- 1
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Ähnliche Issues
-
author-page correction move-papers
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
acl-org/acl-anthology#10978 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
PostgreSQL results table stores labels with single quotes, and a double quote in a label fails the writeEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
GoogleCloudPlatform/professional-services-data-validator#1899 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
HKUDS/CLI-Anything#652 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Project-N-E-K-O/N.E.K.O#3813 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Dao-AILab/flash-attention#3191 ·
Maintainer antworten meist innerhalb von 4 Tagen