You are not logged in.

#1 2023-05-11 05:06:43

richdemars
Member
Registered: 2023-05-11
Posts: 2

GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

After doing a pacman update of at-spi2-core to 2.48, GDM 44.1 is slow to start with an around 20 second delay. Doing a downgrade of at-spi2-core to 2.46, then GDM 44.1 starts at a normal speed. I have seem this happen on multiple test systems.

Offline

#2 2023-05-11 06:25:38

killajoe
Member
From: Berlin Planet Earth
Registered: 2007-07-04
Posts: 168
Website

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

i can reproduce the same here and can confirm that downgrading at-spi2-core to previous version solves the lag on GDM .


Cancel me not -- for what then shall remain?
Abscissas, some mantissas, modules, modes, A root or two, a torus and a node:
The inverse of my verse, a null domain.
-- Stanislaw Lem, The Cyberiad

Offline

#3 2023-05-11 06:51:16

seth
Member
Registered: 2012-09-03
Posts: 48,356

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

Maybe more like 25s ?
Sounds like a dbus timeout, check the journal whether some at-spi* process crashes.
If you don't rely on at-spi (a11y stuff) you can probably just (globally)

export NO_AT_BRIDGE=1

Or mask the /usr/share/dbus-1/*services/org.a11y.* services and /etc/xdg/autostart/at-spi-dbus-bus.desktop

Online

#4 2023-05-11 08:10:10

jpamills
Member
Registered: 2013-03-12
Posts: 13

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

Also experiencing the same on both my desktop and laptop. I found the following in my logs:

May 11 16:00:59 [hostname] xdg-desktop-por[1792]: AT-SPI: Error retrieving accessibility bus address: org.a11y.Bus.Error: Failed to execute child process “/usr/bin/dbus-broker-launch” (No such file or directory)

Offline

#5 2023-05-11 08:14:07

seth
Member
Registered: 2012-09-03
Posts: 48,356

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

pacman -Qs dbus-broker

https://archlinux.org/packages/extra/x8 … us-broker/ is listed as *optional* dependency for at-spi2-core, might not be so optional anymore after all…

Online

#6 2023-05-11 08:23:03

jpamills
Member
Registered: 2013-03-12
Posts: 13

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

I just tried installing dbus-broker to see if it would fix it. It doesn't, but the error message changes:

May 11 16:18:57 [hostname] gnome-shell[1864]: 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.

EDIT: found three more entries in the logs 25 seconds earlier:

May 11 16:18:32 [hostname] at-spi-bus-laun[1882]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 16:18:32 [hostname] /usr/lib/gdm-wayland-session[1853]: dbus-daemon[1853]: [session uid=120 pid=1853] Successfully activated service 'org.a11y.Bus'
May 11 16:18:32 [hostname] /usr/lib/gdm-wayland-session[1853]: dbus-daemon[1853]: [session uid=120 pid=1853] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=1864 comm="/usr/bin/gnome-shell")

Last edited by jpamills (2023-05-11 08:25:42)

Offline

#7 2023-05-11 08:27:54

seth
Member
Registered: 2012-09-03
Posts: 48,356

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

Is there more context around the message?
Are there running at-spi* processes?

nb. that the first message was from some xdg-portal implementation, the second one is from gnome-shell

Just a hunch because it recently breaks everything and the kitchen sink): remove xdg-portal-gnome (and use eg. xdg-portal-gtk instead)

Edit:

May 11 16:18:32 [hostname] at-spi-bus-laun[1882]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed

What happens if you try to run /usr/lib/at-spi-bus-launcher manually?

Last edited by seth (2023-05-11 08:30:29)

Online

#8 2023-05-11 09:46:27

jpamills
Member
Registered: 2013-03-12
Posts: 13

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

Running the /usr/lib/at-spi-bus-launcher manually doesn't create any oddities as far as I can see. But I suspect that some of this is an issue with my GDM user/environment as well, making it hard to diagnose from my regular user. The 25 second hang is also present when switching VT back to F1 (where GDM launched) from Gnome. Full logs of that switch below:

May 11 17:27:02 mangosteen kernel: rfkill: input handler enabled
May 11 17:27:02 mangosteen systemd[1]: Created slice User Slice of UID 120.
May 11 17:27:02 mangosteen systemd[1]: Starting User Runtime Directory /run/user/120...
May 11 17:27:02 mangosteen systemd-logind[456]: New session 14 of user gdm.
May 11 17:27:02 mangosteen systemd[1]: Finished User Runtime Directory /run/user/120.
May 11 17:27:02 mangosteen systemd[1]: Starting User Manager for UID 120...
May 11 17:27:02 mangosteen dbus-daemon[454]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.237' (uid=0 pid=16417 comm="(systemd)")
May 11 17:27:02 mangosteen dbus-daemon[454]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
May 11 17:27:02 mangosteen (systemd)[16417]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 11 17:27:02 mangosteen (systemd)[16417]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
May 11 17:27:02 mangosteen (systemd)[16417]: pam_unix(systemd-user:session): session opened for user gdm(uid=120) by (uid=0)
May 11 17:27:02 mangosteen systemd[16417]: Queued start job for default target Main User Target.
May 11 17:27:02 mangosteen systemd[16417]: Created slice User Application Slice.
May 11 17:27:02 mangosteen systemd[16417]: Reached target Paths.
May 11 17:27:02 mangosteen systemd[16417]: Reached target Timers.
May 11 17:27:02 mangosteen systemd[16417]: Starting D-Bus User Message Bus Socket...
May 11 17:27:02 mangosteen systemd[16417]: Listening on GnuPG network certificate management daemon.
May 11 17:27:02 mangosteen systemd[16417]: Listening on GCR ssh-agent wrapper.
May 11 17:27:02 mangosteen systemd[16417]: Listening on GNOME Keyring daemon.
May 11 17:27:02 mangosteen systemd[16417]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
May 11 17:27:02 mangosteen systemd[16417]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
May 11 17:27:02 mangosteen systemd[16417]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
May 11 17:27:02 mangosteen systemd[16417]: Listening on GnuPG cryptographic agent and passphrase cache.
May 11 17:27:02 mangosteen systemd[16417]: Listening on p11-kit server.
May 11 17:27:02 mangosteen systemd[16417]: Listening on PipeWire PulseAudio.
May 11 17:27:02 mangosteen systemd[16417]: Listening on PipeWire Multimedia System Socket.
May 11 17:27:02 mangosteen systemd[16417]: Listening on D-Bus User Message Bus Socket.
May 11 17:27:02 mangosteen systemd[16417]: Reached target Sockets.
May 11 17:27:02 mangosteen systemd[16417]: Reached target Basic System.
May 11 17:27:02 mangosteen systemd[1]: Started User Manager for UID 120.
May 11 17:27:02 mangosteen systemd[16417]: Starting Update XDG user dir configuration...
May 11 17:27:02 mangosteen systemd[1]: Started Session 14 of User gdm.
May 11 17:27:02 mangosteen systemd[16417]: Finished Update XDG user dir configuration.
May 11 17:27:02 mangosteen systemd[16417]: Reached target Main User Target.
May 11 17:27:02 mangosteen systemd[16417]: Startup finished in 68ms.
May 11 17:27:02 mangosteen systemd[16417]: Created slice User Core Session Slice.
May 11 17:27:02 mangosteen systemd[16417]: Starting D-Bus User Message Bus...
May 11 17:27:02 mangosteen systemd[16417]: Started D-Bus User Message Bus.
May 11 17:27:02 mangosteen dbus-daemon[16443]: [session uid=120 pid=16443] Successfully activated service 'org.freedesktop.systemd1'
May 11 17:27:02 mangosteen gnome-session[16447]: gnome-session-binary[16447]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
May 11 17:27:02 mangosteen gnome-session-binary[16447]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
May 11 17:27:02 mangosteen gnome-shell[16457]: Running GNOME Shell (using mutter 44.1) as a Wayland display server
May 11 17:27:02 mangosteen gnome-shell[16457]: Device '/dev/dri/card0' prefers shadow buffer
May 11 17:27:02 mangosteen gnome-shell[16457]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
May 11 17:27:02 mangosteen gnome-shell[16457]: Created gbm renderer for '/dev/dri/card0'
May 11 17:27:02 mangosteen gnome-shell[16457]: Boot VGA GPU /dev/dri/card0 selected as primary
May 11 17:27:02 mangosteen gnome-shell[16457]: Obtained a high priority EGL context
May 11 17:27:02 mangosteen gnome-shell[16457]: Obtained a high priority EGL context
May 11 17:27:02 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=16457 comm="/usr/bin/gnome-shell")
May 11 17:27:02 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Successfully activated service 'org.a11y.Bus'
May 11 17:27:02 mangosteen at-spi-bus-laun[16537]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 17:27:27 mangosteen gnome-shell[16457]: 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.
May 11 17:27:27 mangosteen gnome-shell[16457]: Using public X11 display :1024, (using :1025 for managed services)
May 11 17:27:27 mangosteen gnome-shell[16457]: Using Wayland display name 'wayland-0'
May 11 17:27:27 mangosteen gnome-shell[16457]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
May 11 17:27:27 mangosteen gnome-shell[16457]: Will monitor session 14
May 11 17:27:27 mangosteen dbus-daemon[454]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.241' (uid=120 pid=16457 comm="/usr/bin/gnome-shell")
May 11 17:27:27 mangosteen systemd[1]: Starting Locale Service...
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=120 pid=16457 comm="/usr/bin/gnome-shell")
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=120 pid=16457 comm="/usr/bin/gnome-shell")
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
May 11 17:27:27 mangosteen dbus-daemon[454]: [system] Successfully activated service 'org.freedesktop.locale1'
May 11 17:27:27 mangosteen systemd[1]: Started Locale Service.
May 11 17:27:27 mangosteen systemd[16417]: Started PipeWire Multimedia Service.
May 11 17:27:27 mangosteen systemd[16417]: Started Multimedia Service Session Manager.
May 11 17:27:27 mangosteen systemd[16417]: Started PipeWire PulseAudio.
May 11 17:27:27 mangosteen pipewire[16595]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
May 11 17:27:27 mangosteen pipewire[16595]: mod.rt: found session bus but no portal
May 11 17:27:27 mangosteen pipewire-pulse[16598]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
May 11 17:27:27 mangosteen pipewire-pulse[16598]: mod.rt: found session bus but no portal
May 11 17:27:27 mangosteen wireplumber[16596]: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
May 11 17:27:27 mangosteen wireplumber[16596]: found session bus but no portal
May 11 17:27:27 mangosteen rtkit-daemon[703]: Successfully made thread 16595 of process 16595 owned by '120' high priority at nice level -11.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 7 threads of 4 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Successfully made thread 16598 of process 16598 owned by '120' high priority at nice level -11.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 8 threads of 5 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Successfully made thread 16596 of process 16596 owned by '120' high priority at nice level -11.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 9 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 9 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 9 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 9 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 9 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen polkitd[548]: Registered Authentication Agent for unix-session:14 (system bus name :1.241 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
May 11 17:27:27 mangosteen rtkit-daemon[703]: Successfully made thread 16602 of process 16596 owned by '120' RT at priority 20.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 10 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 10 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 10 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Successfully made thread 16603 of process 16595 owned by '120' RT at priority 20.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 11 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Successfully made thread 16605 of process 16598 owned by '120' RT at priority 20.
May 11 17:27:27 mangosteen rtkit-daemon[703]: Supervising 12 threads of 6 processes of 2 users.
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=120 pid=16457 comm="/usr/bin/gnome-shell")
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension apps-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension auto-move-windows@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/auto-move-windows@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/auto-move-windows@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension drive-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/drive-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/drive-menu@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension launch-new-instance@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-instance@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/launch-new-instance@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension native-window-placement@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/native-window-placement@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/native-window-placement@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension places-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension window-list@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/window-list@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/window-list@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension windowsNavigator@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/windowsNavigator@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/windowsNavigator@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen gnome-shell[16457]: Extension workspace-indicator@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/workspace-indicator@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/workspace-indicator@gnome-shell-extensions.gcampax.github.com will not be loaded
May 11 17:27:27 mangosteen org.gnome.Shell.desktop[16457]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/10a1770076437cb9d2168379722233575700000164470000.ms”: No such file or directory
May 11 17:27:27 mangosteen wireplumber[16596]: [0:34:12.612397540] [16596]  INFO Camera camera_manager.cpp:298 libcamera v0.0.5
May 11 17:27:27 mangosteen gnome-shell[16457]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Successfully activated service 'org.gnome.Shell.Notifications'
May 11 17:27:27 mangosteen gnome-shell[16457]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
May 11 17:27:27 mangosteen dbus-daemon[454]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.247' (uid=120 pid=16638 comm="/usr/lib/gsd-rfkill")
May 11 17:27:27 mangosteen dbus-daemon[454]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.248' (uid=120 pid=16630 comm="/usr/lib/gsd-print-notifications")
May 11 17:27:27 mangosteen dbus-daemon[454]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
May 11 17:27:27 mangosteen systemd[1]: Starting Hostname Service...
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activating service name='org.freedesktop.systemd1' requested by ':1.22' (uid=120 pid=16677 comm="/usr/lib/gsd-sharing")
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
May 11 17:27:27 mangosteen gsd-sharing[16677]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
May 11 17:27:27 mangosteen gsd-sharing[16677]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
May 11 17:27:27 mangosteen NetworkManager[458]: <info>  [1683797247.9144] agent-manager: agent[3b2bd42b0048487f,:1.241/org.gnome.Shell.NetworkAgent/120]: agent registered
May 11 17:27:27 mangosteen dbus-daemon[454]: [system] Successfully activated service 'org.freedesktop.hostname1'
May 11 17:27:27 mangosteen systemd[1]: Started Hostname Service.
May 11 17:27:27 mangosteen kernel: rfkill: input handler disabled
May 11 17:27:27 mangosteen at-spi-bus-laun[16537]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 17:27:27 mangosteen at-spi-bus-laun[16537]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 17:27:27 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Successfully activated service 'org.gnome.Shell.Screencast'
May 11 17:27:27 mangosteen gnome-shell[16457]: Failed to create color profile from colord profile: Error opening file /home/jonathan/.local/share/icc/edid-fd82f00d46d9ffd2d27859c381e18b40.icc: Permission denied
May 11 17:27:27 mangosteen at-spi-bus-laun[16537]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 17:27:27 mangosteen at-spi-bus-laun[16537]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 17:27:27 mangosteen at-spi-bus-laun[16537]: g_dbus_method_invocation_return_dbus_error: assertion 'error_message != NULL' failed
May 11 17:27:28 mangosteen gnome-shell[16457]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
May 11 17:27:28 mangosteen org.gnome.Shell.desktop[16794]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 11 17:27:28 mangosteen org.gnome.Shell.desktop[16794]: > Warning:          Unsupported maximum keycode 708, clipping.
May 11 17:27:28 mangosteen org.gnome.Shell.desktop[16794]: >                   X11 cannot support keycodes above 255.
May 11 17:27:28 mangosteen org.gnome.Shell.desktop[16794]: Errors from xkbcomp are not fatal to the X server
May 11 17:27:28 mangosteen wireplumber[16596]: <WpSiAudioAdapter:0x55806709c740> Object activation aborted: proxy destroyed
May 11 17:27:28 mangosteen wireplumber[16596]: <WpSiAudioAdapter:0x55806709c740> failed to activate item: Object activation aborted: proxy destroyed
May 11 17:27:28 mangosteen gnome-shell[16457]: Registering session with GDM
May 11 17:27:40 mangosteen NetworkManager[458]: <info>  [1683797260.2796] device (wlp6s0): set-hw-addr: set MAC address to XXXXXXXXXX (scanning)
May 11 17:27:40 mangosteen NetworkManager[458]: <info>  [1683797260.2914] device (wlp6s0): supplicant interface state: inactive -> disconnected
May 11 17:27:40 mangosteen NetworkManager[458]: <info>  [1683797260.2914] device (p2p-dev-wlp6s0): supplicant management interface state: inactive -> disconnected
May 11 17:27:40 mangosteen NetworkManager[458]: <info>  [1683797260.2965] device (wlp6s0): supplicant interface state: disconnected -> inactive
May 11 17:27:40 mangosteen NetworkManager[458]: <info>  [1683797260.2965] device (p2p-dev-wlp6s0): supplicant management interface state: disconnected -> inactive
May 11 17:27:52 mangosteen gsd-color[16627]: 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.
May 11 17:27:52 mangosteen gsd-keyboard[16641]: 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.
May 11 17:27:53 mangosteen gsd-wacom[16643]: 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.
May 11 17:27:53 mangosteen gsd-power[16635]: 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.
May 11 17:27:53 mangosteen gsd-media-keys[16637]: 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.
May 11 17:27:53 mangosteen gnome-session-binary[16447]: Entering running state
May 11 17:27:53 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Activating service name='org.gnome.ScreenSaver' requested by ':1.16' (uid=120 pid=16635 comm="/usr/lib/gsd-power")
May 11 17:27:53 mangosteen gsd-media-keys[16637]: Failed to grab accelerator for keybinding settings:hibernate
May 11 17:27:53 mangosteen gsd-media-keys[16637]: Failed to grab accelerator for keybinding settings:playback-repeat
May 11 17:27:53 mangosteen /usr/lib/gdm-wayland-session[16446]: dbus-daemon[16446]: [session uid=120 pid=16446] Successfully activated service 'org.gnome.ScreenSaver'

Offline

#9 2023-05-11 14:00:09

killajoe
Member
From: Berlin Planet Earth
Registered: 2007-07-04
Posts: 168
Website

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

seth wrote:

that the first message was from some xdg-portal implementation, the second one is from gnome-shell

Just a hunch because it recently breaks everything and the kitchen sink): remove xdg-portal-gnome (and use eg. xdg-portal-gtk instead)

xdg-desktop-portal-gnome

removing this does not change the lag here..

Last edited by killajoe (2023-05-11 14:00:24)


Cancel me not -- for what then shall remain?
Abscissas, some mantissas, modules, modes, A root or two, a torus and a node:
The inverse of my verse, a null domain.
-- Stanislaw Lem, The Cyberiad

Offline

#10 2023-05-11 14:03:53

seth
Member
Registered: 2012-09-03
Posts: 48,356

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

https://gitlab.gnome.org/GNOME/at-spi2- … issues/115

According to https://gitlab.gnome.org/GNOME/at-spi2- … launcher.c this is because at-spi-bus-launcher fails to start its own dbus-daemon instance.

The entire thing is triggered by orca (a screenreader)

seth wrote:

If you don't rely on at-spi (a11y stuff) you can probably just (globally)

export NO_AT_BRIDGE=1

Online

#11 2023-05-11 17:57:35

rudolf_schlepke
Member
From: Ukraine
Registered: 2021-02-27
Posts: 20
Website

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

seth's suggestion solved the issue for me.

Offline

#12 2023-05-12 02:21:24

jpamills
Member
Registered: 2013-03-12
Posts: 13

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

Updating to at-spi2-core version 2.48.2 fixed the issue with no further tweaks needed on my side.

Offline

#13 2023-05-12 02:53:24

richdemars
Member
Registered: 2023-05-11
Posts: 2

Re: GDM 44.1 slow to start after at-spi2-core 2.48 upgrade

Updating to at-spi2-core version 2.48.2 fixed the issue on all my test systems also, thanks to all those who help with the update.

Offline

Board footer

Powered by FluxBB