Hi! I have the question about the proper gail and atk-bridge modules loading for GTK+ application to enable their accessibility. At first orca startup it asks usual questions and make some changes to enable GNOME accessibility. On next GNOME launch at-spi2-registryd is present in processes list but orca speaks only its greeting. The command "export GTK_MODULES=gail:atk-bridge" before GTK-based application startup (including orca itself) lets me enable proper accessibility navigation inside of this application but I don't know how these modules must be loaded automatically for every application inside of GNOME environment. Please, give me any recommendation how I can debug this problem!
Currently I have on my system libgtk+-3.2.3, at-spi2-core-2.2.3 and orca-3.2.2. I am using ALT Linux distribution. It is not based on Debian or Ubuntu packages so the problem can be caused by incorrect GNOME components packaging. Thanks! -- Michael Pozhidaev. Tomsk, Russia. Russian info page: http://www.marigostra.ru/ _______________________________________________ gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
