AT_SPI_REGISTRY not started at session startup [feisty]

[Thomas Wolfe]

Having to type this in from links2 now, so I cannot copy/paste/etc. but after todays updates, I go to login to gnome, and I get the error in the subject line. I think it might have to do with some of those python upgrades since when i searched for AT_SPI_whatever with locate it came up with a lot of python directories. I cannot select 'choose' either to find the package in links2. Sort of a big problem since I cannot even use my desktop. I started a thread in ubuntuforums.org under the feisty dev section and others have this problem too. Any help is appreciated. Thanks.

[Thomas Wolfe (tomwolfe)]

after searching for AT_SPI_REGISTRY in yahoo it seems fedora's dev team also just updated to gnome-session 2.17.2 and I guess now gnome-session starts AT_SPI_REGISTRY again I cannot paste the link, but it looks like they have not really gotten it fixed yet either. Anyone know how I could go about downgrading temporarily until it gets fixed? Thanks again.

[Che Guevara (che-guevara-3)]

Confirmed
Errors:
** (gnome-session:5070): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.
WARNING **: IOR not set.
** ERROR **: Could not locate registry
aborting...

[Thomas Wolfe (tomwolfe)]

Fedora is having the same problem, basically gnome-session 2.17.2 now starts the registry and sometimes it does not start.

[Thomas Wolfe (tomwolfe)]

sorry for multiple comments, damn links2 not showing my comments after i posted them. Anyhow, I just uninstalled (apt-get remove at-spi) and it got rid of a few other packages but after you remove it you can login and use your desktop. (guess the at_spi stuff is for disabled people).

[Che Guevara (che-guevara-3)]

Today's udpdates changed things a bit. When you log in there's a message saying that adaptive something (whatever at-spi support can't be loaded, so a session without support for it will be loaded, but it still bails out

[Che Guevara (che-guevara-3)]

Upstream bug
http://bugzilla.gnome.org/show_bug.cgi?id=345428

[wirelessbit (romm)]

I was wondering if this bug is also affecting Thunderbird loading remote share folders?

When I run:

thunderbird -jsconsole

From the console I get an error as such:
(gecko:3119): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gecko:3119): atk-bridge-WARNING **: IOR not set.

(gecko:3119): atk-bridge-WARNING **: Could not locate registry

I am running:
Ubuntu 9.10 (karmic)
GNOME 2.28.1
Kernel 2.6.31-15-generic

If I run only thunderbird from the console then I get the same error:
(gecko:3164): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gecko:3164): atk-bridge-WARNING **: IOR not set.

(gecko:3164): atk-bridge-WARNING **: Could not locate registry

The error does not allow me to connect to my remote share folders that contain the .sdb folders.
Yes I check all the configurations in the system including permission, I can access the same share folders from my Windows systems using Thunderbird with the exact same configuration as the one in my Ubuntu system and works fine.

>Mel<

[SwaJime (john-swajime)]

I'm getting this same error from "sudo nm-applet"

I don't see what this has to do with the "duplicate" yelp bug other than that it has the same error message.

$ sudo nm-applet
(nm-applet:3700): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(nm-applet:3700): atk-bridge-WARNING **: IOR not set.
(nm-applet:3700): atk-bridge-WARNING **: Could not locate registry
john

[SwaJime (john-swajime)]

Still looking to see how to fix this ...
I get this set of error messages for pretty much everything ...

# gnome-volume-control-applet --display=":0"
(gnome-volume-control-applet:10259): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-volume-control-applet:10259): atk-bridge-WARNING **: IOR not set.
(gnome-volume-control-applet:10259): atk-bridge-WARNING **: Could not locate registry
** (gnome-volume-control-applet:10259): WARNING **: Applet is already running, exiting

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.10
Release: 9.10
Codename: karmic

[sterios prosiniklis (steriosprosiniklis)]

2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

I get this set of error messages for pretty much everything ...
Solved, worked around with

gconftool-2 -s --type=bool /desktop/gnome/interface/accessibility false