Xpra: Ticket #2039: Dell "Second Mouse" keys not recognized

I have a Dell Latitude E6430. The keys below the spacebar (not the touchbar ones), produce (from left to right, one keypress each)

unknown string message: 0xc118L / 0x6 / 0x1
unknown string message: 0xc118L / 0x7 / 0x0
unknown string message: 0xc118L / 0xa / 0x1
unknown string message: 0xc118L / 0xb / 0x0
unknown string message: 0xc118L / 0x8 / 0x1
unknown string message: 0xc118L / 0x9 / 0x0

They do not show up on the utilies, because they are considered mouse events.

Wed, 14 Nov 2018 23:49:40 GMT - stdedos: attachment set

attachment set to csm_DSC04157_bedf23efc8.jpg

Wed, 14 Nov 2018 23:52:51 GMT - stdedos:

And:

unknown string message: 0xc118L / 0x1 / 0x1
unknown string message: 0xc118L / 0x2 / 0x0
unknown string message: 0xc118L / 0x3 / 0x1
unknown string message: 0xc118L / 0x4 / 0x0

are the left/right mouse keys from the touchpad

Thu, 15 Nov 2018 00:09:45 GMT - stdedos:

I have some other copied text, that has the same 0x1 0x1, 0x2 0x0 sequences; but different leading number: 0xc098L

unknown string message: 0xc098L / 0x1 / 0x1
unknown string message: 0xc098L / 0x2 / 0x0
unknown string message: 0xc098L / 0x1 / 0x1
unknown string message: 0xc098L / 0x2 / 0x0
unknown string message: 0xc098L / 0x1 / 0x1
unknown string message: 0xc098L / 0x2 / 0x0
unknown string message: 0xc098L / 0x1 / 0x1
unknown string message: 0xc098L / 0x2 / 0x0

Thu, 15 Nov 2018 14:56:05 GMT - Antoine Martin: owner, type, description changed

owner changed from Antoine Martin to stdedos
type changed from defect to enhancement
description modified (diff)

Those event codes are undefined. It could just be that we already get mouse or keyboard events for those keys, in which case we just need to make sure they are mapped appropriately to a server side key - if at all possible.

Try attaching the client's -d keyboard,mouse log output of just when one of those keys is pressed.

Thu, 15 Nov 2018 22:34:49 GMT - stdedos: attachment set

attachment set to xpra-shell-client-keyboard.log

Fri, 16 Nov 2018 03:18:54 GMT - Antoine Martin: status changed; resolution set

status changed from new to closed
resolution set to wontfix

.. of just when one of those keys is pressed.

(that's the full log..)

But even then, I don't see any PRESS events (either BUTTON from _button_action or KEY from parse_key_event) that aren't known already so we can't support those buttons.

And without any definitions for those event codes, we can't silence them either.

Sorry but this hardware cannot be supported if we don't get events for it.

Sat, 17 Nov 2018 15:26:30 GMT - stdedos: attachment set

attachment set to 2018-11-17_16-42-46.mp4

Sat, 17 Nov 2018 15:28:31 GMT - stdedos:

I noticed this (video) on a normal "C:\Program Files\Xpra\xpra_cmd" start ssh://user@ip/ --webcam=no --speaker=off --microphone=off --opengl=no --start=gnome-terminal --start-new-commands=yes session.

I used only the touchpad and the "other" touchpad. Is there a reason that mouse clicks outside of the xpra window are getting tracked?

Sun, 18 Nov 2018 04:29:43 GMT - Antoine Martin:

Is there a reason that mouse clicks outside of the xpra window are getting tracked?

Microsoft windows is sending those events, you should ask Microsoft - or it could also be the authors of that touchpad driver and its associated tools.

Fri, 27 Dec 2019 10:48:47 GMT - Antoine Martin:

Duplicate ticket: #2530.

Sat, 23 Jan 2021 05:40:31 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2039