caja gksu: apps launched by caja gksu are inaccessible to orca about caja-extensions HOT 7 OPEN

That's the question to Orca devs. Can it read anything from app that's run as root?

from caja-extensions.

hi

The problem is universal. Orca can't read any apps run as root because
it can't get at them to read them. It's a problem we've been struggling
to figure out. Policy kit helps a little bit but still, the only desktop
that consistently gets around this is gnome shell, and I have no idea
what they do to achieve it.

Thanks

Kendell Clark

On 08/29/2016 03:54 PM, monsta wrote:

That's the question to Orca devs. Can it read anything from app that's
run as root?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzGmHgHFeJiBGlYUGws1Wcds6YOTDZhks5qk0cHgaJpZM4H82qW.

from caja-extensions.

hi
The solution seems to lie in gnome settings-daemon. They have code in
there to set up the gtk and qt modules for accessibility when an app is
launched, no matter what user starts the program. Would you guys mind
looking at gnome settings-daemon's code to see if you can figure out
what code needs to be added to mate settings-daemon to fix this? This is
not limited to running apps as root through caja-gksu, but any app run
as root in any way while mate is used, both the gtk2 and gtk3 versions.
The only reason I'm asking is because the manjaro guys have removed the
old installer sonar was using and now we have to use a qt based
installer, which is accessible but only when run as a non root user
because of this bug, so it's pretty important this bug get fixed. I'll
help in any way I can, I don't expect this to be done for me. If you
like I can try looking through the code myself and report what I find to
hear. Just let me know.
Thanks
Kendell Clark

kendell clark wrote:

hi

The problem is universal. Orca can't read any apps run as root because
it can't get at them to read them. It's a problem we've been
struggling to figure out. Policy kit helps a little bit but still, the
only desktop that consistently gets around this is gnome shell, and I
have no idea what they do to achieve it.

Thanks

Kendell Clark

On 08/29/2016 03:54 PM, monsta wrote:

That's the question to Orca devs. Can it read anything from app
that's run as root?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzGmHgHFeJiBGlYUGws1Wcds6YOTDZhks5qk0cHgaJpZM4H82qW.

from caja-extensions.

They have code in there to set up the gtk and qt modules for accessibility when an app is launched, no matter what user starts the program.

I wonder how they did that - settings daemon is running as user...

from caja-extensions.

Just to make sure, can you also check gnome-flashback? I wonder if it's really g-s-d (which is also used in flashback session) or maybe gnome-session (which isn't used there as flashback is a separate session on its own).

from caja-extensions.

hi
I'd be glad to test flashback. Is it still maintained? I seem to
remember it being unmaintained since, I think it was gnome 3.6 but I'll
test that right now since I've got nothing else pressing to do.
Thanks
Kendell Clark

monsta wrote:

Just to make sure, can you also check gnome-flashback? I wonder if
it's really g-s-d (which is also used in flashback session) or maybe
gnome-session (which isn't used there as flashback is a separate
session on its own).

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzGmF7bo_U9xXa6f_W4KH3eSPKYz-HRks5qnXgEgaJpZM4H82qW.

from caja-extensions.

Yes, it's maintained now, there are some developers working on it. Stable release is at 3.20.x now.

from caja-extensions.