What I don't really understand in the whole threading vs. signals
discussion is why the kernel cannot buffer in a queue of some sort
those signals before processing them. They wouldn't be lost anymore
and the kernel could process them at its own pace.

2011/4/29 Marius Kotsbak <124...@bugs.launchpad.net>:
> Regarding the bug severity, I can only agree on that given that we have
> the workaround of disabling keyboard repeat in the X server settings.
> Without that, depending on the frequency it happens, it can make the PC
> almost unusable or at least too unpredictable to trust, i.e. you always
> risk, like when I am writing in this text field to loose all when I am
> correcting one typo if I don't react in time, close all tabs in the
> browser when typing ctrl-w (since this shortcut starts CPU load, the bug
> occurence actually increase at exactly that time, as with tab completion
> in terminal).
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/124406
>
> Title:
>  Keyboard keys get stuck and repeat
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/emacs/+bug/124406/+subscribe
>

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/124406

Title:
  Keyboard keys get stuck and repeat

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to