From: Maxim Levitsky <mlevitsk@redhat.com>
To: Bug 1906180 <1906180@bugs.launchpad.net>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <ghoffman@redhat.com>
Subject: Re: [Bug 1906180] Re: Keyboard keys get stuck
Date: Mon, 30 Nov 2020 15:43:05 +0200 [thread overview]
Message-ID: <8e484633629fae1c7fc060ea1f4ed79eef2ac986.camel@redhat.com> (raw)
In-Reply-To: <160672375658.20924.3180698287779374632.malone@gac.canonical.com>
On Mon, 2020-11-30 at 08:09 +0000, Thomas Huth wrote:
> Which user interface do you use? SDL? GTK? VNC?
>
> ** Changed in: qemu
> Status: New => Incomplete
>
I use GTK and I have seen that exact bug for a while,
but it disappeared long time ago.
You might be unlucky to get the affected version.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2020-11-30 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 20:18 [Bug 1906180] [NEW] Keyboard keys get stuck johannes
2020-11-30 8:09 ` [Bug 1906180] " Thomas Huth
2020-11-30 13:43 ` Maxim Levitsky [this message]
2020-12-01 17:47 ` johannes
2020-12-01 18:13 ` Daniel Berrange
2020-12-02 16:31 ` johannes
2020-12-21 10:48 ` johannes
2021-02-20 4:17 ` Launchpad Bug Tracker
2021-02-28 17:43 ` johannes
2021-05-14 10:06 ` Thomas Huth
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=8e484633629fae1c7fc060ea1f4ed79eef2ac986.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=1906180@bugs.launchpad.net \
--cc=ghoffman@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).