[orca-list] more on inaccessibility when run as root

[kendell clark <coffeekingms gmail com>]

hi all
Since I'm trying to improve the accessibility of the mate desktop, I've
been digging into why apps being launched as root are inaccessible to
orca. Joanie pointed out that generating a debug log wouldn't help
because orca isn't recieving any events so can't process them. I think
I've found a reproduceable way to encounter the issue. Steps to
reproduce. 1: Log into mate in your favorite login manager. 2: make sure
orca starts. 3: run an app that requires root privs, example gparted. 4:
Log out and log back into a desktop such as gnome or unity which this
does work. Do not restart, but press the log out button in mate's menus.
then try to launch the same app you just did using mate. What should
happen is that orca should then read the app. But this doesn't work.
This leads me to think this is an at-spi, rather than an orca issue. But
I'll need help from someone smarter than me to tell for sure. If anyone
can confirm or at least get close, I'll file a bug against at-spi2-core
so that this can get fixed. Note that this happens in cinnamon also
sometimes but not always. I think it may have something to do with the
fact that when logging out, the copy of at-spi2-registryd isn't killed,
instead a new instance is spawned, which can sometimes lead orca to
start but not speak because you can only have so many instances going at
once. Why orca doesn't connect to the existing one I don't know but I'm
sure it tries to.
Thanks
Kendell clark