After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796512 - at-spi-bus-launcher makes Xorg server crash when resuming from suspend
at-spi-bus-launcher makes Xorg server crash when resuming from suspend
Status: RESOLVED OBSOLETE
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal critical
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2018-06-06 12:38 UTC by Paulo Marcel Coelho Aragão
Modified: 2020-11-25 15:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paulo Marcel Coelho Aragão 2018-06-06 12:38:06 UTC
If at-spi2-core is installed, when resuming from suspend messages like these are logged in the systemd journal:

at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
at-spi-bus-launcher[31720]:       after 8065 requests (8065 known processed) with 0 events remaining.

The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start.

It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore.

This is a quite severe bug, which makes it impossible to use at-spi2-core.

This was observed with at-spi2-core 2.28.0-1 on Xubuntu 18.04.
Comment 1 Camille Rodriguez 2020-11-24 18:13:30 UTC
Same bug seen on Ubuntu Bionic 18.04.5 LTS with Lenovo P53.

In my case, the bug seen when attempting a domain login (sssd) in ubuntu. About 75% of the time, the login hangs for several minutes, then the screen turns black, and returns to the greater. Once in a while, the user is able to login.

The workaround of removing the at-spi2-core package effectively stops the crashes -- but this removes also other functionalities. For example, nautilus is removed.

Logs of the error :
Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: Unrecoverable failure in required component org.gnome.Shell.desktop
Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: after 21 requests (21 known processed) with 0 events remaining.
Comment 2 André Klapper 2020-11-25 15:09:59 UTC
Obsoleted by https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/27 it seems