xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 10 years ago

Closed 10 years ago

Last modified 12 months ago

#142 closed defect (invalid)

On networks with high latency, typing fast characters are entered twice

Reported by: sergio Owned by: Antoine Martin
Priority: minor Milestone: 0.3
Component: core Version: 0.3.x
Keywords: Cc:


On a network with a good throughput, but a high latency (connection via a mobile phone), I am experiencing a strange phenomenon.

When typing on the keyboard, if I type slowly everything is fine.
However, if I type fast, some keys get repeated. For instance, trying to type:

echo This is a test

I may get

eccho Thiis iis a teest

Change History (5)

comment:1 Changed 10 years ago by Antoine Martin

Status: newaccepted
man xpra | grep latency

Edited grep:

              Disables keyboard state synchronization. Normally the key
              presses and key release events are sent to the server as they
              occur so that the server can maintain a consistent keyboard
              state.  Using this option can prevent keys from repeating
              unexpectedly on  high latency links but it may also disrupt
              applications which access the keyboard directly (games, etc).

Let me know if that helps..

Last edited 10 years ago by Antoine Martin (previous) (diff)

comment:2 Changed 10 years ago by sergio

Thanks... I have evidently missed it...
I'll try as soon as have that kind of high latency access again.
Would be great if this could be self-tuning.

comment:3 Changed 10 years ago by Antoine Martin

OK, once tested - please close the bug if this works for you.

Self-tuning would be great.. but latency is hard to measure, and by definition it fluctuates, so this is going to be difficult. What we could do, which would help us to bring self-tuning eventually would be to at least provide a GUI option for it so it can be toggled at runtime without disconnecting: moved to #143

comment:4 Changed 10 years ago by Antoine Martin

Resolution: invalid
Status: acceptedclosed

not heard back, closing

comment:5 Changed 12 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/142

Note: See TracTickets for help on using tickets.