Orca fails to run in latest Lucid update
Bill Cox
waywardgeek at gmail.com
Tue Jan 12 17:10:36 GMT 2010
D'oh! This is just what Willie told me to do before:
$ gconftool-2 --set /desktop/gnome/interface/at-spi-corba --type bool true
If you execute this, then at-spi-registryd can run, and Orca starts.
Bill
On Tue, Jan 12, 2010 at 11:08 AM, Bill Cox <waywardgeek at gmail.com> wrote:
> Anyone else seeing this? After an apt-get upgrade, Orca no longer
> works. Here's what gets reported:
>
> vinux at vinux-laptop:~$ orca
>
> (orca:1830): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at
> session startup.
>
> (orca:1830): atk-bridge-WARNING **: IOR not set.
>
> (orca:1830): atk-bridge-WARNING **: Could not locate registry
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/usr/lib/pymodules/python2.6/orca/orca.py", line 1747, in main
> init(pyatspi.Registry)
> File "/usr/lib/pymodules/python2.6/orca/orca.py", line 1266, in init
> registry.registerEventListener(_onChildrenChanged,
> File "/usr/lib/python2.6/dist-packages/pyatspi/registry.py", line
> 331, in __getattribute__
> raise RuntimeError('Could not find or activate registry')
> RuntimeError: Could not find or activate registry
>
>
> I can track this down, but if you have already figured it out, or have
> pointers for me, I'd like to hear from you.
>
> Thanks,
> Bill
>
More information about the Ubuntu-accessibility
mailing list