at-spi2 daemon error messages in .xsession-errors

[Till Kamppeter]

Sometimes I get the following messages in .xsession-errors

init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped

I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode.

Can perhaps have a relation with bug 1227173.

[marmuta (marmuta)]

Perhaps try to get debug output out of at-spi2-registryd. There might be better ways, but I would replace it with a script. Something like

sudo mv /usr/lib/at-spi2-core/at-spi2-registryd{,_}
sudo tee << "EOF" /usr/lib/at-spi2-core/at-spi2-registryd
#!/bin/bash
G_MESSAGES_DEBUG=all /usr/lib/at-spi2-core/at-spi2-registryd_ $* &>>/tmp/at-spi2-registryd-$USER.log
EOF
sudo chmod +x /usr/lib/at-spi2-core/at-spi2-registryd

The output should end up in /tmp/at-spi2-registryd-*.log.

[Till Kamppeter (till-kamppeter)]

Note that in LightDM I have activated the on-screen keyboard via the Accessibility menu for login via touch screen.

Succeeded login:

/tmp/at-spi2-registryd-till.log:
----------
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

** (at-spi2-registryd_:32693): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd_:32693): WARNING **: Unable to register client with session manager
----------

.xsession-errors:
----------
Script for cjkv started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped
----------

Starting Onboard (to work in tablet mode) adds to /tmp/at-spi2-registryd-till.log:
----------
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

** (at-spi2-registryd_:953): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd_:953): WARNING **: Unable to register client with session manager
----------

And nothing to .xsession-errors.

Logout adds to /tmp/at-spi2-registryd-till.log:
----------
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
----------

And nothing to .xsession-errors.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[rtimai (rtimai)]

Ubuntu 13.10 amd64 upgrade, no proprietary drivers, all updates current.
Content of .xsession-errors:
-----
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped
------
I have NO IDEA what is causing this. No observable issues during operation.

[hackel (hackel)]

Looks like this is caused by /usr/share/dbus-1/services/org.a11y.atspi.Registry.service which contains the --use-gnome-session parameter. Is this necessary?

I tried adding a /usr/share/dbus-1/services/org.gnome.SessionManager.service like so:
[D-BUS Service]
Name=org.gnome.SessionManager
Exec=/usr/bin/gnome-session

This caused lightdm to go a little nuts, and a blank wallpaper after logging in. I also tried removing --use-gnome-session from org.a11y.atspi.Registry.service, but this didn't help. In the end, I ended up just disabling at-spi-dbus-bus.desktop since I don't actually need accessibility features, but this is hardly a solution.

[Colin Law (colin-law)]

Present in 14.10RC

[Fabian Boehnlein (fabian-boehnlein)]

Present in 14.04LTS.

Not solveable by chown user:user .Xauthority to active user, as some googling suggests.

[jimav (james-avera)]

Still present in 14.10

[Launchpad Janitor (janitor)]

This bug was fixed in the package at-spi2-core - 2.16.0-1ubuntu1

---------------
at-spi2-core (2.16.0-1ubuntu1) wily; urgency=medium

  * Merge from Debian unstable, remaining changes:
    - Load the at-spi2 registry as part of the Ubuntu upstart user session
  * Remove respawn keyword from upstart file, the service gets restarted via
    dbus if required (LP: #1228567)

 -- Luke Yelavich <email address hidden> Mon, 18 May 2015 14:43:06 +1000

[rtimai (rtimai)]

Bug present in 15.04 amd64-desktop.

2014/09/09: Above mentioned fixed release at-spi2- core 2.16.0 1ubuntu1 is still not available in the repositories. Current in Ubuntu 15.04 is at-spi2-core 2.14.0-1ubuntu2.

Looks mostly like a cosmetic fix, but looking forward to it anyway. I guess I'll remove the dbg module now. : )

[Hans Deragon (deragon)]

Any chances to have this bug backported to 14.04 LTS Trusty Thar? Current version is 2.10.2.is.2.10.1-0ubuntu1.

[Cerin (chrisspen)]

What is the workaround for 14.04? I just did a routine update and this has made my computer unusable.

[Colin Law (colin-law)]

@Cerin: I believe this bug has little impact. If your machine is unusable then it is likely a different problem.

[Daniel C (daniel314)]

@Colin: I'm experiencing the same issue. Installing updates to 14.04LTS on my laptop in early December has made the GUI on my computer unusable as well. It's a ThinkPad, I think with a stock Intel video chipset in it. Here is the output of my .xsession-errors file:

Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped
init: gnome-session (Unity) main process (11515) terminated with status 1
init: logrotate main process (11404) killed by TERM signal
init: update-notifier-crash (/var/crash/_usr_bin_nm-applet.104.crash) main process (11451) killed by TERM signal
init: indicator-bluetooth main process (11638) killed by TERM signal
init: indicator-power main process (11640) killed by TERM signal
init: indicator-datetime main process (11641) killed by TERM signal
init: indicator-session main process (11655) killed by TERM signal
init: indicator-application main process (11671) killed by TERM signal
init: Disconnected from notified D-Bus bus

[Daniel C (daniel314)]

One addendum: the permissions of my ~/.X* files are good (I own them and they're writeable), and the permissions on /tmp and /tmp/.X11* look correct as well. I moved ~/.config/dconf out of the way as well, and that didn't make a difference either.

[Daniel C (daniel314)]

Using the script that Marmuta suggested at the top generates two files. Here is the content of the user one:

SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

** (at-spi2-registryd-:14335): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd-:14335): WARNING **: Unable to register client with session manager
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

** (at-spi2-registryd-:15092): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd-:15092): WARNING **: Unable to register client with session manager

-------------------------------------------------------------------------------------------

Here is the lightdm one:

SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

** (at-spi2-registryd-:14804): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd-:14804): WARNING **: Unable to register client with session manager
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

** (at-spi2-registryd-:15577): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd-:15577): WARNING **: Unable to register client with session manager

[Apotessar (apotessar315)]

It seems that I encountered a problem similar to what Daniek C has. From Jan. 1st my Fujitsu laptop SH782 running Ubuntu 14.04 repetitively fails to start the working environment after I correctly enter the login password. The login screen appears again and again.

According to the log files, I guess something wrong gets /usr/bin/X terminated.

.xsession-errors
----------------------------------------------------------------------------------------------
Script for ibus started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: gnome-session (Unity) main process (2474) terminated with status 1
init: unity-settings-daemon main process (2460) killed by TERM signal
init: at-spi2-registryd main process ended, respawning
init: logrotate main process (2364) killed by TERM signal
init: update-notifier-crash (/var/crash/_usr_bin_Xorg.0.crash) main process (2415) killed by TERM signal
init: update-notifier-crash (/var/crash/_usr_lib_ibus_ibus-ui-gtk3.1000.crash) main process (2426) killed by TERM signal
init: xsession-init main process (2452) killed by TERM signal
init: hud main process (2467) killed by TERM signal
init: unity-panel-service main process (2480) killed by TERM signal
----------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------
[+0.03s] DEBUG: Launching process 1312: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
:
:
[+7.63s] DEBUG: Session pid=1407: Authentication complete with return value 0: Success
[+7.63s] DEBUG: Session pid=1359: Authenticate result for user harold: Success
:
:
[+7.66s] DEBUG: Session pid=1407: Logging to .xsession-errors
[+7.67s] DEBUG: Activating VT 7
[+7.67s] DEBUG: Activating login1 session c2
[+8.08s] DEBUG: Session pid=1407: Exited with return value 0
[+8.08s] DEBUG: Seat: Session stopped
[+8.08s] DEBUG: Seat: Stopping display server, no sessions require it
[+8.08s] DEBUG: Sending signal 15 to process 1312
----------------------------------------------------------------------------------------------

[Emil Mottola (mottola-emil)]

Extremely frustrating.
I had updated to Trusty 14.04 , and upgraded the linux kernel to
3.13.0.77-lowlatency

After 2 days of searching on the internet, and all suggested fixes failed,
I finally compared line for line the ownership and permissions of

.config/dconf

in the home directory of one user (emil) where this annoying behavior did not occur
with the corresponding

.config/dconf

of the second user (sharon) where the immediate logout after login behavior occurred
with gnome classic desktop (either compiz or metacity).

I moved sharon's dconf directory out of .config renaming it dconf.old
Then I copied all of user emil's dconf to user sharon and meticuously did
sudo chown and sudo chmod on the new .config/dconf in sharon's home
directory making sure all the ownership and permissions were identical
for this user as they were for the first one.

Then I rebooted.
That did the trick.

Of course, user sharon lost her personalized gnome window settings which were
replaced by those of user emil, but these can be recustomized without problem.

This seems to me a fairly drastic and unusual step to have to take on a distribution
upgrade. I have found no other solution, so I consider this a bug I hope someone will look into.

[smile1324 (smile13241324)]

Not sure that this is fixed. I had the very same problem today and I am using ubuntu 15.10 desktop.

After my wife tried to login an xOrg error was reported. After that my unity desktop refused to load showing only the background image. I have finally got it back running by renaming my ~/.config/dconf/user and subsequently loose my desktop settings.

I think this is a very serious issue especially for I was not doing any updates or driver changes before this error occured, it simply happend out of the blue which is quite frightening.

Hopefully someone will find time to look into this.

[daniel (danersti)]

Hi, I found a workaround, look into /home/youruser/.xsession-errors and if you find something like this
Xlib: extension "GLX" missing on display ":0".
Script for ibus started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped

then open /usr/lib/at-spi2-core/ and remove the execution flag on both the files inside, reboot the system and check that no at-spi2 or similar process is running

[Fayce (fayce66)]

Habing the same problem! Friday everything was working fine. Started my desktop PC this morning, login, then nothing happens at all, no panel, no menu nothing. Workaround for now is CTRL+ATL+F1, login in terminal, stop ligthdm and startxfce4 manually.

I tried all the solutions suggested in many different blogs, nothing works!
 my .xsession-errors only shows:

openConnection: connect: No such file or directory
cannot connect to brltty at :0
Script for none started at run_im.
init: no-pinentry-gnome3 main process (2163) terminated with status 1
init: gnome-keyring-gpg main process (2176) killed by TERM signal
init: Disconnected from notified D-Bus bus

That's it! Any new suggestions on how to fix this appreciated. Thanks.