Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A at-spi2-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • at-spi2-core
  • Issues
  • #115

AT-SPI slowing GDM start

Description

After updating to at-spi2-core ver 2.48.1-1, GDM is taking too long to show. After investigation, I found that GDM was waiting at-spi to start, while at-spi was giving this issue in journalctl:

archlinux gnome-shell[754]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

It takes around 30 seconds until this error occurs and in the meanwhile, the screen is black with a dot waiting GDM

Steps to reproduce

  1. Update to at-spi2-core ver 2.48.1-1
  2. Reboot

My system

Arch Linux
Wayland
Gnome 44

Edited May 11, 2023 by Rudah Ximenes
Assignee
Assign to
Time tracking