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 660947 - at-spi2-registryd crashed with signal 5 in __libc_start_main()
at-spi2-registryd crashed with signal 5 in __libc_start_main()
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Li Yuan
Depends on:
Blocks:
 
 
Reported: 2011-10-05 01:40 UTC by Luke Yelavich
Modified: 2011-10-06 15:48 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Threaded stack trace. (1.15 KB, text/plain)
2011-10-05 01:40 UTC, Luke Yelavich 		Details

Description Luke Yelavich 2011-10-05 01:40:40 UTC 
Created attachment 198285 [details]
Threaded stack trace.

Stack trace attached.
Comment 1 Luke Yelavich 2011-10-05 01:41:20 UTC 
Whoops, should have added that at-spi2 is at 2.2.0, the entire stack.
Comment 2 Mike Gorse 2011-10-06 15:48:15 UTC 
It looks as though multiple instances of at-spi2-registryd are being started, and instances started after the first one will abort.  I suspect a race where multiple applications start in succession and register with atk-bridge before at-spi2-registryd actually starts to execute and registers the name.  I've made it gracefully exit(0) rather than call g_error and trigger a SIGABRT.