From: Thomas Huth <1502884@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1502884] Re: Super important feature req: QEMU VNC server: Introduce a keyboard "norepeat" option!
Date: Thu, 22 Apr 2021 04:03:14 -0000 [thread overview]
Message-ID: <161906419474.6464.17809360461715014917.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20151005123157.4012.27683.malonedeb@soybean.canonical.com
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1502884
Title:
Super important feature req: QEMU VNC server: Introduce a keyboard
"norepeat" option!
Status in QEMU:
Incomplete
Bug description:
Hi,
A big issue when using QEMU's VNC server (VNC KVM) is that, when
there's a network lag, unintended keypresses go through to the QEMU
guest VM.
This is frequently "enter" keypresses, causing all kinds of unintended
consequences in the VM. So basically it's extremely dangerous.
This is because the VNC protocol's keyboard interaction is implemented
in terms of key down - key up events, making the server's keyboard
autorepeat kick in when it should not.
For this reason, it would be great if QEMU's VNC server part would be enhanced with an option such that when a VNC protocol key down is received, then locally that is treated as one single keypress only (I don't know how that should be implemented but I guess either as an immediate key down - key up sequence locally, or key down + key up after say 0.05 seconds), instead of waiting for the key up event from the VNC client.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1502884/+subscriptions
next prev parent reply other threads:[~2021-04-22 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 12:31 [Qemu-devel] [Bug 1502884] [NEW] Super important feature req: QEMU VNC server: Introduce a keyboard "norepeat" option! Mikael
2015-10-05 12:44 ` [Qemu-devel] [Bug 1502884] " Mikael
2020-09-27 15:46 ` Marcel Partap
2020-09-28 8:15 ` Daniel Berrange
2021-04-22 4:03 ` Thomas Huth [this message]
2021-06-21 4:17 ` Launchpad Bug Tracker
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=161906419474.6464.17809360461715014917.malone@chaenomeles.canonical.com \
--to=1502884@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.