Win 4.0.x client shift+arrow, shift+enter doesn't work, shift+letter/symbol OK

[totaam]

Issue migrated from trac ticket # 2887

component: client | priority: minor | resolution: fixed | keywords: keyboard, shift

2020-09-29 15:50:57: schvab created the issue

---

Hello,
In all Windows 10 client v4.0.x Im observing strange behavior of shift key (server is ubuntu, always same version as client).
When using shift+arrow key to highlight text nothing happens, same for shift+enter (eg to get to new line in chat app) - in both cases the shift is ignored, only the arrow/enter key has effect.
When I enable caps-lock the highlighting works (same for enter key) as it is supposed to with shift.
For letters/symbols the shift works correctly as well as caps-lock does.
This defect doesnt happen when client is running on ubuntu.
This defect did not happen in v3.0.x.

[totaam]

2020-09-29 15:52:39: schvab uploaded file br.zip (82.5 KiB)

[totaam]

2020-09-29 16:31:55: antoine changed owner from antoine to schvab

[totaam]

2020-09-29 16:31:55: antoine commented

---

As per ReportingBugs, please be a lot more specific about what versions you have tested, the commands you used, etc.

This sounds like a duplicate of #2632

[totaam]

2020-09-30 10:25:59: schvab changed status from new to closed

[totaam]

2020-09-30 10:25:59: schvab set resolution to fixed

[totaam]

2020-09-30 10:25:59: schvab commented

---

The server is started as:

XPRA_CLIPBOARD_IMAGE_STAMP=0 PATH="/usr/lib/xorg:$PATH" xpra start :1 \
    --mdns=no --webcam=no --use-display=yes --opengl=no --tcp-auth=sys \
    --html=on --bind-tcp=127.0.0.1:14501

running on Ubuntu 18.04.5 LTS, version xpra v4.0.3-27082

The client is started as:

C:\"Program Files"\Xpra\xpra_cmd attach ssh://<user>@<host>/1 \
    --speaker=disabled --microphone=disabled \
    --encoding=vp8 --opengl=no --min-quality=88

running on Microsoft Windows [Version 10.0.18362.1082], version xpra v4.0.4-27557

Adding XPRA_XKB=0 to server start solved the problem.

[totaam]

2020-09-30 10:36:54: antoine commented

---

Adding XPRA_XKB=0 to server start solved the problem.
You should just update your system to 4.0.4 instead - that's very likely to fix the problem and more correctly too.