at-spi-registryd crash (please attach backtraces, check crash reports before)

[Chito Tuason]

I have the same bug!
"at-spi-registryd"closed unexpectedly

[Chito Tuason (chitotuason)]

gaim is open...

[Daniel Holbach (dholbach)]

Thanks for your bug report. This looks like a duplicate of bug 56452 - which we thought fixed with the same version. Do you remember what you did to get that crash? Is this reproducible?

[Daniel Holbach (dholbach)]

Please try to get a backtrace with http://wiki.ubuntu.com/Backtrace - if the crash report doesn't already contain it.

[John S (jcspray)]

+1, details attached.

[Daniel Holbach (dholbach)]

The crash report does not contain a backtrace.

[tasadar_f (tasadarf)]

I have similar error

[Daniel Holbach (dholbach)]

tasadar_f: your report does not contain a backtrace either.

[Michael (peneycad118)]

I have a similar bug

[Steve Kowalik (stevenk)]

I have seen this as well. However, it is problematic to generate a backtrace from at-spi-registryd, as it drops to T state (in ps aux) whenever you attach to it using either gdb or strace, and kill -CONT'ing it does not help, and it actually makes Gnome in general not respond.

I am more than willing to help debug this problem, but not while it can't be debugged by the means pointed out in the wiki page you linked to.

[Henrik Nilsen Omma (henrik)]

I've not had any crashes after today's update. Anyone else? I've tried to stress it a bit by killing and restarting it as well.

[Henrik Nilsen Omma (henrik)]

Meh, spoke too soon. I just got the crash again :(

However, some observations: First there are two copies of at-spi-registryd running in gnome, one as user and one as root. When I try tol attach gdb to the user version PID I get a general Gnome freeze as Steve says.

If I start KDE from GDM instead of Gnome I get zero copies of at-spi-registryd running (no surprise there). When I then start orca from KDE I get ONE copy of at-spi-registryd and that one accepts a gdb attach. So my plan now is to run that and start lots of gnome apps in Gnome and see if I can provoke a crash.

[Daniel Holbach (dholbach)]

Does anybody have news on this one?

[Daniel Holbach (dholbach)]

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.