System lockup when moving mouse after launching a program

Bug #120465 reported by James Sewell on 2007-06-14
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)

Bug Description

I have a new install of Feisty, all updates installed. If I click on an icon in my launcher area and then immediately move my mouse, the entire system locks up hard. The mouse stops moving and the animated busy cusrsor stops animating. The system doesn't respond to left or right clicks and no key presses. numlock and capslock won't even toggle. The only way out is to hit reset on the tower.

I have most frequently seen with firefox, but other programs do it too. I installed Thunderbird and put it on the launcher and it does to too.

It seems if I click the laucnher and am very careful not to move my mouse, the program starts and seems to run OK. It only seems to be a problem if I move the mouse immediately when starting a program.

Paul Dufresne (paulduf) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] . I have classified this bug as a bug in linux-source-2.6.20.

Please include the following additional information, if you have not already done so (please 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.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "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 [WWW] Thanks in advance!

Paul Dufresne (paulduf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers