Upgrading 18.04 to 20.04: Issues with Logitech Mouse Scroll Button

[Patrick Gillespie]

I upgraded Kubuntu 18.04 to 20.04 Beta. The bug that I'm experiencing causes the logitech scroll button to function at a fraction of its normal speed, making it necessary to repeatedly scroll in order to accomplish what normally might be done with a single revolution.

WORKAROUND
1. Unplug the USB plug and plug back in.
2. Revert to an older Kernel ---> 4.18.5-041805-generic.

Not that it's directly relevant to this bug, but I've solved two other issues by reverting to the older kernel:

https://bugs.launchpad.net/ubuntu/+bug/1871408
https://bugs.launchpad.net/ubuntu/+bug/1871411

Seems that the latest Kernel doesn't like my Thinkpad or accessories.

SOFTWARE/OS VERSIONS

System: Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: KDE Plasma 5.18.3
           Distro: Ubuntu 20.04 LTS (Focal Fossa)
Machine: Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s serial: <superuser/root required>
           Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: <superuser/root required> UEFI: LENOVO v: N1WET31W (1.10 )
           date: 04/17/2017
Battery: ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%)
           ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%)
CPU: Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT MCP L2 cache: 3072 KiB
           Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 830 3: 809 4: 822
Graphics: Device-1: Intel HD Graphics 620 driver: i915 v: kernel
           Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.2
Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.4.0-21-generic
Network: Device-1: Intel Ethernet I219-LM driver: e1000e
           IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi
           IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e
Drives: Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%)
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 476.94 GiB
Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: /dev/nvme0n1p2
           ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4
Sensors: System Temperatures: cpu: 36.5 C mobo: N/A
           Fan Speeds (RPM): cpu: 0
Info: Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB (33.5%) Shell: bash inxi: 3.0.38

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1871415/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1871415

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[jfowlie (jfowlie)]

Turning the mouse off and on again is also a temporary workaround. The problem does recur, though.

[Patrick Gillespie (vermontpoet)]

Sorry, yes, Turning the mouse off and on also alleviates the problem, though the problem does recur.

I read up on apport (Ubuntu Wiki) and it doesn't seem to be the right tool for the current bug, mainly because the bug doesn't seem to meet any of these conditions: "segmentation violation, bus error, floating point exception, etc.)..."

[Patrick Gillespie (vermontpoet)]

Also, in accordance with the automated instructions, I'm changing the status to 'Confirmed'.

[jfowlie (jfowlie)]

Logging out and back in re-creates the issue, and the mouse scroll wheel requires a power cycle or dongle reset to begin working properly.

[jfowlie (jfowlie)]

Here's what discussion on RedHat's bugzilla says about the issue in the thread https://bugzilla.redhat.com/show_bug.cgi?id=1701322

I've excerpted a few remarks:
---------------------------------------------

This is likely a kernel bug.

Since kernel v5.0, we enabled the high-resolution scrolling capability of the mouse. This will allow libinput and gnome to provide smooth scrolling.
However, the setting is not persistent. Whenever the mouse goes to sleep to save battery, the setting is reverted.
The kernel is supposed to resend the setting when the mouse comes back, but it seems it doesn't from time to time.

The question is now whether the kernel doesn't see the "connect" event from the mouse or if the kernel fails at sending the parameter to the mouse.

----------------------------------------------------

Same issue here with a Logitech Performance MX mouse. A workaround seems to be to use Solaar to turn on "Smooth Scrolling", which restores the correct scrolling operation.

----------------------------------------------------

Turns out that solaar can try to guess the device you want so here is my updated command wrapped by a function I stuck in my .bashrc and that I can either execute manually or, is one so desires, could be executed in the background at login.

function hack_bz_1701322() {
    _sleep_interval=25
    if [ $# -gt 0 ]; then
        _DEVICE="$1"
    else
        _DEVICE="mouse"
    fi
    while true; do
        if ! solaar config "$_DEVICE" | grep -qE '^\s*smooth-scroll\s*=\s*True\s*$'; then
                solaar config "$_DEVICE" smooth-scroll True
        fi
        sleep "$_sleep_interval"
    done
}

However, the underlying issue that is causing this needs to be properly diagnosed and fixed. At the moment, this issue has added the unintended feature of the mouse randomly turning into a flying projectile.

[jfowlie (jfowlie)]

And in the Arch forums they have this:
https://bbs.archlinux.org/viewtopic.php?id=245501
----------------------------------------------

I applied patch from here - https://patchwork.kernel.org/patch/10913251/ - to kernel 5.1-rc6 and recompiled with unchanged .config.

this patch addresses hid-core.c and hid-input.c driver modules

output of sudo libinput debug-events shows POINTER_AXIS events for every wheel click, so mouse scroll is normal for these mice that I have tested:

"Microsoft Standard Wireless Desktop mouse" - wireless
"Wheel Mouse Optical 1.1A USB and PS/2 Compatible" - USB
"OPTICAL MOUSE" - ?? generic brand - USB
"Microsoft Wireless Optical Mouse 2000" - wireless

The solution appears to be coming in future kernel 5.x release so I have marked this as [SOLVED]