[orca-list] what in the world is going on with super user apps

[kendell clark <coffeekingms gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

hi all
I've written about this before, so I'll try to be brief. I've noticed
a couple of issues  with apps being run as superuser being accessible
by orca. Most noticeably gparted, but any app that requires the
standard polkit dialog where you enter your user password, is almost
always inaccessible. However, apps that are run using gksu, that
darken the screen and display the standard, 'enter administrative
password. The applications "appname" lets you modofy essential parts
of your system' prompt, is usually, if not always accessible with
orca. I don't think this is an orca issue, however, I suspect it's
some sort of security policy issue that is preventing at-spi from
either getting at the apps contents or returning those to orca.
Running gksu gparted in the terminal returns errors about the bus not
recieving a reply. I'm writing here just in case someone else has any
thoughts on why this happens or any solutions. I've noticed two other,
possibly related, possibly not issues. Applications that use gksu, as
opposed to policy kit, often take somewhere between five and ten
seconds from the time the desktop icon is clicked or the termina
command is entered before the screen darkens and the prompt shows up.
There is an aditional five to ten second lag after you enter the
correct password and when the application launches. I'm also getting a
lag when orca is first started, or restarted due to a crash, the first
time I alt tab or switch workspaces. People with different and even
less powerful hardware than I have hear say they don't get this
particular lag, so it could be something very odd with my system. I'm
also on mate, so the gksu issues might be mate specific. This is *not*
a complaint about orca. The improvements in firefox over the past
couple weeks are absolutely amazing. I was about to either switch
operating systems or browsers before this got done. Amazing work
everyone. Just trying to figure out what could be causing these couple
of issues.
Thanks
Kendell clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJUEBfCAAoJEGYgJ5/kqBTdyr8P/1yuz6CjWD4X8qlIg6EKxvGU
u+uMHxK9K4mFYG3Xng8ycvMT6nRGom+R598Hw0X7oFhj70uqp5hfh/Y38N+eLmHB
uX7j//6509uhXfA/0TC7dtTWc42ucq7ovdcqG+dutJp0y98/dn7V83LWexGLKds2
V4tZjLAokgEyvQKqjqAQTUjlJFl4iWjEdzDcYIlJcSEzU4zlN6s+eEszptjPCnDA
AjkTk7mUShTUCfgN57YajCm3DcaOlKGtHJK3AuyaVpbeBqcUOf5lVoqMzE5TdmNh
vlD8tXduJ0ZUWfdKPjHkWxl/Ao/t9mmezGaYf9UVCUeJCx1W/WYJQOM3FXc8OMZh
Xg7B/l4MQfIy0/nr0EbScdGlpdzy13L3LDEfgPycMeOCEYxV8RZr1xhQzuEH6GXS
BVHh9p2RLHiaYMup8BM6yC7ENHED5DinF9bobl4B7XobYAB/lbaC72vIibeimct2
wmXXBuoCQTMzSIKHNAsX+EfnLzmgucBhujlsiXCDvGPOUxGmS2I6KBxBCIwH6abh
cXdWt2SnitMsutyWEAGbC8L2LASlkpW8n1u5y1L7CdFem0XL6WCLk6Xxy9ks1sba
ZWG+PWhiATLfRog3YfQBFrTpUtOCsBr8fdWWJa3kXdsl+44evTYfILzLwYC3BM4g
az07Ssm9XcwivOKBCIfr
=F/m1
-----END PGP SIGNATURE-----