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

[Jude DaShiell <jdashiel panix com>]

Hi Kendal,

kde has accessibility support in kde-accessibility package group and a 
blind person needs the whole orca stack to enable it but exactly how it 
is enabled I don't fully understand yet.  The kaccessible program for 
instance supposedly specializes in reading qt stuff while orca probably 
ought to be used for non-qt stuff.

On Mon, 5 Sep 2016, kendell clark wrote:

> Date: Mon, 5 Sep 2016 06:21:20
> From: kendell clark <coffeekingms gmail com>
> To: orca-list gnome org
> Subject: Re: [orca-list] I'm getting real tired of apps run as root being
>     inaccessible
>
> hi
> I read your email again and I must've missed the stuff about qt the last
> time.
>
> Yes, I have run the installer as root. I can't get much past the
> keyboard layout section before the installer figures  out it's not run
> as root but yes, it's completely accessible when run as a normal user.
> Well, as accessible as qt apps ever get, flat review by word doesn't
> seem to work but other than that it works fine.
>
> So now I'm confused. It looks like there is a bug somewhere after all.
> If all gnome and unity do is load gtk modules, that means that apps that
> don't use gtk would still be inaccessible. I have tried the installer
> and other qt apps in gnome and they are inaccessible when run as root.
>
> Oops, sorry about that I keep forgetting to indent, I know that makes it
> easier for you to read my mails. So now I'm wondering if maybe it's an
> at-spi problem? sudo -E works for apps like gparted, but it doesn't work
> on the installer and mumble, and apps run as qt. Which means it can't be
> an at-spi problem or gtk apps wouldn't work but maybe qt?
>
> Thanks
> Kendell Clark
>
>
> kendell clark wrote:
> > hi
> > Wonderful! I'll file a bug right now. So it's not that there's a bug so
> > much as things haven't been set up the right way. That can be fixed. Is
> > this similar for qt applications as well? The installer we will use from
> > now is qt5 based, and is completely accessible when run as the normal
> > user but not when run as root. Which modules are loaded? If I can get
> > that I can try creating a file in /etc/profile.d as a stop gap until the
> > bug can get fixed properly. Ditto for qt?
> > Thanks
> > Kendell Clark
> >
> >
> > Luke Yelavich wrote:
> > > Hi Kendell.
> > > On Mon, Sep 05, 2016 at 03:21:14PM AEST, kendell clark wrote:
> > > > hi all
> > > > The subject line pretty much says it all. I'm not writing in to rant but
> > > > I want to crush this bug once and for all. Since manjaro has removed the
> > > > old installer sonar used to use, we have to use their new installer,
> > > > called calamares. The devs have been fantastic and fixed all of the very
> > > > few accessibility bugs that app did have, except for one very annoying
> > > > bug. It's run as root so orca can't get at it.
> > > The way Qt handles working with at-spi is different to the way GTK works with at-spi, see below for more on 
> > > this. So I am surprised that this is an issue. Have you verified that the installer GUI is usable if you 
> > > start it from a normal user account? Yes it wouldn't be able to work properly, but surely the GUI would work 
> > > enough for you to check its accessibility.
> > >
> > > > I'm sick of this one
> > > > cropping up and getting in the way. It only seems to affect mate
> > > > desktop, even the gtk3 version. The only desktops that can somehow get
> > > > around this one are gnome and unity. How are they doing it so I can
> > > > either emulate it or have someone look at the code and port it over to
> > > > mate?
> > > It has to do with how the GTK modules are set up. Unity and GNOME have code
> > > in their settings daemon plugins that configure things such that the GTK
> > > modules are always loaded when an application loads, irrispective of the user
> > > account they are run from. I am guessing mate still sets things up using the
> > > GTK_MODULES environment variable, and I'd hazard a guess that under certain
> > > circumstances, this variable is not set when a GTK based application is run
> > > as root. The circumstances I refer to have to do with how one gains root
> > > privileges to run the app. You can use sudo directly with the command, or you
> > > can drop to a root shell then run the app using sudo -i. I think sudo
> > > preserves more of the environment with sudo -i than it does when using sudo
> > > directly, although using sudo -E should preserve the environment and
> > > therefore pass through GTK_MODULES such that things work.
> > >
> > > Ultimately the best solution would be for the mate devs to examine GNOME's
> > > settings daemon code and port the gtk-modules configuration code over to
> > > mate-settings-daemon.
> > >
> > > Hope this helps.
> > >
> > > 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
>
> _______________________________________________
> 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

--