Ubuntu :: Key Gets Stuck When Disabling Keyboard?

I'm running into some weird behavior while using xinput to disable the keyboard that might be an underlying bug, and I'm wondering if anyone could reproduce it or provide any insight into what's causing it. I'm running Ubuntu desktop 10.10 64-bit in a VMware Workstation VM running on a Windows 7 64-bit host.First I use "xinput list" to find out which keyboards are present in the system. In my case there's only one with id=9. Next I execute "xinput set-prop 9 "Device Enabled" 0" to disable the keyboard at id=9. Now, if I type this into the terminal and hit enter, the keyboard gets disabled but at the same time the enter key becomes stuck. The system thinks the enter key is being held down.

However, if I make a script with the same command and execute it by clicking it in Nautilus, the keyboard gets disabled and no keys are stuck. It seems if the keyboard is disabled with a press of the keyboard, then whatever key was pressed to trigger the disabling of the keyboard becomes stuck.

You might ask why I would want to disable the keyboard in the first place. It's because I'm running Ubuntu in VMware Unity mode, where the system in the VM is integrated with the host desktop system, the VM's windows appear as individual windows on the host desktop,etc. In this mode, whenever I close a VM window by hitting a key on the keyboard (for example, hitting Ctrl+D while in gnome-terminal) and focus goes back to a host window, then that key becomes stuck the next time I open a VM window. If I close a VM window by clicking the mouse then there's no problem. I'm pretty sure now that this is caused by the above mentioned bug from disabling the keyboard. I think in Unity mode VMware workstation runs a script to disable the keyboard in the guest whenever VM windows lose focus, so key presses don't continue to be piped to the guest OS. However, if this action is triggered by a press of the keyboard, then that key becomes stuck in the guest OS.