Gaetano Sferra wrote: > So nobody have ideas on how to solve the keyboard problem? > I'm looking and seeking into the user's forum, there are similar > questions but there aren't replies...
Hi, I am having sort of similar problems with the keymapping. Rather than coming up with an answer, I like to add my own remarks, maybe they are related: First, I want to make it clear I don't have knowledge of the keyboard mapping process in VNC client/server communication. If I write nonsense here, please correct me... When I run qemu-0.8.2 with the VNC server enabled and then connecting to my QEMU's VNC server on a PC with a dutch keyboard layout, there is no way I can get the keyboard to function 100% correct. Normally, when I use a vnc client to connect to any "normal" VNC server like the one from RealVNC, it does not matter if I run the vncclient with a dutch or a US keyboard, the keypresses are correctly translated. But with the QEMU's built-in VNC server (as opposed to the now-gone RFB patch from Johannes Schindelin which worked fine for me) some keys work, some don't give any output at all, and others print incorrect characters. This is when I add "-k nl". Things get a little better when I also "loadkeys nl.map" on the QEMU guest but still the result is not at all 100% OK. Without the "-k" option (thus reverting to the default en-us) I get other combinations of keys that work/print incorrect chars/don't output at all, still not 100% correct. Are other people with international keyboards having these issues as well? What is the difference with the old RFB patch that the currently built-in VNC server handles differently? Eric -- Eric Hameleers _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
