[yast-devel] problem with the yast gtk gui
Yesterday, I was trying open suse 12.3 as I was thinking about upgrading my machines. I am totally blind and thus use the gnome version which provides a screen reader that provides blind users with speech and braille feedback of what is happening on their computer. Until yesterday I had no problems using the screen reader which is called orca with the gtk yast gui. When I launched modules from the yast control center in 12.2, accessibility worked and the screen reader read them well. however, in the new version, orca does not read the modules when they are launched from the control center. The only way to get them to read at this point is to type "su" and then run "yast --gtk <module-name>". My guess is that for some reason, the way the control center is launching the modules is not loading all the accessibility parts. I know this worked part way through the development cycle, because I tried the development milestones and things worked. Also this was after gnome 3.6 had migrated in. One thing worth noting is that the live installer on the live cd worked with the screen reader if launched from gnome-shell, however, when launched from the control center, this did not read either. However, the usual workaround of running it with root privilages in the terminal made this module read as well. Does anyone have any suggestions or have any ideas of changes to the gtk yast that could have broken accessibility? Thanks in advance for the help. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 04/10/2013 01:28 PM, am_dxer wrote:
Yesterday, I was trying open suse 12.3 as I was thinking about upgrading my machines. I am totally blind and thus use the gnome version which provides a screen reader that provides blind users with speech and braille feedback of what is happening on their computer. Until yesterday I had no problems using the screen reader which is called orca with the gtk yast gui. When I launched modules from the yast control center in 12.2, accessibility worked and the screen reader read them well. however, in the new version, orca does not read the modules when they are launched from the control center. The only way to get them to read at this point is to type "su" and then run "yast --gtk <module-name>". My guess is that for some reason, the way the control center is launching the modules is not loading all the accessibility parts. I know this worked part way through the development cycle, because I tried the development milestones and things worked. Also this was after gnome 3.6 had migrated in. One thing worth noting is that the live installer on the live cd worked with the screen reader if launched from gnome-shell, however, when launched from the control center, this did not read either. However, the usual workaround of running it with root privilages in the terminal made this module read as well. Does anyone have any suggestions or have any ideas of changes to the gtk yast that could have broken accessibility? Thanks in advance for the help.
Sounds like a gnomesu issue. Perhaps gnome guys know how to solve this issue. Cheers, Thomas -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 04/15/2013 04:45 AM, Thomas Goettlicher wrote:
Sounds like a gnomesu issue. Perhaps gnome guys know how to solve this issue.
Cheers, Thomas
Hi thomas, I appreciate your reply. When launching a YaST module directly with gnomesu, accessibility works. Do you still think it could be gnomesu causing the problem? If not, do you have any other ideas? Thanks again. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
am_dxer -
Thomas Goettlicher