[BRLTTY] Two problems with Pegasus display from Deininger

[Sebastian Humenda]

Hello,

Dave Mielke <dave at mielke.cc> wrote on Mo, Apr 05, 2010 at 11:07:28 -0400:
>>My speech is configured to speak very fast, hence I hear all keys I press (I
>>can't verify, but distinguish them). When this problem occures the speech
>>stops for felt milliseconds and then begins reporting the repeated keys
>>and the keys which I pressed afterwards. However, this is only how I think it
>>happens.
>This, also, is a helpful observation. I'm now beginning to think that your 
>system is either very busy or there's perhaps a process on your system which 
>sometimes claims the CPU for whatever reason for a long time. If brltty doesn't 
>get the CPU quickly enough then it's very possible that it processes the key's 
>release event some time after its press event. If this delay is long enough, 
>the virtual keyboard device which brltty echoes the key events back into may 
>well start to repeat.
[...]
>Please do a simple test to see if the problem occurs less often: Find out the 
>process identifier (pid) of brltty. You can do this with the command:
>   pgrep brltty
I'll test that and the suggestion with no speech next week and then report
further details.

>>>>For the other problem with the first routing key I started brltty and
>>>>clicked once on the first and then once on the second routing key. The
>>>>same I repeated in a text editor. I attach the file below.
>>So I guess it might be a hardware problem. thanks and sorry for the time wasted
>>on it.
>If you have brltty's alert tunes turned on, you should always hear a tune 
>whenever you press a routing key. Can you test to see whether you do or don't 
>hear the routing tune when you press the first routing key?
I hear a sound only when I press the routing key harder than usual. If I press
less hard, I get no sound and no cursor movement.

Greetings
Sebastian