Re: [orca-list] I'm getting real tired of apps run as root being inaccessible

[kendell clark <coffeekingms gmail com>]

hi
This is great, we've finally found the bug. Definitely don't call the
guy out, it's not his fault this bug's been around a while, and it's
definitely not his fault I handled it so badly. I'm just glad it's
finally being sorted out. I wouldn't have handled it like this except
that I'm under a lot of pressure because of the installer in sonar being
qt based. Before a few weeks ago I could always rely on the older gtk
based installer but it was getting more and mroe buggy and finally
manjaro people ripped it out, so I have to use the new one. Which is
fine, I like the new one it does a bunch of stuff the older one didn't
do but it's the *only* choice we have, so it has to work.

Thanks again for all of your help, especially luke, who handled my
outburst a lot more calmly than I probably could've done had it been
someone else.
Thanks
Kendell Clark


Luke Yelavich wrote:
> On Tue, Sep 06, 2016 at 10:53:38AM AEST, Luke Yelavich wrote:
> > ok, a small clarrification. i've done some digging, and it turns out qt5 
> > requires qt_linux_accessibility_always_on to be set to 1. whether it also 
> > needs qt_accessibility set to 1 as well i am not sure.
> Ok, some more info.
>
> When an application runs, the accessibility stack attempts to locate at-spi 
> on its own dbus. This is attempted in a couple of different ways. It connects 
> to the session bus to get the information from at-spi directly, and it also 
> retrieves the location of the bus from a root X window property. Both Gtk, 
> actually libatspi, and Qt do this, but it seems that the code in Qt to do this 
> is not being executed for some reason. I am unable to get a Qt5 application 
> to work as root, even with the previously discussed environment variables 
> set. This is on an Ubuntu yakkety install with Qt 5.6, and an ArchLinux 
> install with Qt 5.7. I've asked Frederik Gladhorn from the Qt company about 
> this, and will report back. I also believe he subscribes to this list, but I 
> am not going to call him out, since it seems we are dealing with a bug, and 
> I'll likely have to go through the proper channels to get it sorted.
>
> Luke
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org