From: "Daniel P. Berrangé" <berrange@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] 07333e1ca (kbd-state: use state tracker for sdl2) breaks keyboard input
Date: Wed, 6 Feb 2019 17:31:57 +0000 [thread overview]
Message-ID: <20190206173157.GB12331@redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1902061736310.58711@zero.eik.bme.hu>
On Wed, Feb 06, 2019 at 05:41:22PM +0100, BALATON Zoltan wrote:
> Hello,
>
> The commit 07333e1ca breaks keyboard input in bios console with SDL2 UI. To
> reproduce: start qemu-system-i386 without any options, press Ctrl-B when
> prompted to get an IPXE command line and type. Key presses are doubled.
This isn't related to the IPXE BIOS - it is broken in general in fact.
Enabling tracing shows that all the input events are doubled up
all the time, before we even get into IPXE BIOS
$ ./x86_64-softmmu/qemu-system-x86_64 -display sdl -d trace:input*
17197@1549474207.037592:input_event_key_qcode con 0, key qcode f, down 1
17197@1549474207.037662:input_event_sync
17197@1549474207.037680:input_event_key_qcode con 0, key qcode f, down 1
17197@1549474207.037706:input_event_sync
17197@1549474207.145514:input_event_key_qcode con 0, key qcode f, down 0
17197@1549474207.145542:input_event_sync
17197@1549474207.145548:input_event_key_qcode con 0, key qcode f, down 0
17197@1549474207.145552:input_event_sync
17197@1549474208.477246:input_event_key_qcode con 0, key qcode f, down 1
17197@1549474208.477294:input_event_sync
17197@1549474208.477299:input_event_key_qcode con 0, key qcode f, down 1
17197@1549474208.477301:input_event_sync
17197@1549474208.547471:input_event_key_qcode con 0, key qcode f, down 0
17197@1549474208.547503:input_event_sync
17197@1549474208.547509:input_event_key_qcode con 0, key qcode f, down 0
> (Besides this the output window mixup when something is output to serial
> window I've reported earlier is still present. I'd appreciate if these could
> be fixed now that the working SDL1 alternative was completely removed.)
AFAIR, we determined there was something related to the nvidia binary
only drivers that was breaking this and needed to know if using nouveau
drivers would fix it.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-02-06 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 16:41 [Qemu-devel] 07333e1ca (kbd-state: use state tracker for sdl2) breaks keyboard input BALATON Zoltan
2019-02-06 17:31 ` Daniel P. Berrangé [this message]
2019-02-06 18:15 ` BALATON Zoltan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190206173157.GB12331@redhat.com \
--to=berrange@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).