From: Launchpad Bug Tracker <1605045@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1605045] Re: input-linux enter key stuck and/or broken
Date: Sun, 10 Jan 2021 04:17:26 -0000 [thread overview]
Message-ID: <161025224651.18863.14459650132835943781.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20160721033517.413.34124.malonedeb@gac.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1605045
Title:
input-linux enter key stuck and/or broken
Status in QEMU:
Expired
Bug description:
Using new input-linux evdev passthrough feature of qemu (qemu 2.6.0)
causes enter key to be stuck down after executing a shell script to
launch qemu guest, resulting in repeated new lines in terminal. After
a certain point of guest boot, the enter key is no longer pressed.
However, at least under Gnome on Wayland, when pressing both
left+right Ctrl keys to return keyboard back to the host, the enter
key no longer functions. The enter key continues to function when
control is under the guest, but never returns to functionality in the
host until a reboot is performed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1605045/+subscriptions
prev parent reply other threads:[~2021-01-10 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 3:35 [Qemu-devel] [Bug 1605045] [NEW] input-linux enter key stuck and/or broken mutedbytes
2016-07-21 3:38 ` [Qemu-devel] [Bug 1605045] " mutedbytes
2016-07-21 3:41 ` mutedbytes
2016-08-22 14:11 ` nivekuil
2020-11-10 14:44 ` Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker [this message]
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=161025224651.18863.14459650132835943781.malone@loganberry.canonical.com \
--to=1605045@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.