After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 517500 - clicking accessibility applet gives error "gnome-accessibility-keyboard-properties not found"
clicking accessibility applet gives error "gnome-accessibility-keyboard-prope...
Status: RESOLVED FIXED
Product: gnome-applets
Classification: Other
Component: keyboard-accessibility (accessx-status)
2.21.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 520134 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-02-19 18:34 UTC by Sebastien Bacher
Modified: 2008-04-10 22:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
use correct command (568 bytes, patch)
2008-02-20 11:56 UTC, Sebastien Bacher 		committed Details | Review
correct error handling (616 bytes, patch)
2008-04-04 22:26 UTC, Matthias Clasen 		committed Details | Review

Description Sebastien Bacher 2008-02-19 18:34:28 UTC 
The bug has been opened on https://bugs.launchpad.net/bugs/191168

"Binary package hint: gnome-applets

On hardy, I dragged the accessibility applet to the dock. It appears as a little wheelchair, as expected. Clicking it gives an error message. It should bring up the keyboard accessibility control panel.

Strangely enough I can reach that control panel through the Preferences menu.

Apparently this window is reached by running "gnome-keyboard-properties --a11y". So it seems like you either need a shell script under the old name or to update the applet, etc."
Comment 1 Sebastien Bacher 2008-02-20 11:56:07 UTC 
Created attachment 105636 [details] [review]
use correct command
Comment 2 Callum McKenzie 2008-03-02 00:16:57 UTC 
Fixed in SVN. The new code actually checks for both commands, because I'm paranoid about backwards compatibility.
Comment 3 Callum McKenzie 2008-03-03 19:25:19 UTC 
*** Bug 520134 has been marked as a duplicate of this bug. ***
Comment 4 Sebastien Bacher 2008-04-01 22:18:35 UTC 
the change doesn't work correctly the error is stil displayed
Comment 5 Matthias Clasen 2008-04-04 22:26:01 UTC 
Created attachment 108643 [details] [review]
correct error handling

This patch fixes it.
Comment 6 Patrick Wade 2008-04-10 13:57:18 UTC 
Thanks Matthias. Will this be committed soon?
Comment 7 Callum McKenzie 2008-04-10 22:12:03 UTC 
The patch has been applied to both the 2.22 branch and trunk. Sorry for the delay.