CAPS Lock Key!!!

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

CAPS Lock Key!!!

Tushar Jain
Hi,

There are a few posts in the forum related to non-functioning of CAPS Lock key. Have tried a majority of options, but am still stuck. Below is the summary of what i have tried and the observations:

1. By default, when we connect to Windows 2016/10/7 machine from guacamole over rdp, CAPS Lock does not work. What ever is the state before opening the connection gets carried forward to the Windows machine and then it stops working.

2. We changed the keyboard layout to "Unicode" for the connections as recommended in previous posts. Post update, CAPS lock key starts working, but Ctrl key stops working

3. Though the CAPS lock does not work after opening the connection, but if we click on local machine outside guacamole browser instance and change the CAPS lock and then go back to guacamole rdp connection, the change gets reflected. But whenever CAPS lock key is on, Ctrl Key stops working within rdp connection. Whenever CAPS lock key is off Ctrl key works.
,
4. Have downloaded the latest source of guacamole client 1.0.0, build and redeployed, but the problem persists.

Environment
1. Local Machine: Windows 10 laptop
2. Guacamole server: Ubuntu 16.04.4 LTS (Xenial), libfreerdp-1.1.0; xrdp: 0.6
3. Remote Desktop Machine: Windows 2016/2012 server / Windows 10/7

Any help to resolve this is appreciated. May be i have missed out some options. It is such a big bummer in otherwise fantastic product!

Thanks,
Tushar Jain

Disclaimer: This message and any attachment may contain confidential, proprietary information and is intended only for the individual named. If you are not the original intended recipient and have erroneously received this message, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Hitachi MGRM Net E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Hitachi MGRM Net therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. Hitachi MGRM Net Ltd, C - 6/5, Safdarjung Development Area, New Delhi - 110016, India

'Please consider the environment before printing this e-mail'.
Reply | Threaded
Open this post in threaded view
|

Re: CAPS Lock Key!!!

vnick
On Wed, Nov 27, 2019 at 9:41 AM Tushar Jain <[hidden email]> wrote:
Hi,

There are a few posts in the forum related to non-functioning of CAPS Lock key. Have tried a majority of options, but am still stuck. Below is the summary of what i have tried and the observations:

1. By default, when we connect to Windows 2016/10/7 machine from guacamole over rdp, CAPS Lock does not work. What ever is the state before opening the connection gets carried forward to the Windows machine and then it stops working.

2. We changed the keyboard layout to "Unicode" for the connections as recommended in previous posts. Post update, CAPS lock key starts working, but Ctrl key stops working

3. Though the CAPS lock does not work after opening the connection, but if we click on local machine outside guacamole browser instance and change the CAPS lock and then go back to guacamole rdp connection, the change gets reflected. But whenever CAPS lock key is on, Ctrl Key stops working within rdp connection. Whenever CAPS lock key is off Ctrl key works.
,
4. Have downloaded the latest source of guacamole client 1.0.0, build and redeployed, but the problem persists.

Environment
1. Local Machine: Windows 10 laptop
2. Guacamole server: Ubuntu 16.04.4 LTS (Xenial), libfreerdp-1.1.0; xrdp: 0.6
3. Remote Desktop Machine: Windows 2016/2012 server / Windows 10/7

Any help to resolve this is appreciated. May be i have missed out some options. It is such a big bummer in otherwise fantastic product!


A few general thoughts, here...

First, Caps Lock is one of those keys that is going to be tricky to capture at the browser level.  If the O/S or browser intercept any of the keypresses that occur when Caps Lock is enabled, then it will be impossible to send that on to the remote display.  If those key presses are captured, then it may be possible to send it on; however, the current state also has to be detected so that you know whether caps lock is being turned on or off and send the proper/matching keypress into the remote session.  However, if the remote session happens to have the opposite state of the local session, you could end up simply toggling back-and-forth.  My point is not that it's impossible, just difficult, and there are likely to be bugs to be worked out along the way.

Speaking of bugs, there are two issues that seem like they may be applicable, here:

The first, 161, was fixed in 1.0.0, so you should have that fix in.  It also deals with Mac OS, which you do not appear to be using, so it is likely not the source of your issue, but may be worth looking at to get a sense for what was done to fix things in the past.  The second, 859, seems more likely to be related to at least one of the issues you are seeing, and it is fixed in the current git master code, not in 1.0.0 or even in the staging code for 1.1.0.  So, if you're up for a little more work, you might grab the latest git master code for Guacamole Client, download, compile, and deploy it, and see if your Caps Lock issues are different, same, resolved, or still present.

-Nick
Reply | Threaded
Open this post in threaded view
|

Re: CAPS Lock Key!!!

Tushar Jain
Hi Nick,

Thanks for these inputs. I took the client code from current git master, compiled and deployed it this time on a Ubuntu 18.04 server (instead of Ubuntu 16.04). Both CAPS Lock key and Ctrl Key are working like a charm!! You rock!!

Thanks again,
Tushar

On Fri, Nov 29, 2019 at 10:51 PM Nick Couchman <[hidden email]> wrote:
On Wed, Nov 27, 2019 at 9:41 AM Tushar Jain <[hidden email]> wrote:
Hi,

There are a few posts in the forum related to non-functioning of CAPS Lock key. Have tried a majority of options, but am still stuck. Below is the summary of what i have tried and the observations:

1. By default, when we connect to Windows 2016/10/7 machine from guacamole over rdp, CAPS Lock does not work. What ever is the state before opening the connection gets carried forward to the Windows machine and then it stops working.

2. We changed the keyboard layout to "Unicode" for the connections as recommended in previous posts. Post update, CAPS lock key starts working, but Ctrl key stops working

3. Though the CAPS lock does not work after opening the connection, but if we click on local machine outside guacamole browser instance and change the CAPS lock and then go back to guacamole rdp connection, the change gets reflected. But whenever CAPS lock key is on, Ctrl Key stops working within rdp connection. Whenever CAPS lock key is off Ctrl key works.
,
4. Have downloaded the latest source of guacamole client 1.0.0, build and redeployed, but the problem persists.

Environment
1. Local Machine: Windows 10 laptop
2. Guacamole server: Ubuntu 16.04.4 LTS (Xenial), libfreerdp-1.1.0; xrdp: 0.6
3. Remote Desktop Machine: Windows 2016/2012 server / Windows 10/7

Any help to resolve this is appreciated. May be i have missed out some options. It is such a big bummer in otherwise fantastic product!


A few general thoughts, here...

First, Caps Lock is one of those keys that is going to be tricky to capture at the browser level.  If the O/S or browser intercept any of the keypresses that occur when Caps Lock is enabled, then it will be impossible to send that on to the remote display.  If those key presses are captured, then it may be possible to send it on; however, the current state also has to be detected so that you know whether caps lock is being turned on or off and send the proper/matching keypress into the remote session.  However, if the remote session happens to have the opposite state of the local session, you could end up simply toggling back-and-forth.  My point is not that it's impossible, just difficult, and there are likely to be bugs to be worked out along the way.

Speaking of bugs, there are two issues that seem like they may be applicable, here:

The first, 161, was fixed in 1.0.0, so you should have that fix in.  It also deals with Mac OS, which you do not appear to be using, so it is likely not the source of your issue, but may be worth looking at to get a sense for what was done to fix things in the past.  The second, 859, seems more likely to be related to at least one of the issues you are seeing, and it is fixed in the current git master code, not in 1.0.0 or even in the staging code for 1.1.0.  So, if you're up for a little more work, you might grab the latest git master code for Guacamole Client, download, compile, and deploy it, and see if your Caps Lock issues are different, same, resolved, or still present.

-Nick

Disclaimer: This message and any attachment may contain confidential, proprietary information and is intended only for the individual named. If you are not the original intended recipient and have erroneously received this message, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Hitachi MGRM Net E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Hitachi MGRM Net therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. Hitachi MGRM Net Ltd, C - 6/5, Safdarjung Development Area, New Delhi - 110016, India

'Please consider the environment before printing this e-mail'.