You are not logged in.
Pages: 1
Recently updated evdev 2.2.0 has changed the previous default keyboard speed settings (delay and repeat). I've STFW'd and saw many different ways to manage the keyboard speed but as we are now in the age of hal policies, what would be the right way to handle this?
TIA
Offline
I had the same problem and making a regular xorg.conf didn't change anything. I ended up adding this to ~/.xinitrc and things are the way that they use to be:
xset r rate 200 30
Offline
Thanks skottish, that's exactly what I did (and had the same issue with xorg.conf BTW) and it's working perfectly. So no hal policy should be involved in this? I don't want to look insistent but I'd rather fix it now this way (should hal be an option in that case) if that could avoid us surprises in the future.
Offline
Thanks skottish, that's exactly what I did (and had the same issue with xorg.conf BTW) and it's working perfectly. So no hal policy should be involved in this? I don't want to look insistent but I'd rather fix it now this way (should hal be an option in that case) if that could avoid us surprises in the future.
That's a great question that I don't have an answer for. Hopefully someone more knowledgeable than I will jump in.
Offline
ok, I ran into this too, seems there has to be a better way to set this then in bashrc or similar.
Has to be a hal policy for this, what would be the point of centralized policies if they didn't always work?
Offline
For me the problem was not solved...Why is that?
Prepei na xtisw ena tzami gia ola ta ntervisia
Offline
Same issue, "xset r rate 200 25" helped but gave me an error:
Xlib: extension "XFree86-Misc" missing on display ":0.0".
I hope this is nothing serious? And it feels a bit hackish indeed..
Offline
In KDE you can configure it in the control center, under keyboard & mouse. The default is a too slow 600 or something like that, so you can change it to 200 to get the old behaviour.
Offline
I have noticed that too and I have tried xset and it didn't work complaining about a missing extension I think (this on my Arch64 fully up to date) (now I'm still using xorg-server 1.5 in my arch32 and can't confirm that because all works well).
The other solution I have seen was to use kbdrate, which half works, the repeat rate changes but in my case the delay stayed the same at 500ms (according to "xset q").
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Same issue, "xset r rate 200 25" helped but gave me an error:
Xlib: extension "XFree86-Misc" missing on display ":0.0".
I hope this is nothing serious? And it feels a bit hackish indeed..
Strange. My system isn't loading XFree86-Misc and I'm not seeing this message:
xdpyinfo | grep -i misc
XC-MISC
Offline
bangkok_manouel wrote:Thanks skottish, that's exactly what I did (and had the same issue with xorg.conf BTW) and it's working perfectly. So no hal policy should be involved in this? I don't want to look insistent but I'd rather fix it now this way (should hal be an option in that case) if that could avoid us surprises in the future.
That's a great question that I don't have an answer for. Hopefully someone more knowledgeable than I will jump in.
it's supposedly a bug introduced in evdev 2.2.0, a patch has already been submitted upstream but has not made it back down through official channels yet.
concluding from this thread: http://www.spinics.net/lists/xorg/msg43936.html
ᶘ ᵒᴥᵒᶅ
Offline
it's supposedly a bug introduced in evdev 2.2.0, a patch has already been submitted upstream but has not made it back down through official channels yet.
concluding from this thread: http://www.spinics.net/lists/xorg/msg43936.html
Interesting. I found a site that said that it's fixed in evdev 2.2.1, which I'm running. I removed the line out of .xinitrc and started X. It changed nothing. I guess we'll just have to wait.
Offline
Same issue, "xset r rate 200 25" helped but gave me an error:
Xlib: extension "XFree86-Misc" missing on display ":0.0".
I hope this is nothing serious? And it feels a bit hackish indeed..
I get that error too on this command and when trying to use "alock" screen locker.
Offline
Ramses de Norre wrote:Same issue, "xset r rate 200 25" helped but gave me an error:
Xlib: extension "XFree86-Misc" missing on display ":0.0".
I hope this is nothing serious? And it feels a bit hackish indeed..
I get that error too on this command and when trying to use "alock" screen locker.
I get this error as well.
Xlib: extension "XFree86-Misc" missing on display ":0.0".
Is it caused by using 'xset r rate 200 40 &' in my .xinitrc ?
Offline
Offline
Pages: 1