Open MarcelWaldvogel opened 11 months ago
Experimentally, I lowered the upper key limit from KEY_MACRO1
(0x290) to KEY_COMPOSE
(127).
Now, the E
is received by applications.
Judging from the following code/comment, may I presume that you ran into a similar problem earlier?
From the above-mentioned Debian bug discussion, it is my understanding that a kernel fix is required to really fix the problem (increase the buffer to handle these generic virtual keyboards).
Proposal:
for
loop to something smaller than KEY_MACRO1
(KEY_SELECTIVE_SCREENSHOT
works for my setup and is not as radical a step as KEY_COMPOSE
, which was just to see whether the number of supported keys was the culprit).ioctl()
, but at a later stage.)KEY_CNT
, for broken ones, keep them at the value below KEY_MACRO1
.udev
-related processing was able to continue.)Experimentally, I lowered the upper key limit from
KEY_MACRO1
(0x290) toKEY_COMPOSE
(127).Now, the
E
is received by applications.Judging from the following code/comment, may I presume that you ran into a similar problem earlier?
Yes indeed there was an issue, I will have time to look into it again next week.
Thank you for the detailed information
Description Creating a mapped action to a keyboard event does not result in that keyboard event being accepted by an application.
To Reproduce
Expected behavior The application does respond to the key.
Desktop/Linux Environment (please complete the following information):
Linux Distribution and Version: Debian Bookworm
Desktop/Window Manager and Version: GNOME 43.6 (Wayland)
Did you built Projecteur yourself?: Both y+n (Debian Bookworm standard and my powerpointer branch (PR #215) \ (If yes: Please run cmake for existing build directories, to ensure the generated version info is up to date)
What is the output of
projecteur -f
?:The hash is this one
What is the output of
projecteur -d
?:Found 1 supported devices. (1 readable, 1 writable)
+++ name: 'Kensington PowerPointer' userName: 'Kensington PowerPointer' vendorId: 1ea7 productId: 0002 phys: usb-0000:03:00.4-2 busType: BusType::Usb devices: /dev/input/event23, /dev/input/event27, /dev/input/event25, /dev/input/event26, /dev/input/event24 readable: true writable: true
evtest
on the uinput device (Projecteur_virtual_keyboard
for the current state,Projecteur_input_device
for the Bookworm version from the v0.9.2 tag) shows the events being sent (the action isE
):However, nobody seems to receive it.
dmesg
shows the following:This seems related to this bug, where the Xen virtual keyboard is also adding all possible keybits, resulting in an overly long MODALIAS and therefore exhausting the kernel buffer.