[ 
https://issues.apache.org/jira/browse/GUACAMOLE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896530#comment-15896530
 ] 

Michael Jumper commented on GUACAMOLE-232:
------------------------------------------

Well ... you are not detecting stuck keys there - you are simply detecting 
Guacamole's built-in key repeat, which is not a bug. Guacamole will 
automatically repeat the keypress while the key is held down if the key is for 
a printable character. The issue is not that the key is repeating, but that the 
key release is somehow missed. From what you've described so far, Guacamole 
must somehow either (1) not receive a corresponding keyup event for the 
released key or (2) not recognize the received keyup as matching a pressed key.

Please try pressing the problematic key here:

http://guacamole.incubator.apache.org/pub/tests/key-event-test.html

and let us know what output is logged. The above is a generic JavaScript key 
event tester which logs the details of received key events. It should, 
hopefully, reveal why these keys are not properly handled for iPad+bluetooth.

> Stuck keys iPad/Bluetooth keyboard (Return/Backspace/Space)
> -----------------------------------------------------------
>
>                 Key: GUACAMOLE-232
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-232
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-client
>    Affects Versions: 0.9.10-incubating, 0.9.11-incubating
>            Reporter: devrandom
>         Attachments: guac_stuck.png
>
>
> I have the same issues as described in:
> https://glyptodon.org/jira/browse/GUAC-661
> Which theoretically was solved in 0.9.7.
> After some typing using iPad with connected bluetooth keyboard, the following 
> Keys may get stuck.
> * return
> * space
> * backspace
> Attached you'll find an example using xev on linux.
> Guacamole produces keyup and keydown events in a loop.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to