Bug 2001374 - GDM needs ~30s to appear after startup - `AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply`
Summary: GDM needs ~30s to appear after startup - `AT-SPI: Error retrieving accessibil...
Keywords:
Status: CLOSED DUPLICATE of bug 2001057
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-05 20:53 UTC by bjoern.daase
Modified: 2021-09-06 05:24 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-09-06 05:24:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description bjoern.daase 2021-09-05 20:53:13 UTC 
### Affected version

* Fedora 35
* Gdm 41.alpha

### Bug summary

Since I updated to 41.alpha on F35, GDM needs a super long time (~30s) to appear after startup.
F34 did not show this behavior.

### Steps to reproduce

1. Power on your PC
2. Wait for GDM

### What happened

GDM needs ~30s to appear.

### What did you expect to happen

Instantly display GDM.

### Relevant logs, screenshots, screencasts etc.

I have a
```
Aug 26 07:42:39 p14s-gen2-amd gnome-shell[1559]: 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.
```
in the journal, indicating that it is a dbus timeout somewhere.
Comment 1 bjoern.daase 2021-09-06 05:24:49 UTC 

*** This bug has been marked as a duplicate of bug 2001057 ***
Note You need to log in before you can comment on or make changes to this bug.