Comment 179 for bug 195982

Revision history for this message
Alex F (frase) wrote :

I regularly use two different Ubuntu Hardy machines -- one at home, and one at work. I've had this same problem off and on for the last month or two on my work machine, but never on my home machine.

Similarities:
- both are desktops with NVidia graphics cards
- both use the proprietary NVidia driver
- both use Gnome
- both are kept fully up-to-date from the repositories
- both use kernel 2.6.24-19-generic
- both use xserver-xorg 1:7.3+10ubuntu10.2 and xserver-xorg-core 1:7.3+10ubuntu10.2

Differences:
- at work Hardy was upgraded from Gutsy; at home Hardy was installed clean
- at work I run 32bit Hardy on (I think?) an Intel; at home I run 64bit on an AMD64
- at work I have VMware Workstation (5.5.7 build-91707, with anyany116) running constantly (Windows 2000 on the VM); at home I do not use it at all
- at work I have Compiz enabled; at home I do not
- at work my keyboard, mouse and monitor are connected via KVM; at home they are connected directly

Comments:
- My (Win2k) VM at work does have VMware Tools installed.
- I have only ever noticed the problem while releasing control from the VM to the (Ubuntu) host, but it doesn't happen every time I do so, and correlation is not causation. Nonetheless, others seem to also only have the problem when releasing from VMware to the host.
- I never use my VM fullscreen so in my case, it isn't related to CTRL-ALT-ENTER.
- My VM is set to release control when the mouse leaves the window, so I always do it that way -- I never use CTRL-ALT to release control.
- When it does happen, SHIFT, CTRL and ALT stop responding in Ubuntu or any running program, but continue to work normally in the VM. I haven't noticed how CAPSLOCK behaves in my case.
- Existing Ubuntu apps keep running normally, but new apps generally crash the moment I press any key with them focused, including Terminal. I don't know how long existing apps would continue to run since I can't work that way, so I have to log out and back in to restore the keyboard pretty quickly.
- I didn't know about the 'setxkbmap' solution so I've never tried that.

Here's hoping for a solid solution soon. :/