From: johannes <1906180@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1906180] Re: Keyboard keys get stuck
Date: Sun, 28 Feb 2021 17:43:30 -0000 [thread overview]
Message-ID: <161453421060.18329.4040652877155199721.malone@soybean.canonical.com> (raw)
In-Reply-To: 160668110894.7596.13290289019242660849.malonedeb@soybean.canonical.com
This might be less common in 5.2.0 but I have still had some strange
issues with keyboard.
** Changed in: qemu
Status: Expired => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1906180
Title:
Keyboard keys get stuck
Status in QEMU:
New
Bug description:
Keyboard keys get "stuck" quite often, on certain Linux guests at
least, and start repeating themselves until another key is pressed.
This is especially noticeable with key combinations like Ctrl+V for
pasting. When it happens, you get the pasted text and
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv...
This bug has been present for quite some time but I don't remember any
specific version that had it first.
QEMU version: 5.1.0
Guest: Debian stable 64-bit (live), with Gnome desktop (may occur with other Linux guests too)
Host: Arch Linux with KDE desktop (X11, wayland not tested); both default and hardened kernel tested
QEMU start command:
qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom debian.iso -boot d -vga std
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1906180/+subscriptions
next prev parent reply other threads:[~2021-02-28 17:53 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
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 [this message]
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=161453421060.18329.4040652877155199721.malone@soybean.canonical.com \
--to=1906180@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.