046d:c52b Cannot use logitech mouse M324 (Unifying Receiver)

Bug #1028806 reported by Nico Gevers on 2012-07-25
90
This bug affects 18 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Debian)
Confirmed
Medium
linux (Ubuntu)
Medium
Unassigned

Bug Description

I'm using an Asus N56VM notebook with Ubuntu 12.04 and have tried to attach my wireless mouse. All ports are usb 3.0. The mouse has connected once or twice, but i haven't been able to get ubuntu to recognise it at all today. Incidentally it does work on my mac-mini also running ubuntu 12.04.

Here's the lsusb output:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 13d3:3362 IMC Networks
Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.

and a snippet from syslog when I disconnect the dongle then re-insert it:
Jul 25 10:19:59 G-Powerhouse kernel: [ 683.519591] usb 3-4: USB disconnect, device number 2
Jul 25 10:20:02 G-Powerhouse kernel: [ 686.143575] usb 3-4: new full-speed USB device number 3 using xhci_hcd
Jul 25 10:20:02 G-Powerhouse mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
Jul 25 10:20:02 G-Powerhouse mtp-probe: bus: 3, device: 3 was not an MTP device
Jul 25 10:20:02 G-Powerhouse kernel: [ 686.165347] logitech-djreceiver 0003:046D:C52B.0006: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
Jul 25 10:20:02 G-Powerhouse kernel: [ 686.165635] logitech-djreceiver 0003:046D:C52B.0006: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32
Jul 25 10:20:02 G-Powerhouse kernel: [ 686.165883] logitech-djreceiver: probe of 0003:046D:C52B.0006 failed with error -32

Potential duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143 .

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-27-generic 3.2.0-27.43
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nico 2072 F.... pulseaudio
CRDA:
 country FR:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a10000 irq 48'
   Mixer name : 'Realtek ALC663'
   Components : 'HDA:10ec0663,10431477,00100002'
   Controls : 23
   Simple ctrls : 12
Date: Wed Jul 25 10:31:16 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2152e036-91e2-41e6-ac60-3a902baf3b87
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: ASUSTeK COMPUTER INC. N56VM
ProcEnviron:
 LANGUAGE=en_ZA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=0a4363a2-9382-4042-92f9-3f7ffd349980 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-27-generic N/A
 linux-backports-modules-3.2.0-27-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VM.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VM.206:bd04/13/2012:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Nico Gevers (ingevious) wrote :
Brad Figg (brad-figg) on 2012-07-25
Changed in linux (Ubuntu):
status: New → Confirmed
Logan Rosen (logan) wrote :

I just linked an upstream kernel bug about the same exact receiver not working in a USB 3.0 port, but it does work in a USB 2.0 port. This looks like the same exact issue that you're having.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Edward Donovan (edward.donovan) wrote :

Hey, Logan, thanks! It's great to know it's already reported upstream, and it's great to have a workaround, with USB 2.0 ports.

summary: - Cannot use logitech mouse M324 (Unifying Receiver)
+ 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver)
tags: added: needs-upstream-testing
Changed in linux:
importance: Medium → Undecided
status: Confirmed → New

Nico Gevers, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux (Debian):
importance: Unknown → Medium
status: Unknown → Confirmed
Rainer Rohde (rainer-rohde) wrote :

I have the same issue. Had it on my Dell XPS 15z and now on my Asus G75. It seems that if I unplug/plugin the unified receiver multiple times, it will connect eventually. Of course, this is not how it's supposed to work, but functions as a workaround for now...

Rainer Rohde (rainer-rohde) wrote :

Oh, forgot to mention that I never had that issue on my MacBook Pro, which only had USB2 ports...

robert.vertesi (vertesi) wrote :

I have a similar problem with somewhat different hardware. I use a Lenovo u300s and a Logitech M310 set.
When the receiver is plugged in the USB3 port the keyboard works fine but the mouse does not.
You can see it detected when you list xinput however.
In the USB2 port they both work fine.

Rainer Rohde (rainer-rohde) wrote :

I noticed that this morning when I booted up into Quantal I had to keep plugging in the receiver eight (8!) times before the mouse was recognized.

After a subsequent reboot, I only had to do it twice...

Rainer Rohde (rainer-rohde) wrote :

So, after a while of experiencing this bug with Quantal alpha 3, I can say that I have to unplug and insert the Logitech unifying receiver every time I reboot the laptop:

                          THREE (3) to FOURTEEN (14) times before the mouse pointer can be moved.

This is really, really annoying.

Is there anything that can be done to help troubleshoot this? Dmesg always finds the device, but it takes a lot of unplugging and inserting before it finally works.

[ 2.215235] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
[ 2.218025] input: Logitech Unifying Device. Wireless PID:1028 as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/input/input4
[ 2.218126] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on usb-0000:00:14.0-4:1

tags: added: kernel-bug
tags: added: quantal
Rainer Rohde (rainer-rohde) wrote :

Beta 1. This issue still persists.

This morning I had to unplug the unified receiver 37 (!) times before my Logitech Trackman was recognized. This is REALLY getting old now.

When can we expect a fix?

tags: removed: kernel-bug quantal
Andreas Raster (rakete) wrote :

Having the same problem in 12.04 here. Plugging and Unplugging the receiver multiple times does eventually fix the problem, although I had to do it very often.

Rainer Rohde (rainer-rohde) wrote :

@Andreas:

Have a look here (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143), I experience the same issue. I just found out that this issues DOES NOT exist in 10.04, so this is definitely a kernel regression.

I have encountered the same issue with a Logitech unifying receiver, with K350 keyboard and M505 mouse.

I set up the receiver on a Windows machine with no problem, but when I tried to use it with a new Dell Inspiron (USB3, Ubuntu 12.04) I could not get the mouse or the keyboard to work at all until I used the workaround posted by Rainer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143). Even so, I still need to unplug and re-plug the receiver on reboot.

I also found the same keyboard and mouse (and receiver) would not work with a very old laptop running Ubuntu 12.04, with only USB1 hardware, but that may be a limitation of the hardware.

Rainer Rohde / robert.vertesi / Andreas Raster / Robert John Bowles, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may cause your problem to not be addressed as quickly as possible.

Thank you for your understanding.

I'm sorry Christopher, I am not sure I do understand. I don't think I have a 'new' bug to report, the common issue here is the failure of the Logitech unifying receiver. I just wanted to help by adding my own experience to this thread.

description: updated
Gavin Graham (gavingraham) wrote :

I have the exact same hardware as the OP and the same symptoms. Is there any information I can submit to progress this bug report?

Gavin Graham (gavingraham) wrote :

I'm installaing 3.7.0-7.15 (https://launchpad.net/~xorg-edgers/+archive/ppa/+build/4065823) in an effort to solve another problem so I will let you know how this Kernel goes. It's the Kernel that is part of xorg-edgers.

Well there's no difference by using the xorg-edgers Kernel:
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.407752] usb 3-4: new full-speed USB device number 3 using xhci_hcd
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426452] usb 3-4: New USB device found, idVendor=046d, idProduct=c52b
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426460] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426463] usb 3-4: Product: USB Receiver
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426466] usb 3-4: Manufacturer: Logitech
Dec 17 04:32:54 gavin-N53SV mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
Dec 17 04:32:54 gavin-N53SV mtp-probe: bus: 3, device: 3 was not an MTP device
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.431715] logitech-djreceiver 0003:046D:C52B.0006: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.431975] logitech-djreceiver 0003:046D:C52B.0006: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.432184] logitech-djreceiver: probe of 0003:046D:C52B.0006 failed with error -32

Gavin Graham (gavingraham) wrote :

Ok, I've now installed the Kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/ and I am still getting the exact same error messages. The device will always work if I hotplug once booted.

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

Other bug subscribers

Remote bug watches

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