Have experienced the same thing just now with Hardy and VMWare Workstation 6.0.3. The setxkbmap command fixed the problem for me. Is there a way to dump out the currently active X keyboard map? A before-and-after comparison might help figure out what's breaking.
Have experienced the same thing just now with Hardy and VMWare Workstation 6.0.3. The setxkbmap command fixed the problem for me. Is there a way to dump out the currently active X keyboard map? A before-and-after comparison might help figure out what's breaking.