Ubuntu
linux package

Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged

Bug #1875150 reported by Dominik
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The mouse is MX Anywhere 2, the keyboard is K750.

If the system is booted with the Logitech Unifying Receiver plugged in, the keyboard and mouse will keep losing connection. This is most visible after a short inactivity, i.e. I start typing and nothing appears on screen for a couple of seconds, or I start moving the mouse and the cursor takes a couple of seconds to start moving. This also happens while I'm using the input device, as I was typing this paragraph the keyboard cut out twice for a second or two.

Additionally, every second time the mouse reconnects, scrolling via the scroll wheel is painfully slow.

When this is going on, dmesg gets once in some seconds:

[ 381.185787] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
[ 507.351776] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
[ 540.005778] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
[ 627.051731] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
[ 769.329768] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8

I guess it happens when the mouse reconnects.

This can be fixed by unplugging and replugging the Unifying Receiver. This fixes the problem until next boot.

I tried a couple of older kernel versions and the same thing happened. I also just tried Fedora 32 beta and it didn't happen there.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: domin 2235 F.... pulseaudio
 /dev/snd/controlC0: domin 2235 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Apr 26 10:25:57 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-12 (926 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
MachineType: Apple Inc. MacBookPro6,2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=a2abd949-9a7b-43a5-9453-7471311a309b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-26-generic N/A
 linux-backports-modules-5.4.0-26-generic N/A
 linux-firmware 1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-03-26 (30 days ago)
WifiSyslog:

dmi.bios.date: 08/07/17
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.005A.B00.1708072217
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.005A.B00.1708072217:bd08/07/17:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro6,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Dominik (dominalien) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Christian Bourque (christian-bourque) wrote :

I'm experiencing the same behaviour under Ubuntu 18.04 with kernel 5.3.0-51-generic.

My mouse is the Logitech Performance MX and my keyboard is the Logitech K800 (both connected to the Logitech USB unifying receiver)...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Dominik (dominalien) wrote :

It's exactly the same with kernel 5.7.

Revision history for this message
Guy Lunardi (guy-m) wrote :

Facing this issue as well with 5.7.7 on 20.04.

Tried to use logiops and libratbag to configure the mouse better (MX Master 3).

Right now I have two unified receiver dongles connects because I have not taken the time to pair all devices to a single receiver. Would love pointers on how to fix this.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

Revision history for this message
Dominik (dominalien) wrote :

There is no working version I found. It’s broken on a number of recent kernels. As mentioned in the original report, it’s fine with Fedora 32 and whatever kernel is in there.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

What's the kernel version under Fedora 32?

Revision history for this message
Dominik (dominalien) wrote :

Seriously? Here: https://is.gd/WbeePm

I’m just going to take a wild guess here and say perhaps it’s not the kernel.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Fedora doesn't stick to a single kernel version so knowing the exact kernel was used is important.

But anyway, I won't be able to help here.

Revision history for this message
Dominik (dominalien) wrote :

Very well. I’m now running the Logitech receiver on Mint 20 and the kernel is 5.4.0-40-generic from Ubuntu and it works fine.

Revision history for this message
Andrei Nevedomskii (monosoul) wrote :

I have a similar issue, but with direct bluetooth connection (w/o a dingle). I have a Logitech MX Master 3 mouse and Logitech MX Keys keyboard, both connected via bluetooth.
For some reason, they seem to lose connection a few seconds after they connect. Then after reconnect they work fine till the next time they disconnect (purposely, for example during laptop going to sleep).

It was fine with 18.04.3, and started to happen only after I upgraded to 20.04.1.
I tried different distros with different kernel versions, so far I can reproduce this issue with every kernel version higher than 5.3: 5.4 (used in Ubuntu 20.04), 5.6 (Fedora), 5.8 (Fedora).

The issue doesn't happen in openSUSE Leap 15.2 that uses kernel version 5.3.18.

Revision history for this message
borillionstar (babakrezai) wrote :

Also seeing this.

[114400.883710] usb 5-3: USB disconnect, device number 3
[114405.542116] usb 5-3: new full-speed USB device number 5 using xhci_hcd
[114405.718895] usb 5-3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=24.11
[114405.718901] usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[114405.718904] usb 5-3: Product: USB Receiver
[114405.718907] usb 5-3: Manufacturer: Logitech
[114405.757860] logitech-djreceiver 0003:046D:C52B.0009: hiddev1,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:0c:00.0-3/input2
[114410.784914] logitech-djreceiver 0003:046D:C52B.0009: device of type eQUAD step 4 DJ (0x04) connected on slot 3
[114410.898401] input: Logitech MX Keys as /devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/usb5/5-3/5-3:1.2/0003:046D:C52B.0009/0003:046D:408A.000A/input/input31
[114410.898890] logitech-hidpp-device 0003:046D:408A.000A: input,hidraw2: USB HID v1.11 Keyboard [Logitech MX Keys] on usb-0000:0c:00.0-3/input2:1
[114410.912947] input: Logitech MX Master 3 as /devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/usb5/5-3/5-3:1.2/0003:046D:C52B.0009/0003:046D:4082.000B/input/input32
[114410.913371] logitech-hidpp-device 0003:046D:4082.000B: input,hidraw3: USB HID v1.11 Keyboard [Logitech MX Master 3] on usb-0000:0c:00.0-3/input2:3
[114410.942975] logitech-hidpp-device 0003:046D:408A.000A: HID++ 4.5 device connected.
[114411.028897] logitech-hidpp-device 0003:046D:4082.000B: HID++ 4.5 device connected.

Linux bbox 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

babak@bbox:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

babak@bbox:~$ lsb_release -d
Description: Ubuntu 20.04.1 LTS

babak@bbox:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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