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 684167 - Crash.
Crash.
Status: RESOLVED OBSOLETE
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: High critical
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-09-16 23:39 UTC by Luke Yelavich
Modified: 2014-11-13 17:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Threaded stack trace. (4.77 KB, text/plain)
2012-09-16 23:39 UTC, Luke Yelavich 		Details

Description Luke Yelavich 2012-09-16 23:39:40 UTC 
Created attachment 224467 [details]
Threaded stack trace.

Originally filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1050856

The user experienced a crash after attempting to disable Orca, and reboot. Threaded stacktrace attached.
Comment 1 André Klapper 2012-09-17 08:53:18 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Mike Gorse 2012-09-18 01:58:55 UTC 
I don't think that debugging symbols would help--it looks like Orca (or something using AT-SPI) is still being started and is unable to get an address for the accessibility bus, so it errors out.
Is org.a11y.Bus.service from at-spi2-core being installed to an appropriate place on ubuntu? If not, then this might explain the crash, if toolkit-accessibility was turned off but not screen-reader-enabled, since the former starts at-spi-bus-launcher automatically, but otherwise it should be loaded on demand in theory. I'm unsure at the moment if not that.

That being said, I'm not sure if calling g_error() is the right thing to do here.
Comment 3 Luke Yelavich 2012-09-18 02:44:09 UTC 
Yes, the service files for at-spi2-core are being installed to the correct location.
Comment 4 André Klapper 2013-08-14 10:05:50 UTC 
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 5 Magdalen Berns (irc magpie) 2014-11-13 17:52:40 UTC 
I'm going to go ahead and close this because it concerns a very old version.
Feel free to open a new bug if the problem persists.