Summary: | VMware does not intercept ctrl sequences, CTRL C in guest kills host X server | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johan Bondeson <johan> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Johan Bondeson
2008-12-31 13:26:11 UTC
Simple question: does Ctrl-C do that even outside of VMware ? As for "can't login after restart", it may be caused by 'Option "AutoAddDevices" "off"'. In short, I suspect a configuration problem. Nope, in X on the host, CTRL combinations is sent to the window that has input focus. That is the thing that surprises me, that the keystrokes to the guest are sent to some terminal that owns the xserver (startx?) process. Otherwise I suppose it would not behave that way. Or would it? As of config issues, none of that was changed when the error first occured, so it seems a bit odd it would be something in that area. The "AutoAddDevices off" was there because of HAL misbehaving severly, but I disabled it entirely instead so I'll remove this flag. IIRC, hal was never misbehaving, just people failed to properly configure things in it. I never used VMware, so I can't really compare with my own experiences. xorg-server 1.5.3 should properly set the console in raw mode (whatever that means - just quoting from the sources), which should disable Ctrl-C affecting the sever. It does for me, but again, that should be for all of the apps, maybe VMware does something that confuses the server. Ok, I emerged the 6.5.1 workstation, and now it works again... Thanks for the comments, though. |