Indeed the bug does not exist in this exact form any more, but it seems the stray '86' keymap entry *does* still cause problems in current qemu in one specific case:
basically, if using 'usb-kbd', we still get trouble when openQA (os-autoinst) tries to type a '<' character, because it does this:
shift down
comma down
shift up
comma up
(note it does *not* do shift down, comma down, comma up, shift up), and qemu gets confused and converts that into this sequence of input_event_key_qcode events:
shift down
comma down
shift up
less up
and that seems to mess with the key state and cause any subsequent attempts to type a '<' to go wrong.
Indeed the bug does not exist in this exact form any more, but it seems the stray '86' keymap entry *does* still cause problems in current qemu in one specific case:
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1658676
basically, if using 'usb-kbd', we still get trouble when openQA (os-autoinst) tries to type a '<' character, because it does this:
shift down
comma down
shift up
comma up
(note it does *not* do shift down, comma down, comma up, shift up), and qemu gets confused and converts that into this sequence of input_event_ key_qcode events:
shift down
comma down
shift up
less up
and that seems to mess with the key state and cause any subsequent attempts to type a '<' to go wrong.
Removing the '86' key definition avoids the bug.