Bug 204347

Summary:	A4Tech mouse scroll stopped working since 5.1.17
Product:	Drivers	Reporter:	Ivan Kalvachev (ikalvachev)
Component:	Input Devices	Assignee:	drivers_input-devices
Status:	RESOLVED CODE_FIX
Severity:	blocking	CC:	code, dithpri, k-kern-bugzilla, uncaster2
Priority:	P1
Hardware:	All
OS:	Linux
See Also:	https://bugzilla.kernel.org/show_bug.cgi?id=204179 https://bugzilla.kernel.org/show_bug.cgi?id=203369
Kernel Version:	5.1.17	Subsystem:
Regression:	Yes	Bisected commit-id:

Description Ivan Kalvachev 2019-07-28 14:20:44 UTC

https://bugzilla.kernel.org/show_bug.cgi?id=203369 "A4Tech mouse: horizontal scrolling is recognized as vertical since kernel 5.0" is fixing a regression.

Unfortunately the fix itself causes another regression, that prevents *some* a4tech mice from using their vertical scroll.

There is already fix for that here:
https://www.spinics.net/lists/linux-input/msg61859.html

The fix works for me and a number of other people who have similar issue.
However the fix doesn't seem to be merged or pushed upstream and has been forgotten and ignored for almost a month.
The regression is still present in 5.2 and 5.3 branches.

Please apply the fix.

Comment 1 LukasH 2019-07-31 08:14:17 UTC

I can confirm that patch is not implanted into 5.1.20 or 5.1.21 [EOL] kernels and thus this (small, but annoying) bug with A4Tech mouse is still present. I observed freshly new 5.2.5 kernel changelog, but it looks like this patch isn't included here as well.

Please apply the fix, thanks!

Comment 2 Konstantin 2019-08-01 08:10:25 UTC

A4Tech OP-200Q [09da:000a]
Mouse wheel not working in all kernels from 5.2-rc7 to 5.2.5
Didn't try the patch yet.

Would be nice to see it fiexd, thank you!

Comment 3 LukasH 2019-08-04 08:57:43 UTC

New kernel 5.2.6 is freshly on the scene. I'm reading the changelog and it looks like nothing is changed with this issue :-(

Comment 4 Ivan Kalvachev 2019-08-31 16:03:13 UTC

The fix has been merged in linux-5.3-rc4 , so it would be available in 5.3.0 release.
It also has been backported to linux-5.2.11.

I don't think they would be releasing any more revisions of linux-5.1.x ,
so I consider the bug fixed.