[Logitech MX Anywhere 2S] Mouse events not interpreted correctly

Bug #1932357 reported by gpothier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This is a very weird bug that started occurring since I updated to 21.04. I am not sure mutter is the correct package. I have a bluetooth mouse that works perfectly (I'll clarify below why I'm sure it works). Sometimes, seemingly at random, scrolling stops working correctly, but not always in all applications (eg. scroll starts failing in Firefox, but works fine in Terminal). When this happens, moving the mouse around over a window causes it to scroll randomly up and down, while moving the mouse wheel also works randomly (sometimes it scrolls in the correct direction, sometimes in the opposite direction, sometimes not at all).
This occurs only when I have my external monitor connected (dual, non mirrored displays). If I unplug the display, the problem disappears immediately. If I plug the display back in, that problem reappears immediately (if it was already occurring before). While the problem is "active", I can scroll without problem using the notebook's touchpad. It seems to affect only the mouse.
I've seen messages like this in the log, but it does not seem strongly correlated with the occurrence of the problem:
libinput error: event21 - MX Anywhere 2S Mouse: client bug: event processing lagging behind by 21ms, your system is too slow
Also, rebooting the computer fixes the issue for a few hours/days, until it appears again. Also, the problem sometimes "solves itself" after a few minutes, or it intermittenly appears every few minutes.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: mutter 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Thu Jun 17 13:58:15 2021
InstallationDate: Installed on 2018-12-14 (916 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: mutter
UpgradeStatus: Upgraded to hirsute on 2021-05-30 (17 days ago)

Revision history for this message
gpothier (gpothier) wrote :
gpothier (gpothier)
summary: - Mouse wheel not interpreted correctly when using external display
+ Mouse events not interpreted correctly when using external display
Revision history for this message
gpothier (gpothier) wrote : Re: Mouse events not interpreted correctly when using external display

Adding a few details:
- The problem occurs with both Wayland and Xorg
- On Xorg, unplugging the external display does not fix the issue

summary: - Mouse events not interpreted correctly when using external display
+ Mouse events not interpreted correctly
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Mouse events not interpreted correctly

It sounds like some events (or Bluetooth packets) are going missing. Please try a wired mouse, or try avoiding 2.4GHz wifi networks that may interfere with Bluetooth (use 5GHz instead).

affects: mutter (Ubuntu) → libinput (Ubuntu)
summary: - Mouse events not interpreted correctly
+ [Logitech MX Anywhere 2S] Mouse events not interpreted correctly
affects: libinput (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1932357

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
gpothier (gpothier) wrote :

Hi, this issue seems to have been fixed by some update, I haven't encountered the issue in quite a while now. I will close this.

Revision history for this message
gpothier (gpothier) wrote :

Closing as invalid as it seems it no longer happens.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.