random desktop hangs while using mouse

I am still experiencing the same problem with or without the USB mouse. Using the touchpad, the same problems re-occur.

Same exact problem. I've been trying to narrow it down. I removed Flash 9, thinking it might be that but it still happens. Running Opera 9, Nvidia proprietary drivers, gaim, and apache2. I've been trying to narrow down the problem this week.
Using USB Logitech G5 mouse with mouse polling set to 2. USB Creative Fata1ty keyboard.

Athlon 64 3600+ X2 Brisbane, Biostar T-Force 550, 2GB G.Skill DDR2 800 :: Feisty Fawn 64

A similar problem related to this I am having is that my active window will stop responding (gnome) and I cannot interact with the screen AT ALL until I press alt+tab. When I do that the Alt+Tab screen flashes for a split second and the system it back to normal. I suspect these two problems are related.

I'll try to use https://help.ubuntu.com/community/DebuggingSystemCrash when it happens again.

I dragged a picture around on my desktop around until my GUI hung.
Included is the systemcrash info.

Froze again and I switched to a console. Killing nautilus brought gnome back to a usable state. Still not sure how to fix it.

I'm still experiencing this problem randomly and I tried the suggestions you made but it didn't log anything.

Erwin:
Are you using any binary drivers like the NVIDIA ones?

Nothing I tried fixed this problem. I upgraded my NVIDIA binary drivers, tried not using Flash 9, removed all gnome settings in my home directory, tried reinstalling human-cursors-theme, reinstall nautilus. I'm completely out of ideas.
I did find my related problem: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/41301

No dice on this one. Included is another trace.

@Sitsofe

Nope. I am only using the default drivers from Feisty.

@cappy

I am not sure if https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/41301 is related at all. The symptoms are different and the workaround doesn't work for me.

Again, in my case X totally hangs on and the mouse pointer cannot be moved around at all.

Yeah, that other bug isn't related to this one - sorry for not being clear there.
I reinstalled Feisty today and this bug is still happening.

I found a workaround to the problem. If the mouse hangs, I switch to a new desktop (ie ctrl+alt+right arrow) and return to the previous one.

This seems to "un-hang" the application.

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments 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 '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!

1) $ uname -a
Linux cappy-chan 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux

I no longer have this problem! It was fixed for me at the same time as https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/41301
For me it just may have been that the above bug caused this one for me. I havn't had the freeze-ups (tm) in a week!

Thank you much!

I'm happy for you. I'm not having such luck.

Still getting random hangs even while using apps like gnumeric. In fact, it happens very often in gnumeric that I have to use OOo Calc instead.

Just to add that 99.9% sure I still have this problem as well (i.e. since the 41301 fix). Hasn't reoccurred for a bit but, if it does, I'll post the log info for the Kernel team.

For info, I'm running 64-bit Feisty on an Acer Aspire 5101AWLMi laptop, with a USB MS Trackball Optical (have never not used this mouse, so don't know if problem would occur just with touchpad, as other posters have mentioned).

Standard Feisty install with the usual multimedia add-ons (am using ATI proprietary graphics drivers). Exact same symptoms and definitely different to (now closed) 41301 - Alt-Tab becomes unusable, cursor stuck in whatever operation was underway (generally a resize) and had to virtual console and kill nautilus to fix.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

I'm having a similar problem with my usb-wireless-mouse.

If I don't attach the mouse to my acer aspire one 110. The system works as expected. The system works with the usb-mouse attached, but when I remove the wireless receiver from the USB-port the touchpad is not taking its place. The keyboard works most of the time. Sometimes the system hangs completely and the capslock flashes.

If the system doesn't lock completely I can install the usb-wireless mouse again and I can use the usb-mouse, but not the touchpad.

Before when I had a wireless logitech mouse the touchpad started to work again. After I replaced the mouse with a Kensington USB-wireless mouse this problem started.

I'm using ubuntu 8.10 with all updates available.

I found out what it was: I had without my attention managed to press FN+F7.

This locks the mousepad.

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.