You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "andrea lattanzi (Jira)" <ji...@apache.org> on 2020/04/21 12:07:00 UTC
[jira] [Comment Edited] (GUACAMOLE-1037) Caps Lock doesn't work via
RDP (1.2 guacd)
[ https://issues.apache.org/jira/browse/GUACAMOLE-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088454#comment-17088454 ]
andrea lattanzi edited comment on GUACAMOLE-1037 at 4/21/20, 12:06 PM:
-----------------------------------------------------------------------
Hi Weston!
to answer your question:
"Just the client via Chromium" you are wondering right, my local, client side, keyboard layout is IT.
about the remote desktop site, the configuration is:
Windows 7 Pro, about RDP version is hard to say, I opened Chromium with [https://unixpapa.com/js/testkey.html], the remote computer is a VM doesn't have a real keyboard but the localization is IT, since incubating version, I'm forcing any Guacamole RDP to US Keyboard layout because it is the only way to make the keyboard layout match.
I also tried the same test with this remote, with the same results:
Windows 10 Pro VM, RDP 1903 "patched", I opened Chromium with [https://unixpapa.com/js/testkey.html], the remote computer is a VM doesn't have a real keyboard but the localization is IT, since incubating version, I'm forcing any Guacamole RDP to US Keyboard layout because it is the only way to make the keyboard layout match.
"client via Chromium, guacamole 0.9.14 RDP" = guacamole client and guacd 0.9.14
(bug) is a way to mark a test session where the caps bug is present.
About "client via Chromium, guacamole 1.1, guacd 1.2, RDP (bug)" I was forced to move guacd 1.2 to follow mitigations suggested for bug 1008.
Now I'm very busy to support a lot of people during the lockdown, I will try a guacamole-client and guacd 1.2 VM during the next weekend.
Weston, if you know about a 1.2 setup where the caps works, please tell me, I will try to reproduce it.
Do you know If there are DB structure difference between 1.0 and 1.1.
Thanks!
was (Author: scintillarsls):
Hi Weston!
to answer your question:
"Just the client via Chromium" you are wondering right, my local, client side, keyboard layout is IT.
about the remote desktop site, the configuration is:
Windows 7 Pro, about RDP version is hard to say, I opened Chromium with https://unixpapa.com/js/testkey.html, the remote computer is a VM doesn't have a real keyboard but the localization is IT, since incubating version, I'm forcing any Guacamole RDP to US Keyboard layout because it is the only way to make the keyboard layout match.
I also tried the same test with this remote, with the same results:
Windows 10 Pro VM, RDP 1903 "patched", I opened Chromium with https://unixpapa.com/js/testkey.html, the remote computer is a VM doesn't have a real keyboard but the localization is IT, since incubating version, I'm forcing any Guacamole RDP to US Keyboard layout because it is the only way to make the keyboard layout match.
"client via Chromium, guacamole 0.9.14 RDP" = guacamole client and guacd 0.9.14
(bug) is a way to mark a test session where the caps bug is present.
About "client via Chromium, guacamole 1.1, guacd 1.2, RDP (bug)" I was forced to move guacd 1.2 to follow mitigations suggested for bug 3008.
Now I'm very busy to support a lot of people during the lockdown, I will try a guacamole-client and guacd 1.2 VM during the next weekend.
Weston, if you know about a 1.2 setup where the caps works, please tell me, I will try to reproduce it.
Do you know If there are DB structure difference between 1.0 and 1.1.
Thanks!
> Caps Lock doesn't work via RDP (1.2 guacd)
> ------------------------------------------
>
> Key: GUACAMOLE-1037
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1037
> Project: Guacamole
> Issue Type: Bug
> Components: guacd
> Affects Versions: 1.2.0
> Reporter: andrea lattanzi
> Priority: Minor
>
> Hello!
> I was pushed to use guacd 1.2 after facing 1.1 huge memory leaks bug.
> The users signalled me this bug that could be workaround by running OSK on the remote.
> To log key events I used this site:
> [https://unixpapa.com/js/testkey.html]
> Now I'm pasting the results in several conditions of the following test sequence:
> 1) "a" key low case
> 2) caps lock
> 3) "A" key
> 4) caps lock
> 5) "a" key
> The client OS is Ubuntu, but OS and browser/version combinations don't look to affect the bug.
>
> *Just the client via Chromium:*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=20 which=20 charCode=0
> keyup keyCode=20 which=20 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=65 (A) which=65 (A) charCode=65 (A)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=20 which=20 charCode=0
> keyup keyCode=20 which=20 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
>
> *client via Chromium, guacamole 0.9.14 RDP*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=255 which=255 charCode=0
> keyup keyCode=255 which=255 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=65 (A) which=65 (A) charCode=65 (A)
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=255 which=255 charCode=0
> keyup keyCode=255 which=255 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
>
> *client via Chromium, guacamole 1.1, guacd 1.2, RDP (bug)*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=20 which=20 charCode=0
> keyup keyCode=20 which=20 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=20 which=20 charCode=0
> keyup keyCode=20 which=20 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=16 which=16 charCode=0
>
> *client via Chromium, guacamole 1.0, RDP*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=0 which=0 charCode=0
> keyup keyCode=0 which=0 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=65 (A) which=65 (A) charCode=65 (A)
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=0 which=0 charCode=0
> keyup keyCode=0 which=0 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=16 which=16 charCode=0
>
> *client via Chromium, guacamole 1.1, guacd 1.2, VNC*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=16 which=16 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=65 (A) which=65 (A) charCode=65 (A)
> textInput data=A
> Akeyup keyCode=16 which=16 charCode=0
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=65 (A) which=65 (A) charCode=0
>
> *client via Firefox, guacamole 0.9.14 RDP*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=255 which=255 charCode=0
> keyup keyCode=255 which=255 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=65 (A) which=65 (A) charCode=65 (A)
> textInput data=A
> Akeyup keyCode=16 which=16 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=255 which=255 charCode=0
> keyup keyCode=255 which=255 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=65 (A) which=65 (A) charCode=0
>
> *client via Firefox, guacamole 1.1, guacd 1.2, RDP (bug)*
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=65 (A) which=65 (A) charCode=0
> keydown keyCode=20 which=20 charCode=0
> keyup keyCode=20 which=20 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=16 which=16 charCode=0
> keydown keyCode=16 which=16 charCode=0
> keyup keyCode=65 (A) which=65 (A) charCode=0
> keyup keyCode=16 which=16 charCode=0
> keydown keyCode=20 which=20 charCode=0
> keyup keyCode=20 which=20 charCode=0
> keydown keyCode=65 (A) which=65 (A) charCode=0
> keypress keyCode=97 (a) which=97 (a) charCode=97 (a)
> textInput data=a
> akeyup keyCode=65 (A) which=65 (A) charCode=0
>
> I hope this could help.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)