Bug 194054

Summary: keyboard repeat is broken
Product: [Applications] systemsettings Reporter: Nicolas Bigaouette <nbigaouette>
Component: kcm_keyboardAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Nicolas Bigaouette 2009-05-25 18:12:40 UTC
Version:            (using KDE 4.2.3)
Compiler:          gcc version 4.4.0 20090505 (prerelease) (GCC) ./configure --prefix=/usr --enable-shared --enable-languages=c,c++,fortran,objc,obj-c++ --enable-threads=posix --mandir=/usr/share/man --infodir=/usr/share/info --enable-__cxa_atexit --disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic
OS:                Linux
Installed from:    Unspecified Linux

Setting the keyboard repeat is broken in system settings.
First, the repeat delay has a minimum value of 100, and if set to this, the slider bar will be at 165 instead of all to  the left. Same thing for  the rate. The right box shows 25, while the slider bar is located at 50  (max).

Setting the deelay to 100,  ppressing apply, closing and reopening, the slider is still in the middle while the box says 100.  But the keyboard reacts as if it was more like  500.. I kkeep  having multiple press events even if I press keys fast:  konsole gets crazy  when I do "ctrll+tab"  because it thinks I'm pressing multiple times tabs and then bash ask  for completion for everything  in my path. If in an editor, ctrl+tab will often put a  lot of tabs in the document.

This is driving me crazy.. The only way to prevent this is to disable completely tthe repeeat.. But then I need it (talk about going up in a document if yoou  can't keep down the key abut need too press mutliple times...)

I'mm running KDE 4.2.3 on ArchLinux. I don't have an xorg.conf.
Comment 1 Nicolas Bigaouette 2009-11-20 19:09:33 UTC
I can't reproduce the problem on 4.3.3...
Comment 2 Christoph Feck 2009-12-02 09:17:50 UTC
Thanks for the feedback. If this bug shows up again, please reopen.