It's kind of our own fault that we didn't ask for those sorts of details in that error message. I think that a lot of the time it was reported without necessarily meaning that any interesting keys weren't being handled correctly.
In any case, as of commit 2ec78706d188 that message has been removed, so the 2.12 release should fix this, or at least not produce unhelpful warnings :-)
It's kind of our own fault that we didn't ask for those sorts of details in that error message. I think that a lot of the time it was reported without necessarily meaning that any interesting keys weren't being handled correctly. In any case, as of commit 2ec78706d188 that message has been removed, so the 2.12 release should fix this, or at least not produce unhelpful warnings :-)
Yes, if you get the same situation in 2.12, it will now print a much better mesage:
- Which version of QEMU are you using? - Which keyboard layout do you have on your physical keyboard? - Which key did you press to get that message? - Which user interface of QEMU are you using (GTK, SDL1.2, SDL2 or VNC)?
FYI, offlist we determined that it was QEMU 2.10 displaying over ssh on XQuartz display server. This is known to be broken because QEMU historically only understands the Linux evdev & kbd keycode mappings.
QEMU 2.12 is much improved with explicit support for XQuartz and XWin, so hopefully the problem will be solved for this particular case.