[Bug 1013623] Re: at-spi2-core does not turn on automatically and cannot be turned on from a menu

[Michael Mess]

What does "at-spi2-core does not turn on" mean?
Does at-spi2 crash when it is started automatically or by menu? 

See the following bugs:
 * Bug 1173033 - at-spi2-registryd crashes with SIGSEGV
 * Bug 1170072 - at-spi2-registryd crashed with signal 7 in g_main_context_check()
 * Bug 1023908 - at-spi2-registryd crashed with signal 5 in g_type_create_instance()
 * Bug 1050856 - orca crashed with signal 5 in _atspi_bus() Edit
 * Bug 855123   - at-spi2-registryd crashed with signal 5 in g_type_create_instance() 

As there are so many bugs open that let this program crash, I assume
that you are really experiencing a crash problem and probably this bug
is just a duplicate of one of the bugs mentioned above.

You can enable Apport so that you can get an error popup when any program crashes when started automatically after login.
When you get the popup you can get more information about the problem by clicking on details.

To do so, type at the command prompt:

gksu gedit /etc/default/apport

Change value of "enabled" from 0 to 1 (instructions are provided in the
text file itself).

See also http://www.techdrivein.com/2012/08/how-to-disable-system-
program-problem.html and https://wiki.ubuntu.com/Apport for more
information

-- 
You received this bug notification because you are a member of
Accessibility, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1013623

Title:
  at-spi2-core does not turn on automatically and cannot be turned on
  from a menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1013623/+subscriptions