KDE

5931 readers

11 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 2 years ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

[Partial workaround!] KDE Accessibility, enable bounce keys with less than 100 ms? (github.com)

submitted 1 month ago* (last edited 1 month ago) by JackbyDev@programming.dev to c/kde@lemmy.kde.social

1 comments fedilink hide all child comments

My Keyboard has a chattering problem. On Windows I was able to run a program that would detect this and fix it. I believe I could use the built-in keyboard bounce accessibility feature to solve this, but the lowest setting it will allow me to use is 100 ms. When I type normally I will sometimes push a key that fast (e.g., hitting backspace a lot or in a video game). Is it possible to lower this settings to something like 10 ms? Maybe via the terminal?

Edit:

Potential workaround found. In ~/.config/kaccessrc manually change it to something like 10. Save and reboot. It didn't seem to take hold if I didn't reboot. Even typing this now I am seeing some problems, but I also hear the ding indicating it is working. Change BounceKeysRejectBeep to false to get rid of the ding. A comment on the bug mentioned 40 ms, so maybe that's a good sweetspot.

[Keyboard]
BounceKeys=true
BounceKeysDelay=10
BounceKeysRejectBeep=true

top 1 comments

sorted by: hot top controversial new old

[–] JackbyDev@programming.dev 2 points 1 month ago* (last edited 1 month ago)

Oh wow, I decided to look into reporting this as a bug (to at least raise the issue), but it is already reported.

The main reason I was looking into this is because I have a mechanical keyboard that's chattering like crazy and discovered there's a built-in feature to reject double-key presses.

I've edited the post with a workaround, but it would be nice if the menu itself let me type in values lower than 100.