[Ubuntu Wiki] Update of "Accessibility/Specs/SudoAdminAtspi" by
IanJackson
Ubuntu Wiki
noreply at ubuntu.com
Wed Jun 21 09:12:51 BST 2006
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The following page has been changed by IanJackson:
https://wiki.ubuntu.com/Accessibility/Specs/SudoAdminAtspi
The comment on the change is:
bof witter
------------------------------------------------------------------------------
== BoF agenda and discussion ==
+ * Problem with screen reader etc. not working on apps running as root is that accessibility libraries are finding the accessibility bridge by looking in /tmp/orbit-$username-of-current-uid rather than something to do with the display. See http://bugzilla.gnome.org/show_bug.cgi?id=163132.
+ * As a side-effect, this means that a11y doesn't work with remote X displays (eg, LTSP)
+ * The real fix for this is too complicated for us.
+ * However, we think we can make it work by patching the at-spi bridge lookup to use SUDO_USER. This is a grievous hack but doesn't make anything any worse.
+
+ * Another problem is that the display-grabbing of gksu prevents the use of a11y tools with the gksu interface (eg, on-screen keyboard).
+ * There is a gconf key named ??? which can disable this display-grabbing. This "solves" the problem in that it makes it possible to use gksu with a11y tools.
+ * It is not currently clear what the real best solution is; there are good reasons for the grab and naively it would be nice if we could somehow exempt the a11y tools but this is hard (the grab is at a very low level)
== References ==
@@ -41, +49 @@
SvenJaborek: just an idea, try executing xhost + as user before starting the admin tool
-
More information about the Ubuntu-accessibility
mailing list