Don't hide the menu entry

Bug #41234 reported by Vincent Untz
6
Affects Status Importance Assigned to Milestone
gok (Ubuntu)
Invalid
Medium
Accessibility

Bug Description

From the last gok update:

gok (1.0.7-0ubuntu3) dapper; urgency=low

  * debian/patches/04_menu_change.patch:
    - hide menu entry.

I don't understand why it is hidden. Right now, if you want to try an accessibility tool, you'll have to go to the accessibility pref dialog, enable an option, and see that you have to logout to test it. You have no way to start it now.

I agree that part of it should be fixed upstream, but right now, it feels broken to me.

Revision history for this message
Daniel Holbach (dholbach) wrote :

The decision was taken together with the Accessibility team - the configuration with gnome-at-properties seemed sufficient to everybody and this was done to get rid of a nearly empty Accessibility menu.

Changed in gok:
assignee: nobody → accessibility
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Since the bug was left open I'll chime in and close it. The way AT features are configured and organised ATM is not ideal IMO. See: https://launchpad.net/distros/ubuntu/+spec/common-at-conf for a suggested path to improvement. Removing the menu entry is a right step in this direction IMO. With the default Gnome setup you have to activate GOK in the panel and log out+in to activate it, at which point it pops up on start anyway. So the menu has no useful function as it is. A better option would be to modify the key state applet so that it could also launch the on-screen keyboard.

Thanks for testing the accessibility support though, we need more of that!

Changed in gok:
status: Unconfirmed → Rejected
Revision history for this message
Vincent Untz (vuntz) wrote :

Late answer :-)

FWIW, I disagree on this decision for a simple reason: my keyboard was broken and I could have used gok to do some stuff before rebooting the computer, but it was not possible because the menu was removed. Also, it was good to be able to demonstrate the AT features without logging out. Now, it's harder.

I can understand it might make sense in the general case, and that the real bug is that you have to logout/login to activate it via the capplet.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.