[winswitch] client failed to provide any keycodes (XPRA client win10 2.2-r17577 against XPRA server 2.2-0.20171206r17578.fc27)
Antoine Martin
antoine at nagafix.co.uk
Sun Dec 10 08:13:50 GMT 2017
On 10/12/17 01:31, WireRydr via shifter-users wrote:
> Hello all;
>
> I've posted this as a question to the mailing-list instead of as a
> bug-report because I cannot rule out the possibility of
> mis-configuration. However, given that this problem doesn't happen with
> an older client, I suspect it's a regression.
It is.
> Operating Environment
> ---------------------
> Host OS: Fedora 27 (x86_64)
> XPRA Server: 2.2-0.20171206r17578.fc27
> XPRA Client: Python/Gtk2 Microsoft Windows 10 aero client version
> 2.2-r17577 64-bit
>
> I've pasted two logging outputs below: 1) When I attempt to connect to
> a running XPRA server with a Win10 client 2.2-r17577, and 2) When I
> connect to the same XPRA server with a Win10 client 2.2-r17538.
>
> In the first attempt the resulting child xterm doesn't respond properly
> to keyboard input, and the server log includes an error and traceback.
> In the second attempt (same server but older client), the xterm responds
> properly and there's no server error/traceback.
>
> Any advice/guidance you can provide to assist with better
> troubleshooting this would be greatly appreciated. Thanks!
This bug has been fixed, for details see here:
http://xpra.org/trac/ticket/1665#comment:6
And you can find updated builds in the usual location:
https://xpra.org/beta/
Sorry for the inconvenience.
For future reference, keyboard debugging is documented here:
https://xpra.org/trac/wiki/Keyboard
But I have to say that your bug report is one of the best I have seen.
Cheers
Antoine
More information about the shifter-users
mailing list