AT SPI registry not responding

Bug #577113 reported by steros on 2010-05-07
This bug affects 23 people
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
Nominated for Lucid by amy

Bug Description

I upgraded from 9.1 to 10.04 two days ago, and now every time I try to shut down the message "AT SPI registry not responding. I've had a look on the net and the common fix seems to be start up programs or assistive technologies . The registry does not appear on my start up list, and the assistive technologies are not selected. This is a minor problem I know, but annoying when in a hurry. Today the only way to by-pass it is to turn the power off. Can somebody please advise me on how to fix it?

I have the same problem as questioned here, but it's not an option to add a shutdown button for me.


Philip Muškovac (yofel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at I have classified this bug as a bug in at-spi.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at

affects: ubuntu → at-spi (Ubuntu)
tags: added: lucid
amy (a7mdyassin) wrote :

affects me too.. also running Lucid.. terribly annoying...

Medor (bogkuz) wrote :

affects me to...

Ramaddan (ramaddan) wrote :

it affects me too, but i usually get it after programs randomly freeze, and i get that a lot, which makes my atom based device unreliable.

tell me if you need any information, and how to get that information.

Thank you

Ramaddan (ramaddan) wrote :

I noticed it happens more to hang when I use "gksu", just in case that is useful

Charlie Kravetz (charlie-tca) wrote :

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in at-spi (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
steros (steros) wrote :


thanks for marking it.
Somewhere else, sad thing i do not know where, someone stated he has the exact same thing when using "eclipse".
I can confirm this.
If i use eclipse that error appears on shutdown otherwise not.
They reported the case to the eclipse developers as far as i remember.


SGosnell (spamtrap47) wrote :

I usually get it after Nautilus crashes. Nautilus crashes or won't load, everything hangs, and when I reboot, I get an error dialog saying AT SPI Registry is not responding, and usually File Manager is also not responding. It's getting to be very frequent in Lucid.

David Oxland (doxland) wrote :

This is happening to me when trying to use update manager and then it hangs after which killall will not work; and states " another Synaptic is running."

Pita (petermartischka) wrote :

A "sudo apt-get autoremove at-spi" helps. So the bug must be in this package

Charlie Kravetz (charlie-tca) wrote :

@Pita : that is incorrect reasoning. The fact the removing the package helps means it could be an issue with the package removed or another package that is conflicting with the removed package. Removing the at-spi package is simply a workaround that works for some people with this issue.

Karesz (lengyel-karesz) wrote :

also affects me on natty

George Masters (gmasters2) wrote :

This same message also appears in ubntu-mate 16.04 during shut down. Not sure why it is happening. I closed all foreground applications I had running on the desktop. I finished updating the system using the GUI Software Updater tool, then played a few rounds of PySol solitaire. After finishing that game, I exited the PySol app. I then attempted to shutdown and got the message that the desktop is not responding referenced above. Wondering if it is a long-standing issue with Mate specifically. I have not seen that with earlier versions running Unity or LXE desktops.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers