046d:c52f [Lenovo G510] Wireless mouse not recognised after reboot

[Thanasis Naskos]

I'm using Ubuntu 14.04 beta 2 64bit with the latest package updates till today, on a lenovo g510 laptop with a Logitech M185 Wireless Mouse. If I reboot my computer with the bluetooth micro-receiver of my mouse plugged in a USB, when it boots it doesn't recognise my mouse.

WORKAROUND: Shutdown the laptop and boot it again without unplugging the receiver.

The problem solved when I've install latest kernel 3.14.0 rc8 and used boot-repair to access the grub menu as I couldn't before (tried pressing SHIFT, setting grub timeout options). After that I've booted again in my old kernel 3.13.0.19 to file a bug report and my mouse was working flawlessly even after reboots. There must be something that the boot-repair tool fixed even if finished with errors http://paste.ubuntu.com/7173127/ .

dmesg after reboot: http://paste.ubuntu.com/7169569/
dmesg after shutdown and reboot: http://paste.ubuntu.com/7169571/
lspci after reboot: http://paste.ubuntu.com/7169573/
lspci after shutdown and reboot]: http://paste.ubuntu.com/7169575/
lsusb after reboot: http://paste.ubuntu.com/7169580/
lsusb after shutdown and reboot: http://paste.ubuntu.com/7169583/

As you can see in the two lsusb files, it is not only my mouse not recognized but no other USB device.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.40
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thanasis 1566 F.... pulseaudio
 /dev/snd/controlC1: thanasis 1566 F.... pulseaudio
Date: Sat Mar 29 11:52:24 2014
HibernationDevice: RESUME=UUID=18e9615a-78c7-4ff4-bd4d-d637eb3dcaec
InstallationDate: Installed on 2014-03-16 (12 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
MachineType: LENOVO 20238
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic.efi.signed root=UUID=1fff532e-1f5c-440a-b22a-7e61a06a246d ro rootflags=subvol=@ quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic N/A
 linux-firmware 1.126
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 79CN46WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G510
dmi.modalias: dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
dmi.product.name: 20238
dmi.product.version: Lenovo G510
dmi.sys.vendor: LENOVO

[Thanasis Naskos (naskoos)]

The workaround/solution I've mentioned is not valid. After some reboots I got the same behaviour. Only when I switch to 3.14.0 rc8 kernel the problem is solved.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Thanasis Naskos, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. 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. For example:
kernel-fixed-upstream-3.15-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[penalvch (penalvch)]

Thanasis Naskos, the next step would be to fully reverse commit bisect from kernel 3.13 to 3.14-rc8 in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Thanasis Naskos (naskoos)]

The bug was fixed on 3.14-rc1. On the previous kernel 3.13.11 it still exists!

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]