Ok, unfortunately that's different from my experience; there may not be
a lot more I can help with.
However, it may be useful for others if you could let us know what
happens if you use Guacamole's on-screen keyboard?
On 21/08/2019 4:04 p.m., Manoj Patil wrote:
thanks for response .
I am done all these setting but Cap lock not work in any condition.
please suggest any other solution.
On 20-Aug-2019, at 4:37 PM, ivanmarcus <[email protected]
<mailto:[email protected]>> wrote:
In Guacamole itself there's a setting for keyboard layout.
This is located, from the web gui, in settings -> connections ->
[connection name] -> basic settings -> keyboard layout
Try changing this option to Unicode
On 20/08/2019 8:46 p.m., Manoj Patil wrote:
i am setting keyboard type -unicode on firefox version 68 but still
cap locks not work .
On 20-Aug-2019, at 5:02 AM, ivanmarcus <[email protected]
<mailto:[email protected]>> wrote:
Manoj,
Have you tried setting the keyboard layout to 'unicode' in Guacamole?
On 19/08/2019 11:09 p.m., Manoj Patil wrote:
Dear thank
We used RDP protocol?? and xrdp version 0.9.6 with x11rdp session .
On Mon, 19 Aug 2019, 16:17 ivanmarcus <[email protected]
<mailto:[email protected]> wrote:
Thanks, that's useful as I wasn't aware you were using x11rdp.
I've not used it before but have just installed xrdp on
another Mint 19 machine and attempted a connect via Guacamole.
Unfortunately I get the login screen but when I enter the
requisite detail it goes to a blank screen and I can't do
anything further. Having had a look around it seems this isn't
uncommon with xrdp on debian based systems but none of the
fixes I've seen to date have been able to sort it out.
Thus I'm sorry I can't test that further right now (it''s
getting late), however I did try the caps lock at the login
prompt. What I found may be useful for further fault-finding(?):
Guacamole is 1.0.0 on Ubuntu server 16.04 server VM, keyboard
for specified RDP connection is set to nothing, or US, or UK,
target is xrdp 0.9.5 on Linux Mint 19.0, client is FF 68.0.1
on Mimt 19.2:
At login the caps lock key doesn't work, shift will happily
give caps
The Guacamole on-screen keyboard caps lock works fine.
If I switch back to the remote keyboard the state of the caps
lock from the Guacamole keyboard remains (ie. all typing is in
caps) and caps lock still doesn't do anything, however shift
will return the typing to lower case while it's pressed.
If I set the Guacamole RDP connection to a Unicode keyboard
the caps lock key *will* work as expected and I can select
caps on / caps off with seemingly good results.
With the same Guacamole/Ubuntu VM and same client caps lock
works fine to a Win7 target with nothing specified for the
keyboard.
WIth the same Guacamole/Ubuntu VM and same client caps lock
does NOT work to the Mint 19 target machine with x11VNC
running on that machine (and appropriately set up in Guacamole
- with no keyboard set).
Bear in mind I can't check within a xrdp session because I
can't get beyond the login prompt but for the moment you might
want to try changing your keyboard type to Unicode and test
that out, then let us know.
This sort of information may be useful for those who know more
about these things, it could give them a pointer as to what
the issue is and if there is an easy way to address it.
At this stage, and with my single user case and limited
knowledge, it suggests to me the issue is replicable between
Guacamole and a Linux target, initially it doesn't seem to be
client related, and may not be anything to do with the
protocol in use (ie. VNC or RDP).??
On 19/08/2019 9:06 p.m., Manoj Patil wrote:
Ok I know that without any log or details informatiom you can
not give solution but someone have occurred this issues and
someone gives the solution that's I am asking solution.
I am tested through windows mstsc (remote desktop servicce)
to linux which have x11rdp installed ( centos7) that time cap
locks work fine.
But when I am take remote from client side windows version
(windows 7, Windows 8, windows 10) with version firefox 68
and crome 76 through guacamole 1.0 (keyboard type _ en us
qwerty) that time cap lock not work.
If you want additional information please mail me
On Mon, 19 Aug 2019, 02:37 ivanmarcus <[email protected]
<mailto:[email protected]> wrote:
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
