Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
Vincent Lefevre <email@example.com> writes:
> On 2012-07-20 08:58:57 +0200, Vincent Lefevre wrote:
>> So, it would seem that some part of the system would enable SlowKeys
>> in my back for one of the keyboards (I recall that when this happens
>> while I'm using the USB keyboard, only the USB keyboard is affected,
>> not the laptop keyboard).
>> If there a way to know whether SlowKeys is enabled, for each available
>> keyboard? (Note: I'm not using GNOME, and even GNOME would be useless
>> because according to what I see on this page, it cannot differentiate
> Additional information:
> * SlowKeys can be turned on and off by pressing the Shift key for
> at least 10 seconds:
> I've tried and I confirm that this "works". When several keyboards
> are attached, only the keyboard for which the Shift key is pressed
> is affected (I suppose that this is expected).
Thanks a lot for posting this. I've now hit the bug several times
myself over the last few days, and without having read this thread first
I would never have known how to get out ot it. And that would have been
really annoying given that this typically happens in the middle of some
heavy editing session. I would have hated to have to throw away the work
and reboot to get the system working again, and I don't think I ever
would have figured out the shift key trick.
BTW, is it only me, or do you have to hold down the key significantly
longer to turn the "feature" off than to turn it on? It certainly feels
> * When the bug occurred in my case, I don't think I've pressed Shift
> for 10 seconds (well, when I do this, this is in combination with
> another key like PageUp / PageDown, but in this case, SlowKeys
> switching isn't triggered), at least in most of the cases.
In my case it seems to happen most often when I do cut and paste,
combining mouse selection with shift + del. I often end up holding down
the shift key while selecting and bam...
IMNSHO, the hotkey choice is too generic to be acceptable at
all. Holding down any single key to silently enable a feature like this
is not going to do. I find it somwhat surprising in light of the
Why couldn't they have used *both* shift keys as a trigger? That would
have eliminated all false positives with no drawbacks AFAICS.
Anyway, please disable this extremely annoying feature until some safer
trigger can be found.