Wireless Mouse not registered on Startup or Reboot

[Patrick Gillespie]

Since the last updates to Ubuntu 12.04 Beta 2 (as of March 12), Unity no longer recognizes the wireless mouse after a reboot or when the OS is initially started.

The workaround is to unplug the USB Mouse and plug it back in.

The Mouse: Logitech Anywhere MX

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.6.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,resize,mousepoll,move,obs,place,regex,imgpng,gnomecompat,grid,session,unitymtgrabhandles,vpswitch,animation,wall,workarounds,expo,ezoom,fade,scale,unityshell]
Date: Sat Mar 17 17:23:23 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Patrick Gillespie (vermontpoet)]

This bug continues to worsen with the latest update. After Suspend, the mouse won't work in two out of the three USB ports. The workaround, unplugging and plugging back in, no longer works.

[Omer Akram (om26er)]

that's really not unity's fault I would say

[Patrick Gillespie (vermontpoet)]

OK, I think I'm narrowing this down:

Every time I use the Ubuntu-Tweak (Compiz) "Scale" feature (in my case by going down to the left corner), I lose wireless mouse functionality.

I'm still not sure where this bug should be filed? Unity? Ubuntu Tweak? Compiz?

[Patrick Gillespie (vermontpoet)]

The workaround (so far):

1.) Lock Screen.
2.) Unplug USB mouse.
3.) Plug back in.
4.) Unlock screen.

Also, I can use the compiz SCALE feature without losing my mouse if I use the middle mouse button (assigned in CCSM). So, I'm beginning to think this is an Ubuntu Tweak issue.

[Patrick Gillespie (vermontpoet)]

Scratch those last two comments. I can no longer reproduce the problem with Ubuntu Tweak. If there's a consistent reason why Unity/Ubuntu drops my mouse, I can't narrow it down. The only thing that remains consistent is that 12.04 drops my USB mouse at inconsistent times - when scaling, when using expo, after unlocking the screen and especially after suspend.

I can use the mouse in Xubuntu 11.10 without a hitch. I'm going to test it in the Gnome Session of 12.04.

[Patrick Gillespie (vermontpoet)]

The Mouse adventures continue.

The latest behavior is that the mouse will just stop. I can be in the middle of mousing and it will just stop - no mouse, no connection. I've been wondering whether it's my mouse, but I can restore the connection almost every time thusly:

1.) Click on Lock Screen using touchpad
2.) Mouse functionality magically returns
3.) Unlock Screen
4.) Use Mouse until it Just Stops - Wash, Rinse, Repeat

Is anyone listening, by the way? :-|

[Patrick Gillespie (vermontpoet)]

The mouse has begun exhibiting the same behavior on other OS's, including Windows.

I hereby call this an object lesson in user denial. My mouse is bad. I'm marking the bug invalid.

[NoOp (glgxg)]

Your mouse may be bad, but mine is not and I exerience the exact same symptoms on 12.04 (64bit fully updated as of 2012-03-28. Many times the mouse is not working at the lightdm login page. Mouse & Unifying receiver work just fine with 11.04 & Win7 on the same machine.

3.2.0-17-generic x86_64

046d:c52b Logitec, Inc. Unifying Receiver

Mouse is a Logitec M505.

Removing the USB Unifying Receiver & plugging in again sometimes works. Rebooting sometimes works. Again; only problems when booting/rebooting to 12.04 - mouse & receiver work fine when booted/rebooted to 11.04.

[Lucazade (lucazade)]

@NoOp
same here, mouse is not recognized at boot and I have to unplug and plug again to get it working.
It happens only with a Logitech Perfomance MX with DarkField tech whille other logitech mouse works properly.

[Lucazade (lucazade)]

lsusb when mouse is working and when is not recognized

[Чайка Андрей (bymer3)]

I also has Logitech mouse and I should plug and unplug it to use. It happened only after I have updated to Ubuntu 12.04. I am waiting for solution.

[Bipin Mathew (bipinmathew)]

I can confirm this bug. Downloaded latest beta last night, and wireless mouse failed to be recognized on boot. Had to unplug and replug usb wireless adapter to work. Build:

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.2.0-20-generic #33-Ubuntu SMP Tue Mar 27 16:42:26 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Here is the tail of the /var/log/syslog when reseating the wireless adapter for the mouse:

Apr 17 19:16:17 ubuntu kernel: [ 1875.776157] usb 6-2: USB disconnect, device number 3
Apr 17 19:16:20 ubuntu kernel: [ 1879.328216] usb 6-2: new full-speed USB device number 4 using uhci_hcd
Apr 17 19:16:20 ubuntu mtp-probe: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2"
Apr 17 19:16:20 ubuntu kernel: [ 1879.519730] logitech-djreceiver 0003:046D:C52B.0012: hiddev0,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.1-2/input2
Apr 17 19:16:20 ubuntu kernel: [ 1879.522902] input: Logitech Unifying Device. Wireless PID:101d as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:046D:C52B.0012/input/input18
Apr 17 19:16:20 ubuntu kernel: [ 1879.523138] logitech-djdevice 0003:046D:C52B.0013: input,hidraw4: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101d] on usb-0000:00:1d.1-2:1
Apr 17 19:16:21 ubuntu mtp-probe: bus: 6, device: 4 was not an MTP device

[Bungeur (sanfton-0801)]

Affects me too. Logitech Peformance MX, Kubuntu 12.04 beta2. Old N42 mouse fine. Replugging clears fault, usually.
when I try the receiver in the USB of a Toshiba Port replicator (hub + LAN, serial, keyboard) it NEVER works - and dmesg reports "insufficient bandwidth". Yet this setup works faultlessly on 10.04 Lucid.

[Uğur Çetin (ugur-jnmbk)]

Hi, I'm not sure but this might be related to this debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658029

Looking at the patch in this bug I edited my local /usr/share/initramfs-tools/hook-functions file and added hid-logitech-dj on line 416
then I did:
sudo update-initramfs -u

After a restart, my m505 mouse was correctly working without having to replug the receiver. Still this might be a one time luck. I'll comment again if this stops working later on.

[Lucazade (lucazade)]

@Uğur Çetin (ugur-jnmbk)
great! going to try it asap :)

[Bungeur (sanfton-0801)]

I tried it, too. Performance MX still not recognised at boot. :-(
 (I have no problems at RESUME)

[Uğur Çetin (ugur-jnmbk)]

It seems that was just my luck. Several hours later, mouse wasn't working after a start. Replugging the receiver is the only workaround.

[Frans Bijma (fbijma)]

I have the same kind of problem with my wireless Logitech mouse. Do'nt know the type. But very regularly the mouse just stucks and when I then move it arround a few times it just comes back. I used this same mouse on a windows machine yesterday ( another laptop) without any problem. lsusb allways shows the mouse in the list.

lsusb

Bus 001 Device 004: ID 0a5c:217f Broadcom Corp. Bluetooth Controller
Bus 001 Device 005: ID 17ef:480f Lenovo Integrated Webcam [R5U877]
Bus 002 Device 003: ID 05c6:9204 Qualcomm, Inc.
Bus 001 Device 006: ID 046d:c510 Logitech, Inc. Cordless Mouse

[purtpelhcs (christian-c-benz)]

I experienced the same issue here with my wireless Logitech M325 using 12.04 LTS final amd64.

[Swarnendu Biswas (swarna-cse)]

Yes, thanks for the bug post. This is one feature which has been bothering me to no ends. I am facing this bug since maybe early Jan developer releases of Precise. I have a Dell XPS 15 laptop and a Logitech usb wireless mouse. However, interesting part is that I do not face this issue with Oneiric.

[Patrick Gillespie (vermontpoet)]

Logitech replaced my Anywhere MX mouse. Worryingly, the new mouse worked perfectly with Oneiric, just like my old mouse; but when I booted up the 12.04 partition (same computer) the brand new Anywhere Mouse failed (so far just once) to be recognized. Had to unplug the USB transmitter and plug it back in. Why this is worrisome is that this is precisely how the older mouse began to fail.

I'm concerned that something in 12.04 (the kernel?) is potentially damaging the hardware. I never had problems with my old mouse until I started testing 12.04. Is it sheer coincidence? Seems to me that the severity of the bug should be changed and the devs should start taking this problem seriously - either eliminating possibilities or confirming them.

[JM (jose-mingorance)]

Very same problem here....
Anywhere MX mouse not working at boot with 12.04.

Note that:
With any other previous version of ubuntu it works perfectly.
If I unplug the receiver and then plug it again, the mouse works perfectly. Therefore the problem is only at boot.

[Sree Harsha Totakura (sriharsha-totakura)]

I'm also observing this problem with my logitech M325 mouse.
Instead of unplugging and re-plugging the USB receiver I'm running the following commands as discussed here: http://askubuntu.com/questions/128345/logitech-m515-does-not-work-after-upgrade-to-12-04

as super user:
modprobe -r hid_logitech_dj
modprobe hid_logitech_dj

[Roy J. Villarreal 3 (rojovilla)]

Logitech Performance MX Mouse with same issue. Unplugging/re-plugging solves this issue, but obviously is a hassle. Seems to happen at restart only.

[John Feole (jfeole)]

I am also seeing this bug on a fresh install of 12.04. Mouse is fine, tested on 2 other machines with 12.04. The only way I can get it back is to remove/re-add the Logitech Unifying receiver into USB slot.

JFeole

[Sree Harsha Totakura (sriharsha-totakura)]

I did a recent update through the update manager and this issue seems to have been resolved.

[Roy J. Villarreal 3 (rojovilla)]

Negative, thought it was resolved, but it just happened again to me.

[Sree Harsha Totakura (sriharsha-totakura)]

Yes, I too thought it was resolved. It just happened and I had to restart.

[David Gattrell (david-gattrell)]

Similar story here...
Logitech M515 mouse. Triple boot machine, Windows7, Lucid 32bit, 12.04 64bit.
12.04 is clean install into empty partition.
Mouse operation may or may not work on boot into 12.04 (consistently fine in other OS's)
remove/reinsert USB dongle after boot restores normal operation
sudo modprobe -r hid_logitech_dj; sudo modprobe hid_logitech_dj; also restores normal operation

I'd guess at some sort of race condition. Is the new kernel faster than previous kernels? Is the M515 slower at poweron than other logitech mice?

[Jeahavee (jamillskill)]

When I first boot up and get to the log in screen my mouse doesn't respond. I'm using a fresh install of 12.04. I didn't have this problem when I upgrade from 11.10 to 12.04 (I had other problems which forced me to reinstall 12.04). [64bit only]

[cki (charles-kirsch)]

I have a M510 mouse and K800 wireless keyboard. If the problem appears, it affects both, the keyboard and the mouse. My impression is that if I switch on the devices only after I'm seeing the login screen, that the problem doesn't appear. I didn't have an issue that the mouse/keyboard stopped working after a couple of hours.

[Mário Vrablanský (vrablansky)]

Same issue here .It happens randomly after reboot and i din't have this problem with previous ubuntu releases. Unplug/Plug mostly works .

[Jeahavee (jamillskill)]

Check this out. So yesterday I had to unplug replug, but when I did it I change the USB port to the one right behind it. What's special about that port is that's the original port I had first put the Unity dongle into when I first install this mouse on windows. SO today just now when I logged into 12.04 I turn my mouse on and it moved... I'm thinking maybe the labtop remembers where that port was from the beginning and somehow the OSs remembered the unity dongle was plugged in there from the beginning and so when I first boot up Windows notices the change, 11.10 noticed the change but some how 12.04 didn't notice the change. Maybe it's just my labtop might not be the same for others.

[Patrick Gillespie (vermontpoet)]

My 12.04 install still has occasional problems with my MX Mouse.

I just upgraded my wife's netbook from 11.10, which never once had a problem with her generic Logitech mouse M525, to 12.04. Now, she has to unplug and plug the mouse back in. Sometimes even that doesn't work.

So... is there any point to reporting this information? I have yet to see any effort made toward solving this bug.

I get the feeling everyone here is wasting their time.

[Gunaddho Bhikkhu (taanpeter)]

I have a logitech anywhere mx, as does my 83 year old mother. Both using ubuntu precise with unity. Both having the usb mouse not recognized at bootup and have to unplug and replug to get it working. Ubuntu devs should know that I also dual boot with Archlinux gnome-shell and there are no issues on that distro. This seems to be an Ubuntu exclusive. Any attention would be welcome.

[Mustapha Mond (mustaphamond)]

Same issue here. 12.04 (32bit) 3.2.0-24-generic-pae #39-Ubuntu SMP
Logitech Wireless Trackball M570

[Jon Quiros (jquiros)]

Same here- Release 12.04 (precise) 64-bit Linux tlaloc 3.2.0-24-generic #37-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
with Logitech MX310...
Regards,
Jon

[Uğur Çetin (ugur-jnmbk)]

Hi. I think I found something worth mentioning here.
It only works when mouse is moved before the module is loaded. Example:

sudo modprobe -r hid_logitech_dj
**move mouse**
sudo modprobe hid_logitech_dj

works 100% for me since I last commented here. It doesn't work when I don't move the mouse before loading module. So I think the problem should be related to detection part of this module (hid_logitech_dj).

[memartin (memartin)]

Might be worthwile to have a look at the special powersave features of recent Logitech mice. They are advertised as getting 3 years life out of a set of batteries. So maybe there are mechanisms to turn the mouse or the receiver so completely off when in powersave, tat it is no more recognized by the system on loadding the module. At least not without some special "wake up call", some special USB sequence required to activate the port/receiver/mouse.

This is just my fairy-tale view on the issue, unfortunately I am too dumb to be able to help debug this.

I'm using a Logitech M515 on a recent Kubuntu Oneiric -> Precise Upgrade, and same on another Kubuntu Precise fresh install with an Anywhere MX. Both worked fine under Oneiric before.

BTW, both mice use one of these new Logitech Unity receivers (not to be confused with the Ubuntu Window Manager). It is used to connect several devices to one PC using the same dongle. Maybe that's related, too.

[memartin (memartin)]

Here some additions from dumb checking a few test cases here ;-)

Test | A.MX | M515 |
-------------------------------------------------------|--------|--------|
Just reboot running system * | ok | no |
reboot, moving mouse * | ok | ok |
power down, mouse OFF, boot up, mouse ON | ok | ok |
switch mouse OFF, then ON when not working | no | no |
remove receiver, then reattach when mouse not working | no | no |
boot up while mouse activity LED is ON * | ok | -- |
boot up when mouse activity LED is OFF * | no | -- |

I have also tested if it matters wether the mouse is ON or OFF BEFORE shutdown/reboot: No, it doesn't seem to be the case.

* The M515 has touch sensors that send the mouse to powersave almost immediately after the hand is removed from the mouse's surface (especially the sides). The Anywhere MX in contrast seems to have the classical timeout mechanism, going into powersave after a minute or so after it has last been moved. So that seems to be the reason why it passes the first test (simple restart), whereas the M515 doesn't. It also feeds the assumption that the mice's powersave mode is key to the problem. However, remember that the problem ocurred in 12.04 Precise first, the mice are working without these problems in earlier releases. So it's not a mouse problem after all.

= Conclusion =

I think it is fair to conclude that the mouse is not recognized at boot when in idle/inactive/powersave mode. If you agree, I suggest to change the Bug's summary accordingly, to something like "Logitech Unity Mice are not recognized on boot when in powersave state" and link more specifically to the 12.04 Precise release (if possible), or an adequate package.

= Erratum =

Seems I have let myself to be confused in the first place: The new Logitech receiver is known as "Unifying Receiver", so no danger of confusion except for those like me who are not good at reading and/or remembering :-)

[Andrew T. Aldridge (dubleeh)]

I just updated to 12.04 on an acer one and my logitech m570 wireless mouse doesn't work on boot. I have to unplug and replug.

[avejidah (avejidah)]

Same issue. lsmod

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 001 Device 005: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver

The loading/unload of hid_logitech_dj does not work for me, unfortunately (possibly my mouse simply doesn't use that module).

If I unplug the mouse and plug it back in, it begins to work.
If I log out and log back in, the mouse works.
Also - I am able to launch one application before the mouse stops working. For instance, I can launch the terminal using the mouse, but after launching it, I can no longer click (I can still move the mouse).

Here's my dmesg |grep -i logitech

[ 4.236512] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input3
[ 4.236610] generic-usb 0003:046D:C50E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1a.0-1.2/input0
[ 564.215062] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input13
[ 564.215216] generic-usb 0003:046D:C50E.0002: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1a.0-1.2/input0
[ 1110.978489] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input14
[ 1110.978653] generic-usb 0003:046D:C50E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1a.0-1.2/input0

Lastly, this is a fresh install. I upgraded from 11.10 and had this issue. I formatted yesterday, and installed 12.04 fresh hoping that the issue would be resolved. I also have this issue using 12.04 live.

[89c51 (barz621)]

I am not on ubuntu but this seems to be a general problem with 3.2+ kernels (its the kernel where hid_logitech_dj module was introduced)

There is a bug in the kernel bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=43631 and the hid_logitech_dj module author has been notified and is aware of the bug but was unable to reproduce it on a 32bit system.

Could it be that it is a 64bit only bug??

[Roman Stingler (coolx67)]

could be
my 64bit system is also affected by this bug

[89c51 (barz621)]

If anyone could boot their system with hid.debug=1 log_buf_len=2097152 as a parameter and log dmesg messages when this happens and when it doesn't would be helpful.

[Uğur Çetin (ugur-jnmbk)]

I'm attaching a related portion of my dmesg after using these kernel parameters on 64-bit Ubuntu.

When mouse is working properly, only this line is added to dmesg per move:
/build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15

When cursor is not moving, these 2 lines are added to dmesg per move:
/build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15
/build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: djrcv_dev->paired_dj_devices[dj_report->device_index] is NULL, index 1

[Veli-Jussi Raitila (vjraitila)]

Nope, not 64-bit only. I have the same problem on 32-bit (Logitech Anywhere MX, reconnecting the dongle helps). Wasn't the original reporter on i386 as well?

[David Lambert (davidork-deactivatedaccount)]

I ++THINK++ I have found a fix.

open /etc/modprobe.d/blacklist.conf

comment out the line "blacklist usbmouse" (change to "#blacklist usbmouse") or remove that line altogether and reboot/shut down and cold boot and see if this fixes the issue.

Seemed to work for my dad's pc. If so, i belive this means there is a problem in the usbhid kernel module.

[89c51 (barz621)]

An update from the author of the hid_logitech_module i got this morning:

"A quick update:

We are able to reproduce the issue on our side. After plugging/unplugging several times, I am able to get the same behaviour you observe. This is good.
We are missing one notification from the Unifying receiver that brings the information on the paired devices. This seems to be a race condition that might come from outside hid_logitech_dj module. We need some more time to investigate that. I will keep looking at that during next week.

That being said, we have a quick patch that does not tackle the root problem, but should be a usable workaround. I want to hold back publishing the patch until at least we spend a bit more time in trying to understand the origin of the suspected race condition."

Logitech people are working on it. When the patch gets published or if there is any other update i will post here.

[Luis Alvarado (luisalvarado)]

Confirmed. I was going out of my mind with this. At least with this bug report I know it is a bug and I am not the only one. I guess I found it very odd to see a mouse not supported on Ubuntu. Habit I guess.

[Mark Fraser (launchpad-mfraz)]

Hope this gets fixed soon as I upgraded the wife's computer at the weekend and only came across this bug after she turned computer on for the first time after the upgrade.

This is with a keyboard/mouse combination and this bug causes both to stop working.

[mrsfixit (mrsfixit)]

I am using Xubuntu 12.04, 3.2.0-25-generic #40-Ubuntu.

I have a Logitech M570 wireless trackball, and I am experiencing the same problem.

I came across this on a forum somewhere, and it has been working pretty consistently:

Add following lines to /etc/rc.local

modprobe -r hid_logitech_dj
modprobe hid_logitech_dj

I did this. I have tried booting to the desktop with the trackball switch turned on, and turned off.

With the switch turned on, it works most of the time. I have actually had better luck waiting until the desktop was fully loaded, and then turning the trackball switch on.

YMMV, but I hope this helps somebody as this problem has been driving me bonkers as well.

[89c51 (barz621)]

Ok. This is an update from the author of the hid_logitech_dj module:

"We've found the root cause and we have a patch that we would like you to try.
The culprit is a modification introduced by commit 4ea5454203d991ec that added a new semaphore to each hid_device. This commit came after the hid_logitech_dj driver was included in the kernel and it silently broke it.

This patch should resolve what we observe. It is not a permanent/elegant solution, but it is the only way we can solve the issue without impacting other modules in the kernel. We'd like you to test it on your side and let us know your results.

It is working for me. If as expected, works for you too, we'll publish the patch for inclusion. In parallel we will start a discussion on the best approach to solve the lock issue.

You can ignore a warning about a missing return value on line 469. We'll fix that later before submission."

Attached you will find a preliminary patch.

WARNING: This is for people that want to test it. I repeat this is for testing purposes. If you don't know what you are doing you are advised to wait until it is included upstream. You have been warned.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "Patch for testing" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Uğur Çetin (ugur-jnmbk)]

I tried the patch. Seems to work for me.

[Uğur Çetin (ugur-jnmbk)]

After one day of use, I noticed a small issue with the patch:

* Stop using the mouse for a few seconds.
* Move mouse.
* Cursor starts moving after half a secound later I started moving mouse.

I think mouse wake ups aren't handled fast enough as it was before. I didn't have this issue before and mouse works fine on windows. This might also be related to another bug in Ubuntu kernel 3.2.0-26 in git which I compiled using the patch at comment #55.

[Luis Alvarado (luisalvarado)]

Tried the patch and yes it works but as the above poster mentioned, it has a problem after not using the mouse for a couple of seconds. Like almost a second delay after moving it again.

[Luis Alvarado (luisalvarado)]

Forgot to add that if I do this: modprobe -r hid_logitech_dj as mentioned above

it will freeze the system in that precise moment. No keyboard or mouse (Wired or Wirelessly) will work. Even if I try to connect them again.

[mrsfixit (mrsfixit)]

And meanwhile, that little hack I posted in #54 is still working for me,
boot after boot after boot.

Go figure. :-)

[EV (ebaykembel)]

I have laptop Dell L502X & Logitech Performance MX. Dell worked perfect with Logitech for a year. Then I dicided to move to the new laptop Sony SVE1511MFXS. I took my hdd with installed ubuntu and put it in the new laptop. And the mouse stop working at start.

[Roger Davis (rogerdavis-d)]

 Logitech Mouse Not Found in Ubuntu Bootup
Please read below the ------ line first, then the problem.

When I try to run the CD as a test (downloaded today, 8/7/12, can't check details, the #$^%&* mouse isn't working), the mouse is not found. The keyboard works fine. The mouse cursor only appears momentarily as Ubuntu is in process of booting, and I can't move it during that time. The keyboard, which runs off the same USB receiver (Unified) works.

My guess is that Ubuntu is having problems with the "Unified" single receiver for both keyboard and mouse. See http://www.logitech.com/en-us/promotions/6072 . The mouse / keyboard set I have is MK560.

I am using the AMD64 download (VERY confusing that this is also for Intel 64 bit products!?!?!?
-------------------------------------------
I just got a new high power computer and want to confirm which to install of 12.04 - 32 or 64 bit?

Specs:
Intel DZ77BH-55K motherboard
Intel i7 3770 Ivy Bridge CPU at 3.4 GHz
Radeon 7750 1 Gig 800 MHz display card
16 Gig memory
1T hard drive for Ubuntu only

I thought this might be a common question, but a search turned up nothing definitive.

I simply assumed that 64 bit would be the answer, but I see that 32 bit is recommended, and if I select 64 bit, it appears that I'm still only offered 32 bit even though 64 bit is selected - so WHERE can I get a for sure 64 bit version for normal desktop use?

[Roger Davis (rogerdavis-d)]

I tried rebooting from the live CD while constantly moving the mouse. That made a difference, but just barely. The mouse movement is slow and jerky, next to useless. Almost like trying to help a fall-down drunk take a walk. It took me about 5 minutes just to get logged out.

[Roger Davis (rogerdavis-d)]

The real bottom line is - When will a fix be present in the download disk file ?!?!?!?

It seems that there are at least two possibles (54 and 56 above). There may be others.

Until then, myself and many others have a severe problem with Ubuntu, and most will walk away. Do we really want that?

[Roger Davis (rogerdavis-d)]

OOPS...

Another important point I meant to include above... How will the common Ubuntur know when the fix is done, except to download a disk every day or so and try it...?

[EV (ebaykembel)]

89c51, I just check the patch with kernel 3.4.7 and it didn't work for me.

[John Doe (prometheus--0)]

got a new Logitech k400 wireless touch keyboard which is not detected at boot on my
xubuntu 12.04
adding the already commented modprobe fix in /etc/rc.local resolved the issue

[Peter Ung (ung-peter)]

modprobe -r hid_logitech_dj
moving the mouse
modprobe hid_logitech_dj

This has seemed to help, but is quite annoying. Adding the modprobe commands to rc.local doesn't help. I've experienced this with 3 logitech keyboard combos - MK710 and M510/K350. I've upgraded to Ubuntu 12.10 with the new kernel to see if it fixes the issue but it doesnt.

[jimmy (jimmy-kimal)]

Hi,

I'd like to test the patch suggested in 55, can anyone give me the steps required to apply it?

[Luis Alvarado (luisalvarado)]

The issue is happening again on Ubuntu 12.10 Beta 1. Using the Live USB after the desktop appeared the mouse did not work.

[Luis Alvarado (luisalvarado)]

I need to add that this only happens on the Installer from the Live USB. If you finish installing Ubuntu it will work after rebooting.

[Mercer Rivière (vincentuq)]

Hi,

I just want to note that this is likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990870

[Guy (guy-b)]

Hi,

I came across this bug report for an another reason (mine are well recognized and initialized) but I would like to know if it's possible to disable hid_logitech_dj and return as in the 11.10 release configuration? I have tryied to blacklist it but I remained without mouse (Logitech M705) and keyboard (K800).

 I "suspect" this driver to causing unexplained (irq scheduling race?) mini mouse and graphical freezes and unregular sound pops by web radio which began with release12.04 that I never had seens ubuntu 10.10 and somewhere in relation with mouse scrowling and clicking, like a differed/not synchronised call/instruction. Sorry for maybe misposting here and the lack of informations but this bug report sounds like a plausible reason of the misbehaviors I'm experiencing without rational explanations. Thank you

[NoOp (glgxg)]

@Mercer: Actually 990870 isn't a duplicate of this bug. This bug was filed 2012-03-17 (hence the lower bug number (958174).
000870 was opened 2012-04-29. Further, this bug primarily focuses on Logitech Unifying receiver & hid_logitech_dj.

I've noticed that I've had to:
$ sudo modprobe -r hid_logitech_dj
$ sudo modprobe hid_logitech_dj
on every 12.04 startup the past few days. This followed the 2012-09-13 batch of updates:
Upgrade: unity:i386 (5.14.0-0ubuntu1, 5.16.0-0ubuntu1), libc-bin:i386 (2.15-0ubuntu10, 2.15-0ubuntu10.1), unity-2d:i386 (5.12.0-0ubuntu1.1, 5.12.0-0ubuntu1.2), gnome-media:i386 (3.4.0-0ubuntu2.1, 3.4.0-0ubuntu3.1), unity-2d-panel:i386 (5.12.0-0ubuntu1.1, 5.12.0-0ubuntu1.2), language-pack-kde-en:i386 (12.04+20120801, 12.04+20120910), language-pack-kde-tl:i386 (12.04+20120801, 12.04+20120910), grub2-common:i386 (1.99-21ubuntu3.1, 1.99-21ubuntu3.4), libc-dev-bin:i386 (2.15-0ubuntu10, 2.15-0ubuntu10.1), libunity-2d-private0:i386 (5.12.0-0ubuntu1.1, 5.12.0-0ubuntu1.2), gnome-control-center:i386 (3.4.2-0ubuntu0.4, 3.4.2-0ubuntu0.5), libnux-2.0-common:i386 (2.14.0-0ubuntu1, 2.14.1-0ubuntu1), unity-2d-shell:i386 (5.12.0-0ubuntu1.1, 5.12.0-0ubuntu1.2), unity-services:i386 (5.14.0-0ubuntu1, 5.16.0-0ubuntu1), unity-2d-common:i386 (5.12.0-0ubuntu1.1, 5.12.0-0ubuntu1.2), login:i386 (4.1.4.2+svn3283-3ubuntu5, 4.1.4.2+svn3283-3ubuntu5.1), grub-pc:i386 (1.99-21ubuntu3.1, 1.99-21ubuntu3.4), passwd:i386 (4.1.4.2+svn3283-3ubuntu5, 4.1.4.2+svn3283-3ubuntu5.1), libnux-2.0-0:i386 (2.14.0-0ubuntu1, 2.14.1-0ubuntu1), unity-common:i386 (5.14.0-0ubuntu1, 5.16.0-0ubuntu1), multiarch-support:i386 (2.15-0ubuntu10, 2.15-0ubuntu10.1), unity-2d-spread:i386 (5.12.0-0ubuntu1.1, 5.12.0-0ubuntu1.2), grub-pc-bin:i386 (1.99-21ubuntu3.1, 1.99-21ubuntu3.4), libunity-core-5.0-5:i386 (5.14.0-0ubuntu1, 5.16.0-0ubuntu1), indicator-appmenu:i386 (0.3.97-0ubuntu1.1, 0.3.97-0ubuntu1.2), libc6-dev:i386 (2.15-0ubuntu10, 2.15-0ubuntu10.1), gnome-control-center-data:i386 (3.4.2-0ubuntu0.4, 3.4.2-0ubuntu0.5), nux-tools:i386 (2.14.0-0ubuntu1, 2.14.1-0ubuntu1), language-pack-en:i386 (12.04+20120801, 12.04+20120910), grub-common:i386 (1.99-21ubuntu3.1, 1.99-21ubuntu3.4), glibc-doc:i386 (2.15-0ubuntu10, 2.15-0ubuntu10.1), libgnome-control-center1:i386 (3.4.2-0ubuntu0.4, 3.4.2-0ubuntu0.5), libc6:i386 (2.15-0ubuntu10, 2.15-0ubuntu10.1), language-pack-tl:i386 (12.04+20120801, 12.04+20120910), language-pack-gnome-en:i386 (12.04+20120801, 12.04+20120910), language-pack-gnome-tl:i386 (12.04+20120801, 12.04+20120910)

[Mercer Rivière (vincentuq)]

OK. But are you sure? The other bugreport (and kernel's bugzilla) seems to supersede that one here.

[Richard Boudreau (rbo83)]

This also happens with 2 separate usb logitech receivers, (same or different ports and hubs), which are handling one keyboard and one mouse. So I suspect it is not a 'Race' but simply a bad loading sequence, since grub always finds the keyboard upon booting. The reloading of the module does not always work. Same problem on a desktop, and laptop core duo 32 bit.

[quequotion (quequotion)]

One way to know if you've gotten lucky:

You can watch kern.log in gnome-system-log, "Log File Viewer", while unplugging and replugging the receiver. If you hit the jackpot you should see 2 lines for "logitech-djdevice", one that mentions "USB HID v1.11 Mouse" and another for "USB HID v1.11 Keyboard"

I've found that unplugging and replugging rapidly only reduces your chances.

[Guy (guy-b)]

Can this module be disabled as it was on realese 11.10 where it wasn't present and it woked perfectly?

[Andrea Azzarone (azzar1)]

https://lkml.org/lkml/2012/8/20/378

This can explain why mouse works intermittently.

[Michael Bewley (michael-bewley)]

Using a fresh install of 12.04 on a 2012 model Sony Vaio SVS15116GG, I had this same problem - my Logitech MX Anywhere mouse stopped working sometimes. Occurs after suspend, on fresh boot, etc. It seems fairly unpredictable what causes it, but sometimes even booting fresh without the receiver plugged in, and then plugging in (or unplugging/replugging failed).
I was just caught in the situation with unplug/replug not helping, and there seemed to be no way to get it working again. The suggestion from an earlier commenter to try unplug/replug after locking the screen worked!

[NoOp (glgxg)]

The unplug/replug workaround isn't of use if the machine is under a desk or in another room. This is what I use instead:

Open gedit and enter the following:

sudo modprobe -r hid_logitech_dj && sudo modprobe hid_logitech_dj

save the file as Mouse.sh in the Desktop directory. Open Nautilus & (or use a CLI) and make the file executable:
right-click on the file|Properties|Permissions| tick the Owner 'Execute' box & exit.

You'll now have a 'Mouse.sh' icon on the desktop. When you login and the mouse isn't working, use the arrow keys to get to the icon, hit return & use the arrow key to 'Run in Terminal', enter. You'll now be shown a terminal and be prompted for your password, enter your user password & return. That works for me.

It's unfortunate that users have to resort to these types of workarounds... particularly given that this bug is a regression.

[quequotion (quequotion)]

>>82 Good idea. I think I'll make a shortcut so I can run this from unity.

There is apparently an updated version of the patch in this thread which may already be committed, but may not actually fix anything. I find it very hard to correlate the discussion here, in the upstream bug report (linux-kernel-bugs 43631, link at the top of this report), and this one: https://patchwork.kernel.org/patch/1490961/

It seems the issue is known, fixes have been tried, but there are no confirmations that the fix works and I can't figure out which kernel branch it's being tested in or if it's already in the kernel.

[Jonas Amstutz (jonas-amstutz)]

A startup script with the following commands works for me and my thrust mouse:

sudo modprobe -r usbhid
sudo modprobe usbhid

[Karol Szkudlarek (karol-mikronika)]

Logitech M525 and plug/unplug unifing receiver doesn't helps. Mouse is stuck forever.... (ubuntu 12.04, latest, greatest)

[Guy (guy-b)]

Hi, seens today kernel update my mouse and keyboard are not responsive anymore..! I had no problems before.

[DR. VIMAL HURRY (vhurry200)]

Same problem here with my Logitech M325 mouse & wireless Logitech K360 keyboard. They were worked perfectly well on Ubuntu 11.10. Just tried Ubuntu 12.10 Beta 2 but to n avail :(

[DR. VIMAL HURRY (vhurry200)]

but to no avail!

[Nick S (pinkcoons)]

To make mine work, I have to repeatedly run

sudo modprobe -r hid_logitech_dj
sudo modprobe hid_logitech_dj

some number of times (anywhere between one and ten) at each boot. I wrote a script for it, but this is silly.

[Donnavon Hallgren (don-hallgren)]

I have this same exact issue on 12.10 Beta 2 as of today on my Inspiron 15R Notebook (Inspiron 7520) using the Logitech Anywhere MX mouse. after spamming "sudo modprobe -r hid_logitech_dj && sudo modprobe hid_logitech_dj" a few times the mouse pointer comes to life until I reboot again.

[anna van puijenbroek (anna-vanpuijenbroek)]

same problem here on the ASUS zenbook

[Zelcor (x-launchpad-dev-null-name)]

same problem with dell xps L521X / fedora 17 / kernel 3.6.3-1.fc17.x86_64 / M505 mouse

[wilbur.harvey (wilbur-harvey)]

I have several systems, all running 12.10 at this point.
Older Logitec mice without the Unifying dongle work always, on all machines.
Mice with the Unifying dongles have been working always on my machines with USB2 ports.
Mice with the Unifying dongles have never worked properly (12.10) on my Sony Z-Series with USB3.
Sometimes unplugging/plugging in the dongle will make it work, but it will randomly stop working.

[Ian Brock (brock-physik)]

I intermittently had the problem with slow and delayed mouse movement (Logitech M505) in Ubuntu 12.04. I upgraded to 12.10 last week and the problem appears much more often. My usual fix in the past of booting Windows 7 and then rebootting with Ubuntu did not fix the problem any more.
I tried fix #50, i.e. commenting out "blacklist usbmouse" and since then things are OK (several new starts and suspends), but only only one day of testing so far.

[Luis Alvarado (luisalvarado)]

The problem is back again in 12.10. Have not tried the #50 fix yet, but the common problems for me are:

1. Mouse moves correctly until I stop using it for a couple of seconds. After that it behaves good for 0.5 seconds, then bad for 0.5 seconds and this behavior continues until I remove the usb dongle plugged in.

2. The distance the mouse covers is smaller now on the same area I was doing the check. Nothing was added or removed from the room I was doing the check, somehow it works worse now at about 3 meters when it worked perfect in 5 and after 5 is when it started to loose effect (Tested batteries).

3. The "unifying effect" does not work between my Anywhere Mouse and my M600 Touch Mouse. I think they hate each other.

[Ian Brock (brock-physik)]

The "# blacklist usbmouse" solution I mentioned in #94 does not work every time. I therefore blacklisted usbmouse again.

The following combination of workarounds seems to work reliably (at least for the past 3-4 days):

http://askubuntu.com/questions/128345/logitech-m515-does-not-work-after-upgrade-to-12-04/202627#202627

i.e. I installed the logitech-unifying.sh script advertised there in /etc/init.d/. This script removes and reinstalls hid_logitech_dj

In addition, when I boot my laptop (Dell E6410 with (K)Ubuntu 12.10) I keep the mouse (Logitech M505) switched off and only switch it on 10 seconds or so after I have logged in.

[Mercer Rivière (vincentuq)]

Unfortunately the problem persist.
Sometimes after a boot the mouse is still not working, unplug and plug results with:

[10282.964070] hub 1-0:1.0: unable to enumerate USB device on port 3
[10434.128070] usb 2-4: new low-speed USB device number 2 using ohci_hcd
[10434.438116] input: HID 1241:1166 as /devices/pci0000:00/0000:00:02.0/usb2/2-4/2-4:1.0/input/input4
[10434.438985] generic-usb 0003:1241:1166.0001: input,hidraw0: USB HID v1.00 Mouse [HID 1241:1166] on usb-0000:00:02.0-4/input0
[10434.439047] usbcore: registered new interface driver usbhid
[10434.439052] usbhid: USB HID core driver
[10434.440748] usbcore: registered new interface driver usbmouse
[10434.440756] usbmouse: v1.6:USB HID Boot Protocol mouse driver

[wilbur.harvey (wilbur-harvey)]

I agree, with my Logitec Anywhere MX mouse, it works a little better, but
still, most of the time I have to plug/unplug the dongle several times.
I am running the latest 12.10 updates.

On Fri, Dec 21, 2012 at 12:04 PM, Mercer Rivière
<email address hidden>wrote:

> Unfortunately the problem persist.
> Sometimes after a boot the mouse is still not working, unplug and plug
> results with:
>
> [10282.964070] hub 1-0:1.0: unable to enumerate USB device on port 3
> [10434.128070] usb 2-4: new low-speed USB device number 2 using ohci_hcd
> [10434.438116] input: HID 1241:1166 as
> /devices/pci0000:00/0000:00:02.0/usb2/2-4/2-4:1.0/input/input4
> [10434.438985] generic-usb 0003:1241:1166.0001: input,hidraw0: USB HID
> v1.00 Mouse [HID 1241:1166] on usb-0000:00:02.0-4/input0
> [10434.439047] usbcore: registered new interface driver usbhid
> [10434.439052] usbhid: USB HID core driver
> [10434.440748] usbcore: registered new interface driver usbmouse
> [10434.440756] usbmouse: v1.6:USB HID Boot Protocol mouse driver
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/958174
>
> Title:
> Wireless Mouse not registered on Startup or Reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/958174/+subscriptions
>

[Mercer Rivière (vincentuq)]

Btw, as for the (WIRED!) mouse, the difference is with these modules in before/after plug/unplug:
+usbmouse 12666 0
+usbhid 41937 0
+hid 77428 1 usbhid

So I guess it's not hid_logitech_dj's cause...

[Zoran Jeremic (zoran-jeremic)]

Seems that solution suggested in #50 works for me too.

[Mercer Rivière (vincentuq)]

For me works an USB extension cable - the plug is close to the keyboard (which is on PS/2, great!) and makes plug/unpluging more easy.

Can we make that an official fix?

[wilbur.harvey (wilbur-harvey)]

The problem seems to be only with certain USB controllers.
Problems with two different new Sony Vaio with USB3 controllers.
Exact same configuration on my older Dell Studio 15 and there are no
problems.

On Mon, Jan 7, 2013 at 11:16 AM, Mercer Rivière
<email address hidden>wrote:

> For me works an USB extension cable - the plug is close to the keyboard
> (which is on PS/2, great!) and makes plug/unpluging more easy.
>
> Can we make that an official fix?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/958174
>
> Title:
> Wireless Mouse not registered on Startup or Reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/958174/+subscriptions
>

[Mercer Rivière (vincentuq)]

I don't have a same configuration, but LTS on 5 machines (two DELL laptops, one very old DELL workstation, one recent HP Z820 and a desktop which is hard to describe), out of them, only on a single one (the last desktop) the problem manifests itself.

[Mark Bokil (mark-bokil)]

On a Lenovo GT780 with Ubuntu 12.10 I have mouse failure at startup. I have to do:
 sudo modprobe -r hid_logitech_dj && sudo modprobe hid_logitech_dj
about 2-5 times to get the logitech m325 to work.

[Luis Alvarado (luisalvarado)]

The problem for me is with 2 Logitech wireless mice:

- Anywhere mouse with it's Unified connector
- Touch Mouse m600 with it's Unified connector

I say "with it's Unified connector" because both do not work automatically when ing to use only one connector. There is actually no "unified" connection. But this is just another problem.

The problem with both is that if they stay a couple of seconds without use, they start a blinking game where they work for 0.5 seconds and then do not. It repeats forever. This affects 12.04 and 12.10. Have not yet tested 13.04

[Gabriel Thörnblad (gabriel-thornblad)]

Same problem here on Ubuntu 12.10 and Ubuntu 13.04 (kernel 3.8.0-4-generic) with a Logitec Anywhere MX mouse. Worked fine on my old laptop with Ubuntu 12.10. This computer has USB 3 ports, my old one only had USB 2.

[g3n1uss (g3n1uss-yandex)]

The same problem. I think the reason is USB 3, cause it works fine on my old laptop with USB.

[Jason Shultz (1-jason)]

I can confirm that I'm having the same issue. I was able to restore mouse functionality by:

1.) Lock Screen.
2.) Unplug USB mouse.
3.) Plug back in.
4.) Unlock screen.

I have a Logitech Anywhere MX Notebook mouse.

[Jason Shultz (1-jason)]

I should add that I'm on Ubuntu 12.10 on a ASUS A55A-AH51. I have all the latest updates as well.

[Kaiz Vohoumger (hx6030)]

I confirm that this bug is fixed by the solution presented in comment 50.

I am using ubuntu 12.04 64bit with the latest updates and confirm this exact issue with a standard wired usb mouse. The keyboard is also affected but with a much lesser frequency than the mouse.

Since applying the fix in comment 50, I have had no problems whatsoever. I immediately noticed this problem when recently upgrading to 12.04 after years of trouble free operation on the previous ubuntu LTS release.

Based on my understanding of how the fix works by unblacklisting the usbmouse module and the intermittent nature of the problem (eg 50% failure rate on boot) - I would say that the hid handling subsystem of the 3.2.0-37-generic kernel has some kind of race condition which causes it to fail to identify the usb mouse.

In my 15 years of using linux this is the first time I've had a problem with a mouse being recognised!

Hardware AspireR3610, nvidia Ion, Logitech optical mouse M-bt96a

[Ben Copeland (bcc)]

I also have this problem on Ubuntu 13.04.

Have to unplug and plug the receiver back in to get the keyboard and mouse to work. Sometimes have to do it more than once.

[mo cook (mo-cook)]

I had this problem with 12.04 with the device plugged into a standard USB slot on the back of the machine itself.

But.... When I plugged it into an existing powered USB port instead of directly into the back of the machine it worked fine.... And still does after several reboots.

No idea why.... It's just a simple NEWLINK 4slot box which also has the Wireless adaptor and the printer plugged in.

This seems to have solved the problem for me!

[Kent57 (kent5700)]

Can confirm this problem still exists in Kubuntu 13-04 clean install with a Logitech Cordless Optical Trackman. Running "lsusb" shows the wireless device is there but it does not function.
Solutions offered in posts 40 & 50 do not work only unplugging and plugging it back in, resolves the issue till next time.

[mabox (mabox)]

I can confirm that this problem not longer exist for me in Ubuntu 13.04 with a Logitech Anywhere MX. For me this problem is fixed.

[Jeffrey Seria (kl7jef)]

I am new to Linux and just loaded Ubuntu 12.04. Even during install I had to use the keyboard to complete it. I can move the cursor with the mouse without problem, it's just that I am unable to left click on anything all of a sudden. I have tried all the above suggestions to no avail. My mouse is a Logitech M510. Does anyone have suggestions on a mouse that isn't susceptible to this bug?

[MEB (mysticeyeblink)]

Problem still exists in Ubuntu 12.04 with kernel 3.2.0-47-generic-pae #72. I've Logitech M505. Sometimes shutdown system and then start helps but rarely. My USB port hurts :(

[penalvch (penalvch)]

Patrick Gillespie, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, 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 mainline kernels archive directory 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. 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-v3.10-rc7

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

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

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.

[J.J. Valenzuela (computer-b)]

Comment 50 worked for me. I have Logitech K800 keyboard and M510 mouse, both use the Unified Wireless Receiver (USB) and on boot (on Mint 15) they would never load, I had to unplug and plug the receiver in before they would work. commenting out usbmouse and usbkbd worked for me. They now load on boot.

[J.J. Valenzuela (computer-b)]

I spoke too soon. Comment 50 did not work for me after another reboot.

very frustrating

[J.J. Valenzuela (computer-b)]

This is what I'm going to try tonight:
1. Use a USB 2.0 port instead of USB 3.0. This thread seems to have a pattern of people having it not work on boot with USB3 but it works fine on USB2.
2. If that doesn't work, try software from www.hidpoint.com
3. If that doesn't work, update to the very latest kernel, 3.10 i believe.

[J.J. Valenzuela (computer-b)]

Seems that

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

Is all about this bug also and there was a fix in kernel but now it no longer works in the latest 3.10

[Evgeny Barsukov (evg-barsukov)]

The bug in NOT present in 3.9.8, but it's back in 3.10. I've tried all
ports (2.0 & 3.0)

[almadana (almadana)]

Same issue for me, mouse won't work in kernel 3.10 (3.10.3, 3.10.6...)

~$uname -a
Linux vaiaia 3.10.6-031006-generic #201308112316 SMP Mon Aug 12 03:17:33 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Works great with 3.8 kernel in Raring though.

[penalvch (penalvch)]

almadana, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the official Ubuntu documentation:
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

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

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Felix Moreno (info-justdust)]

same problem here, in ubuntu 13.10 is not working mouse at start a problem if u have encrypted partitions...
probably the solution is the same as this...
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1066376

[penalvch (penalvch)]

Felix Moreno, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.