Further to the bug, here's the evtest output: > Input driver version is 1.0.1 > Input device ID: bus 0x3 vendor 0x24ae product 0x2010 version 0x110 > Input device name: "RAPOO Rapoo 2.4G Wireless Device" > Supported events: > Event type 0 (EV_SYN) > Event type 1 (EV_KEY) > Event code 272 (BTN_LEFT) > Event code 273 (BTN_RIGHT) > Event code 274 (BTN_MIDDLE) > Event code 275 (BTN_SIDE) > Event code 276 (BTN_EXTRA) > Event type 2 (EV_REL) > Event code 0 (REL_X) > Event code 1 (REL_Y) > Event code 8 (REL_WHEEL) > Event code 11 (REL_WHEEL_HI_RES) > Event type 4 (EV_MSC) > Event code 4 (MSC_SCAN) > Properties: > Testing ... (interrupt to exit) >
>From what I see, the driver is correctly processing the left and mid button: Event: time 1692563194.319720, -------------- SYN_REPORT ------------ Event: time 1692563194.407719, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001 Event: time 1692563194.407719, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1692563194.407719, -------------- SYN_REPORT ------------ Event: time 1692563199.591686, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003 Event: time 1692563199.591686, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1 ...but unfortunately the driver remains dead silent of the right click. I guess it's the kernel input driver then... Brgds Mike
