Manoj,

Unfortunately this group can't always give solutions, especially when there is little information. It would assist greatly if you could look for solutions yourself, post what you've done to resolve the issue and what you've found, and perhaps include log detail where useful (or when asked). All of this will help to narrow down what the issue might be.

Following on I've had a look to see what 'msctc' is but I'm unable to find out.

However per my previous respone I've found that caps lock works for me with Firefox v68 on Mint 19 -> Guacamole 1.0.0 -> Win7. I've just downloaded Chromium to test it for you and I find that caps lock works ok there too.

Per Nick's earlier suggestion it's possible that something at your client end is failing to pass on the necessary information to Guacamole. To help find out where the issue lays he's made a suggestion about trying the Guacamole on-screen keyboard, did you try that? Also, have you tried a completely different client? Can you get someone else to log in and see what happens?


On 19/08/2019 5:10 a.m., Manoj Patil wrote:
Please give solution

On Sat, 17 Aug 2019, 22:49 Manoj Patil <[email protected] <mailto:[email protected]> wrote:

    Dear,

    when i am  connecting through msctc cap lock work well but when i
    am connecting through crome/firefox then cap lock not work . why?



    On 17-Aug-2019, at 11:45 AM, Manoj Patil <[email protected]
    <mailto:[email protected]>> wrote:

    Dear ,

    Cap lock work for some days but suddenly this not work .

    where is the i want to change and compiled again .
    please guide in details.



    On 16-Aug-2019, at 3:54 AM, Nick Couchman <[email protected]
    <mailto:[email protected]>> wrote:

    On Thu, Aug 15, 2019 at 3:28 PM ivanmarcus
    <[email protected]
    <mailto:[email protected]>> wrote:

        Manoj,

        There is some explanation in the link that Nick included,
        you will also see that Nick has merged the fix into the
        master code.

        In terms of your installation, no doubt someone will correct
        me if I'm wrong but I believe that if you (re)compiled
        Guacamole from source this fix would now be included and
        caps lock will work. However if you've installed from a
        binary it won't assist you until the next release.


    Yes, you're correct - the change has been merged into the master
    code, so the fix will only be available if you check out the git
    master branch and compile it.

    We don't distribute any binaries of the guacd code - the closest
    we come is the Docker images, which are still compiled from
    source, so one way or the other you'll probably be compiling
    this from source until we push new Docker images.

        I'm not sure of your exact issue but I expect you noted
        this: "it only impacts the key up and down events for the
        Caps Lock key, not Caps Lock's effect on sending uppercase
        [A-Z] characters"?

        I mention this because I'm presently typing this response
        via a 1.0.0 binary install of Guacamole to a Win7 VM and THE
        CAPS LOCK key works for capitalising what I type. FYI while
        I don't specifying it I am using a 'US keyboard'.



    It's also worth noting that the Caps Lock key may be intercepted
    by O/S, window manager, and/or browser before it actually hits
    Guacamole - this will vary platform-to-platform and
    browser-to-browser - so if you're just pressing the Caps Lock
    key expecting it to turn on in the RDP session, you may be
    expecting something that won't work on your own platform.  One
    way to begin to track this down is to enable Guacaomle's
    on-screen keyboard (through the menu) and toggle Caps Lock from
    that keyboard to see if it works within the RDP session.

    -Nick



Reply via email to