[winswitch] capslock acting like shiftlock?

[Antoine Martin]

On 23/10/2020 11:44, Thomas Esposito via shifter-users wrote:
> If I had to guess, I'd say the the xpra client is translating the capslock
> to a shift before it ever gets to the server. Is that possible?
No, the client tries hard not not modify key events before sending them
to the server.

> If so, how
> can I verify that this is happening and how would I fix it?
Run the server and client with "-d keyboard" to get details on events
and how they are processed.
(just be aware that this is hard to interpret as it is very verbose)

"Shift" and "Caps_Lock" are treated interchangeably by the key mapping
code for non-native keymaps. (non-X11 clients for seamless servers)

To fix it, please file a ticket as per:
https://xpra.org/trac/wiki/Keyboard#ReportingBugs

Cheers,
Antoine



> 
> On Fri, Oct 23, 2020, 12:08 AM Thomas Esposito <tmesposito00 at gmail.com>
> wrote:
> 
>> We finally upgraded from Centos 6.6 to 7.6 at work (it will be YEARS
>> before we see 8.x) and I took the opportunity to upgrade xpra to 3.x.
>>
>> So far, everything seems to be working well, except for some strange
>> keyboard behavior. My capslock key is acting as shiftlock (i.e. effects ALL
>> keys, not just letters). I DON'T get this behavior in a VNC session on the
>> same machine. I have compared xmodmap and setxkbmap settings between my vnc
>> and xpra sessions and haven't found any differences that seem like they
>> could explain this behavior.
>>
>> Any ideas?
>>
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> https://lists.devloop.org.uk/mailman/listinfo/shifter-users
>