Description of problem:
When keeping the function keys or /*-+ of the numeric keypad pressed, only one
action/character will be executed/created.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start X & xterm
2. keep / pressed for some seconds
only one '/' appears
I'm unable to reproduce this. I'm getting as many other people as I can
muster up to also test it to see if anyone at all out there can reproduce
it first though.
Created attachment 89798 [details]
Strange; I see it at least on 4 machines. They are differing from the RH beta
in the following points:
- an ~/.Xmodmap file (see attachment)
- Gnome1 desktop-environment
The "InputDevice" in /etc/X11/XF86Config-4 on one of the affected machines is
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
Well those are rather IMHO significant "differences" from the Red Hat
beta. Can you reproduce this problem on a stock phoebe system without
any addons or customizations? ie: no GNOME 1, no custom Xmodmap files,
no custom anything?
I don't want to research this further until I know we're playing on an
even field here, in particular because nobody has been able to reproduce
this so far.
I can reproduce it without Gnome1 and/or a custom ~/.Xmodmap file:
| $ X &
| $ DISPLAY=:0 xterm
DISPLAY=:0.0 xterm &
/*-+ on the numeric keypad won't repeat. Other keys on the keypad do repeat,
including numbers when numlock is turned on. /*-+ on the normal part of the
keyboard do repeat. Tried "xset r on" with no change.
Ok, I've done a completely fresh install of the latest tree, and I can
now reproduce this with XFree86-188.8.131.52-20030129.4. Reporting bug upstream.
Ivan Pascal found and fixed this issue quite a while ago, which got into
4.3.0, and should be fixed and working in Red Hat Linux 9.
I just tested my 9 box, and the / * - + keys on the numeric keypad, and the
Fx keys autorepeat ok in xev.
Closing bug as fixed in CURRENTRELEASE of RHL 9. If the problem comes back,
report the bug upstream at http://bugs.xfree86.org, and reopen this bug and
put the upstream bug report URL here and I'll track it.