Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Each window waits 25 s on the accessibility bus when the account has no desktop session (ssh -X)

Aperta
#372 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

Reproduce the delay on an account without a desktop session, using ssh -X or Xvfb, and trace startup to identify the blocking call; the issue does not name source files or tests to start from. The environment workarounds listed did not remove the wait, so first establish which call blocks before deciding on a fix. Done means the affected ecce startup no longer waits about 25 seconds in this scenario.

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

Descrizione

On a machine where the user has a systemd user session (and therefore a session D-Bus) but has never had a desktop session, every GTK window of ECCE waits about 25 s before it appears. GTK registers with the accessibility bus (org.a11y.Bus, org.a11y.atspi.Registry); no reply comes, and the call ends at the D-Bus default timeout:

dbind-WARNING **: Couldn't register with accessibility bus: Did not receive a reply.

Seen on a Debian 13 host used only over ssh (2026-10-19), started with ssh -X and on Xvfb. Measured with strace: X11 connect to first data server request 25.8 s; with DBUS_SESSION_BUS_ADDRESS=disabled: 0.8 s. After one graphical login on that host the wait was gone (0.8 s). xdg-desktop-portal and xdg-desktop-portal-gtk user units were in the failed state before the login.

Who would see it: users who run ecce on a server over ssh -X, VNC or X2Go with an account that has never logged into a desktop there. Not a local desktop session; not the central-server mode where the client runs on the user's own machine.

Not yet known: which call blocks. NO_AT_BRIDGE=1, GTK_USE_PORTAL=0 and GIO_USE_VFS=local did not remove the wait in a scripted test, so the obvious environment fix is unconfirmed.

Next step: reproduce on an account without a desktop session, find the blocking call, then decide whether ecce sets something when no desktop session is present.

Related: the apps smoke check passed on Builder's 10x10 placeholder window while the main frame never appeared; it should wait for the real main window. The apps suite could also run apps under its own dbus-run-session.

Lingua principale
C
Stelle
10
Fork
8
Merge medio
21m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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.

Altre issue di FriendsofECCE/ECCE

Tutte le issue di FriendsofECCE/ECCE

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.