Bug when we start Feisty : trouble with at-spi

There seems to be a problem with AT-SPI 1.7.13. I'm guessing it's due to the changes introduced to allow it to work with sudo. If you force and install of 1.7.12 bit works fine. See: https://lists.ubuntu.com/archives/ubuntu-accessibility-devel/2006-November/000075.html

i have this problem too, I cannot enter in a gnome session and it seems too that feisty can no longer see my wireless card with iwconfig

There were a bunch of updates today. I installed them all and reinstalled AT-SPI 1.7.13. Everything *seems* to be working as expected now.

I reinstalled AT-SPI 1.7.13 and installed all the updates. I still have the error message, but when I click on "Ok", now I can log in.

1.7.12 didn't have the bug, 1.7.13 does.

I assume this the same or a related problem, I'll report it separately if needed.

I did a test of Feisty Herd 1, and selected "F5 > Accessibility". Just before the login screen (I think) I got the following error:

"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."

I got that error once more after clicking OK. Then the login which once gave me the following message from gnome-session 'critical error' that AT_SPI_REGISTRY had not been started at session startup. Then I was sent back to the login menu. I continued to either get that message or the "Your session has lasted less than 10 seconds" message. Of course I couldn't get in to check the contents of .xsession-error.

I can't say more than that. Anyone else tried this with the live-cd?

I also get the message when I log in remotely through nx:

"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."

But I don't get it with vnc.

Here is what I get when I try to reinstall at-spi with the Synaptic Package Manager:

Gtk-Message **: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 54, <> line 1.
GTK Accessibility Module initialized
Gtk-Message **: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 60, <> line 1.
GTK Accessibility Module initialized
Selecting previously deselected package at-spi.
(Reading database ...

Here is what I get when I try to reinstall libatk1.0-0 with the Synaptic Package Manager:

GTK Accessibility Module initialized
WARNING **: AT_SPI_REGISTRY was not started at session startup. at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 54, <> line 1.
WARNING **: IOR not set. at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 54, <> line 1.
WARNING **: Could not locate registry at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 54, <> line 1.
GTK Accessibility Module initialized
WARNING **: AT_SPI_REGISTRY was not started at session startup. at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 60, <> line 1.
WARNING **: IOR not set. at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 60, <> line 1.
WARNING **: Could not locate registry at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 60, <> line 1.
(Reading database ... 228872 files and directories currently installed.)
Preparing to replace libatk1.0-0 1.18.0-0ubuntu1 (using .../libatk1.0-0_1.18.0-0ubuntu1_i386.deb) ...
Unpacking replacement libatk1.0-0 ...
Setting up libatk1.0-0 (1.18.0-0ubuntu1) ...

I hope it can be helpful.

May be that I should clearly tell, that all this problems do not occur when connecting with vnc; in other words when connecting to the gnome session that is automatically started when the computer boots. (May be that the issues are due to nx.)

This bug is marked as 'Needs info'. Could someone from Accessibility tell us what info is needed? Thanks.

[Expired for at-spi (Ubuntu) because there has been no activity for 60 days.]