[Hardy] at-spi issues

[Shirish Agarwal]

Binary package hint: at-spi

I'm using GDM for login. After logging while I'm going to metacity normal mode, I get this message box.

"Assistive technology has been requested for this session, but the accessibility registry was not found. Please ensure that the AT-SPI package is installed. You session has been started without assistive technology support."

Then at various points in time I get these kind of messages (as an e.g.) :-

shirish@Mugglewille:~$ deluge

(deluge:1812): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(deluge:1812): atk-bridge-WARNING **: IOR not set.

(deluge:1812): atk-bridge-WARNING **: Could not locate registry
checking for ubuntu...
found and fixing ubuntu
shirish@Mugglewille:~$
(deluge:2351): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(deluge:2351): atk-bridge-WARNING **: IOR not set.

(deluge:2351): atk-bridge-WARNING **: Could not locate registry
checking for ubuntu...
create proxy object
create iface
send to iface

at-spi is version 1.21.5-1 also have libatk1.0 & others which are needed, gnome-session is 2.21.91-0ubuntu2 any help/guidance would be appreciated.

[Luke Yelavich (themuso)]

I use hardy daily, and do not get this problem with accessibility enabled. Have you tried removing all GNOME related settings from your home directory, and starting afresh to see if you get the same messages?

[Shirish Agarwal (shirishag75)]

Hi Luke,
      Can u tell me which all gnome related settings should I remove my home directory or if u can point me to some list which people have compiled to remove. If not you will have to tell me one by one, there is also possibility that somebody might have made a script for doing the same.

Any help/guidance is appreciated.

[Tina Russell (tinarussell)]

I get the same problems. Usually, it seems to happen if I restart X.

Deleting all my GNOME settings sounds like a scary proposition! So, ehhh, not right now.

I also cannot use Mousetweaks... at all, whether or not I've restarted X on any particular session. I guess that's related... is there a way of telling whether or not the accessibility registry has activated in effect (rather than merely in name)? I mean, the registry daemon is running, but other than that, I can't tell...

Thanks!

[Luke Yelavich (themuso)]

One way you could check if the at-spi registry is running is to use an app like accerciser or dogtail to probe applications via the at-spi framework.

[sbq (sam-quiring)]

See this link for an explanation (but not necessarily a solution): http://osdir.com/ml/gnome.gdm.general/2007-08/msg00011.html.

I get this problem on occasion when I'm running Ubuntu in VMware. I've was told that restarting Gnome will usually fix it. So I ssh into Ubuntu and use this command:

sudo /etc/init.d/gdm restart

This has worked pretty well for me.

-Sam

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Could test the current Ubuntu development version? It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 193.

[Charlie Kravetz (cjkgeek)]

There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Could test the current Ubuntu latest version? It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 193470.

[Charlie Kravetz (cjkgeek)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Charlie Kravetz (cjkgeek)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!