Michael Thayer <michael.tha...@oracle.com> writes: > Otherwise the traditional method to fix that, if that is really the > problem, is to ssh in and to kill things until the keyboard comes back. > You could begin with "VBoxClient" processes to establish from the > start whether we are to blame or not!
Thanks for the links... Just barely looked at the first so far... very neat, what ever that software is that makes X-server reveal all that stuff.... This is just a note and there will be a fuller response after I get some sleep. Just wanted to let you know that I did ssh in and kill everything to do with VboxClient. Then shut down the services with vbox in there name: vboxserver and vboxmslnk. And I've still got no keyboard.... so I guess vbox is not the villain after all. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
