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 118189 - accessX mouse keys
accessX mouse keys
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keyboard Accessibility
unspecified
Other Linux
: High major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
AP1
Depends on:
Blocks:
 
 
Reported: 2003-07-24 13:59 UTC by david.hawthorne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description david.hawthorne 2003-07-24 13:59:47 UTC 
Unsure where to file bug, maybe if it could be re-relocated.

Using gnome-2.4 nightly build from July 24th.

.logged in as root
-go to applications->desktop prefs->accessibility->keyboard
-enable accessiblity features and go to the mouse keys tab and try and
change any of the 3 settings tabs.

.none of them take effect and after confirming them, they are reset the
next time you go to change them.

The following errors appear in the console window when accessing the
settings slider bar:

(gnome-accessibility-keyboard-properties:5942): GConf-CRITICAL **: file
gconf-value.c: line 872 (gconf_value_get_float): assertion `value->type ==
GCONF_VALUE_FLOAT' failed
Comment 1 Calum Benson 2003-07-24 14:50:09 UTC 
Reassigning to control center, Jody or jrb can take it from there :)
Comment 2 Calum Benson 2003-07-24 14:51:12 UTC 
Just to clarify, this only happens when you are logged in as root, not
as a regular user?
Comment 3 david.hawthorne 2003-07-24 15:53:15 UTC 
sorry I should have clarified that - it happens with a normal user
too.

thanks
Comment 4 Calum Benson 2003-08-07 16:05:14 UTC 
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)
Comment 5 bill.haneman 2003-08-21 11:02:01 UTC 
bumping up priority.  This is a stopper IMO since it defeats a basic
keyboard-accessibility/accessx feature and no workaround is apparent.
Comment 6 padraig.obriain 2003-08-21 12:01:27 UTC 
I will have a look at this.
Comment 7 padraig.obriain 2003-08-21 12:47:56 UTC 
This is not reproducible with the latest build.