Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libinput (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
https:/
---
### Expected behaviour
My "Contour Design RollerMouse Free 2" has a specific button for double click. This button should with one physical click result in double click (button press, button release, button press and button release).
This works as expected without issues in Ubuntu 16.04 LTS 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64
### Experienced behaviour
Only one mouse click is registered (button press and button release). Tested with "xev" and "xinput test"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 28 16:26:08 2018
InstallationDate: Installed on 2018-04-27 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in libinput (Ubuntu): | |
status: | Incomplete → Confirmed |
no longer affects: | gnome-shell (Ubuntu) |
I read up on https:/ /www.kernel. org/doc/ Documentation/ input/input. txt and tested with "evtest" for the RollerMouse and can see that the kernel emits proper events, as far as I understand.
### Single left click button
Event: time 1525013249.812780, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1525013249.812780, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1525013249.812780, -------------- SYN_REPORT ------------
Event: time 1525013249.936782, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1525013249.936782, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1525013249.936782, -------------- SYN_REPORT ------------
### Double click button
Event: time 1525013251.656770, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1525013251.656770, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1525013251.656770, -------------- SYN_REPORT ------------
Event: time 1525013251.660700, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1525013251.660700, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1525013251.660700, -------------- SYN_REPORT ------------
Event: time 1525013251.664778, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1525013251.664778, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1525013251.664778, -------------- SYN_REPORT ------------
Event: time 1525013251.668782, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1525013251.668782, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1525013251.668782, -------------- SYN_REPORT ------------
What is inbetween what the kernel emits to /dev/input/eventX and what is registered by "xev" and "xinput"?