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 78013 - auto repeat settings use Xfree86 sepecific calls
auto repeat settings use Xfree86 sepecific calls
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Keyboard
unspecified
Other Linux
: High major
: GNOME2.0
Assigned To: Jody Goldberg
Control-Center Maintainers
: 78014 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-04-08 05:37 UTC by Avirupa Chakrabarty
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Avirupa Chakrabarty 2002-04-08 05:37:58 UTC
Reproducibility: Always
Version : 1.99.6
Tested on Linux as well as Solaris 2.9 64 bit platforms. The problem is 
present in both the places.

Procedure:
1. Start up Gnome control center. Double click on the option 'Preferences: 
Keyboard' to open the Keyboard preferences dialog window.
2. Change the speed in the 'Repeat speed' option and delay before 
repeating in the 'Delay before repeating' option and try typing the same 
key on any text editor everytime after changeing the speed and the delay 
before repeating. No change is noticed in the speen of repeatation 
everytime after the speed is changed.
Comment 1 Luis Villa 2002-04-10 02:14:55 UTC
*** Bug 78014 has been marked as a duplicate of this bug. ***
Comment 2 Luis Villa 2002-04-10 02:52:21 UTC
Updating all cc bugs that have the GNOME2 keyword set to the GNOME2.0 milestone,
to help jrb triage/prioritize cc bugs. Filter on 'luis doing GNOME2 work' to
ignore this spam.
Comment 3 Jody Goldberg 2002-04-11 00:25:52 UTC
Damn.
Looks like the settings daemon is using Xfree86 specific calls to change the
repeat rate.  We helpfully silently ignore them if they are not available.
I'll replace with something from the XKB extension.
Comment 4 Jody Goldberg 2002-04-25 04:52:43 UTC
Fixed to default to xkb, and fall back to xfree86 both are checked for
viability first.
Comment 5 Luis Villa 2002-04-30 20:28:25 UTC
Jody: are 78015 and 78016 the same basic bug as this? or no?
Comment 6 Jody Goldberg 2002-04-30 21:19:48 UTC
They would not have been affected by my patch that was strictly related to
autorepeat speed.

Both of those bugs smell like sever mis configuration rather than gnome issues.
They should use xset -q to see if the changes are being applied to the server.
Comment 7 Avirupa Chakrabarty 2002-05-10 06:29:25 UTC
The problem still persists in the latest source taken on May 5th. 
After running xset -q the status of auto repeat shows "off" even 
after setting the repeat speed to short. Hence I am reopening the bug.
Comment 8 Jody Goldberg 2002-05-10 13:27:26 UTC
Is this on solaris ?  Is XKB enabled ?
If so you need to have the latest and greatest xserver.  We currently only
support setting the repeat rate via XKB or xfree86 specific calls (in that
order) if XKB is non functional we're up a creek.
Comment 9 Jody Goldberg 2002-05-17 03:35:42 UTC

*** This bug has been marked as a duplicate of 80325 ***
Comment 10 Avirupa Chakrabarty 2002-05-17 10:54:21 UTC
The bug still persists in Solaris. I tested it on the source code 
taken on 14th of May. Change in the speed of repetition of a character 
is not noticeable on Solaris when changes are made in the repetition 
speed. However it is noticeable on Linux. Hence I am reopening the 
bug.
Comment 11 Jody Goldberg 2002-05-17 12:23:13 UTC
There were 2 portions to this bug.

1) The autorepeat was not being enabled/disabled
This is fixed.

2) The repeat rate and delay were not changing.
On solaris this requires patches to the X server.
That portion  is a duplicate, please do not reopen this bug.
Comment 12 Avirupa Chakrabarty 2002-08-13 07:14:43 UTC
I tested the delay rate change in the beta 2 build. It is still not 
working. May I know the bug id of the bug which is a duplicate of this 
problem.
Comment 13 Jody Goldberg 2002-08-13 15:03:41 UTC
It is part of the generic XKB support is required set of bugs associated with
the AccessX functionality.