On Fri, Nov 21, 2025 at 4:34 AM steph01 <[email protected]> wrote: > > Hi Nick, > just checking in about the issue below — not sure if you had the chance to > look into it yet. > > I kept digging and found a couple more details that might help: > > It’s not actually sending Shift, but rather turning CTRL + c into CTRL + C > (uppercase). I assume Guacamole is internally converting that into a > Shift-modified combo. > > The issue always starts if the RDP session is opened while Caps Lock is > already ON on the client. > > Toggling Caps Lock inside the RDP session doesn’t fix anything. > > But if I switch to another browser tab, toggle Caps Lock there, and then come > back to the Guacamole tab, everything magically starts working again. So > something about the browser tab focus seems to force a correct state sync. > > Do you have any updates on this or any insight from your side? > Also — before I start experimenting randomly — do you know of any possible > workaround I could try client-side or server-side to force Guacamole to > resync the lock-key state on session start? >
No, I have not had a chance to look at this - it sounds like maybe the issue you referenced either never got fully fixed, or there was a regression somewhere along the way that has re-introduced that issue. If I get a chance I'll try to reproduce and maybe see if it was really fixed in the 1.2.0 release and where along the way it got broken. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
