Comment # 16 on bug 957295 from Michael Gorse

Do you have at-spi-bus-launcher running? If so, is it owned by the user running
emacs?

We were intending to phase out the use of toolkit-accessibility and have
accessibility be available on demand, but it also needs not to cause problems
where it is not needed. Anyway, gtk+ no longer checks the key, and the intent
was that other applications would ultimately stop relying on it once they
confirmed that removing the check would not lead to performance issues,
although I believe that firefox still checks the key. Anyway, orca sets the
key, but I don't believe that the focusCaretTracker code does, for instance (so
we may have a bug there, where the focus caret tracker does not work in firefox
unless the key is set). Setting NO_AT_BRIDGE would also mean that, if the
screen reader is started, then existing gtk applications would not have
accessibility enabled until the desktop is restarted. As far as I know, the
only bug being noticed is that we're getting a console warning. If we need to
eliminate it, then my preference would be to patch AT-SPI to remove the
warning, or only display it if toolkit-accessibility is set.