Mouse pointer won't move on boot

[Edvin Lindström]

On boot, sometimes the mouse pointer is stuck and won't move unless the mouse is plugged out and back in, and even then it will only work for a few seconds until it's stuck again. It's Apple's Mighty Mouse. I dual-boot OS X, and the problem only seems to appear when I have just been in OS X and reboot into Ubuntu. After an arbitrary amount of reboots, the problem disappears.

I'm using Ubuntu 8.04.1 on a 64-bit Mac Pro.

I can fully understand if this is given a low priority, but it is very annoying.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Edvin Lindström (bongrouge)]

Yes, it's still there in Intrepid, but it doesn't happen quite as often. Maybe every three reboots from OS X or so.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.recognized.log" after a fresh boot where the mouse is recognized properly and attach the resulting file "dmesg.recognized.log" to this bug report.
3. Please run the command "dmesg > dmesg.problem.log" after a fresh boot where the mouse is *not* recognized properly, and where you unplug and replug the mouse to work properly, and attach the resulting file "dmesg.problem.log" to this bug report.
4. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Edvin Lindström (bongrouge)]

The problem seems to occur more infrequently than before. Both times it has happened since your comment the problem was gone after I plugged the mouse out and in again. dmesg.log.problemgone is the output of dmesg after I unplugged and replugged it, dmesg.log.problem is before I unplugged it.

uname -a gives:
Linux ubuntu 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

[Ricky Campbell (cyberdork33)]

Edvin, I think you forgot the attachment.

[Edvin Lindström (bongrouge)]

How so? I can see it just fine in my previous comment? See: http://i33.tinypic.com/2v0fp7r.png

I'll attach it to this comment too.

[Ricky Campbell (cyberdork33)]

Yes I I see it now. I am just blind.

[kernel-janitor (kernel-janitor)]

Hi Edvin,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 267222

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Edvin Lindström (bongrouge)]

This problem hasn't occured since I upgraded to Jaunty, so it appears to be fixed.

[Leann Ogasawara (leannogasawara)]

Thanks for the update. Marking this Fix Released based on the previous comment.