Comment 7 for bug 155927

I tried putting

echo "enabling accessibility"
export GTK_MODULES=gail:atk-bridge
export GNOME_ACCESSIBILITY=1
gconftool-2 --set --type bool /desktop/gnome/interface/accessibility true
/usr/lib/at-spi/at-spi-registryd &

inside ume-xephyr-start.
Running the testing script gave the same bug report error

Setting the environment variables inside gdb
(gdb) set environment GTK_MODULES=gail:atk-bridge
(gdb) run

gave
GTK Accessibility Module Initialized
atk-bridge-warning: AT_SPI_REGISTRY was not started at session startup
atk-bridge-warning: IOR not set
atk-bridge-warning: Could not locate registry

and then the Program exited with code 0377 which means garbage was returned by the OS

I also compiled hail inside the target and substituted hail for gail like:
export GTK_MODULES=/usr/lib/gtk-2.0/modules/lib/gtk-2.0/modules/libhail:atk-bridge

putting this inside the ume-xephyr-start script meant the UI would not
start with this error:
FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.

commenting this out in ume-xephyr-start and exporting it directly from a shell inside the UI gave this:

python moblin-media
creating logfile at /tmp/dogtail/logs/moblin-media/20071119-111356_debug
Hildon Accessibility Module Initialized
Error file accessible.c line 554 (spi_accessible_construct): assertion failed
Aborted (core dumped)

when running the testing script. This seems more encouraging than the original bug reported error message