xpra icon
Bug tracker and wiki

Opened 5 weeks ago

Closed 4 weeks ago

Last modified 4 weeks ago

#2039 closed enhancement (wontfix)

Dell "Second Mouse" keys not recognized

Reported by: stdedos Owned by: stdedos
Priority: minor Milestone: 2.5
Component: client Version: 2.4.x
Keywords: Cc:

Description (last modified by Antoine Martin)

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.


Attachments (3)

csm_DSC04157_bedf23efc8.jpg (486.8 KB) - added by stdedos 5 weeks ago.
xpra-shell-client-keyboard.log (285.2 KB) - added by stdedos 4 weeks ago.
2018-11-17_16-42-46.mp4 (3.1 MB) - added by stdedos 4 weeks ago.

Change History (9)

Changed 5 weeks ago by stdedos

Attachment: csm_DSC04157_bedf23efc8.jpg added

comment:1 Changed 5 weeks ago by 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

Last edited 5 weeks ago by Antoine Martin (previous) (diff)

comment:2 Changed 5 weeks ago by 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
Last edited 5 weeks ago by Antoine Martin (previous) (diff)

comment:3 Changed 5 weeks ago by Antoine Martin

Description: modified (diff)
Owner: changed from Antoine Martin to stdedos
Type: defectenhancement

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.

Changed 4 weeks ago by stdedos

comment:4 Changed 4 weeks ago by Antoine Martin

Resolution: wontfix
Status: newclosed

.. 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.

Changed 4 weeks ago by stdedos

Attachment: 2018-11-17_16-42-46.mp4 added

comment:5 Changed 4 weeks ago by 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?

comment:6 Changed 4 weeks ago by 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.

Last edited 4 weeks ago by Antoine Martin (previous) (diff)
Note: See TracTickets for help on using tickets.