Control: tag -1 + upstream confirmed Control: forwarded -1 https://bugs.launchpad.net/qemu/+bug/1038136 Control: severity -1 normal Control: found -1 1.1.2+dfsg-1
06.12.2014 21:04, R. Lemos wrote: > Package: qemu > Version: 2.1+dfsg-7+b1 > Severity: important > > Dear Maintainer, > > when host X Window System is configured for ABNT2 keyboard layout (gnome > says just "Portuguese (Brazil)", but Xorg.0.log outputs: rules: evdev, > model: pc105, layout: br, variant: abnt2) qemu simply does not recognize > a single key, right of AltGr (which happens to be the right Alt), that > displays three symbols: / (slash), ? (question mark) and ° (degree). > > Since this key is the only one with a slash, it is virtually impossible > to use linux console inside qemu running on these hosts. What way do you use to iteract with qemu guest console? Is it some sort of vnc client, or sdl directly on X window, or something else? As long as I understand, "proper" VNC client should not have any probs with keyboard at all, sending just the keycodes to the VNC server without any need to translate them or to use any keymaps etc. There was a good writeup about this, but I can't find it right now, will try to add an url when/if I'll find it. Now, I've no idea really how keyboard mapping works in qemu, so the info you provided is of no use to me. Instead, that info might be better added to the original launchpad bugreport -- I wont be able to do anything besides whatever upstream will do. Speaking of the patch you mentioned in the other email, ofcourse it is not acceptable since it will break keyboard for everyone else. Thanks, and please excuse me for being unconstructive. Adding tags and setting appropriate level of priority. Thanks, /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
