[Lucid] When I run any program with sudo command, the system does'nt found atk-bridge module and Orca does'nt handle the application accessibility

[Attila Hammer]

Binary package hint: gnome-orca

Dear Developers,

Possible I not send right package this bugreport.

When I running any program with sudo (for example the gedit application), I see following message, and the launched application is inaccessible with Orca screen reader with Lucid alpha 1:
For example, I run sudo gedit command, and see following result in gnome-terminal:
hammera@hammera-laptop:~$ sudo gedit
[sudo] password for hammera:

Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory

After this output, gedit is launched, but inaccessible with Orca screen reader.

In /etc/sudoers file contains following right line:
Defaults env_reset

Defaults env_keep = "ORBIT_SOCKETDIR XDG_SESSION_COOKIE GTK_MODULES"

Another problem, the system/shutdown and system/logout dialogs now are inaccessible again.

Attila

ProblemType: Bug
Architecture: i386
Date: Wed Dec 16 13:10:27 2009
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091214)
Package: gnome-orca 2.29.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-8.12-generic
SourcePackage: gnome-orca
Tags: lucid
Uname: Linux 2.6.32-8-generic i686

[Attila Hammer (hammera)]

Libatk-bridge.so is does'nt missing my system. The find --name
libatk-bridge.so command shows following result:
/usr/lib/gtk-2.0/modules/at-spi-corba/modules/libatk-bridge.so

Possible need a new g-conf key configuration with is not setted now by
default?

Attila

[WaywardGeek (waywardgeek)]

I can confirm that this happens on my Ubuntu Lucid alpha install. I tried to see if the problem would go away by simply deleting all my ~/.* directories and re-logging in. It does not fix the problem. I also tried setting the same value needed to get orca working:

sudo gconftool-2 --set /desktop/gnome/interface/at-spi-corba --type bool true

This had no effect. However, I can enable the root account with 'sudo passwd', and then 'su' to root, and then launch programs like synaptic, and they are accessible.

[Attila Hammer (hammera)]

Bill, when I updated my system with this morning, have some at-spi and
py-atspi upgrades. When I installed all updates and restart my system,
the sudo launched programs are accessible again.
System/shutdown and system/logout dialogs are accessible again.

Please update your system, and if you confirming this result, this bug
is fixed the developers.

Attila

[WaywardGeek (waywardgeek)]

If we modify /etc/sudoers to enable ORBIT_SOCKETDIR to be passed to the sudo command, then Orca is able to control the application.

[WaywardGeek (waywardgeek)]

I did a new install of Ubuntu Lucid alpha, and upgraded to the latest code. I still get this bug on my system, but there is no longer any reported problem loading libatk-bridge.so. However, 'sudo synaptic' still results in synaptic being inaccessible. However, 'sudo -E synaptic' works! I tracked down the variable that needs to be passed to the sudo environment: ORBIT_SOCKETDIR. If I add this line to /etc/sudoers (using visudo) then sudo works without the -E command:

Defaults env_keep+="ORBIT_SOCKETDIR"

Hopefully this can be added to the /etc/sudoers file by default.

[Luke Yelavich (themuso)]

I don't think we'd be allowed to add this by default, but it can certainly be added when the accessibility profile is chosen on the live CD.

[Luke Yelavich (themuso)]

This was fixed in the accessibility profiles blindness and braille during the jaunty cycle.