From: Launchpad Bug Tracker <1802465@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1802465] Re: typing string via VNC is unreliable
Date: Fri, 02 Jul 2021 04:17:19 -0000 [thread overview]
Message-ID: <162519944002.31921.10962672417038971301.malone@loganberry.canonical.com> (raw)
In-Reply-To: 154174980807.2749.13752196954108515323.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/1802465
Title:
typing string via VNC is unreliable
Status in QEMU:
Expired
Bug description:
QEMU version is 3.0.0
# Description
The problem is that, when typing string through VNC, it can be
unreliable -- sometimes some key strokes get skipped, sometimes get
swapped, sometimes get repeated. There's no problem when typing
through VNC on physical hardware.
# Steps to reproduce
1. Launch virtual machine by:
qemu-kvm -display vnc=:1 -m 2048 opensuse-leap-15.qcow2
2. Connect to VNC by:
vncviewer -Shared :5901
3. Simulate a series of key strokes by "vncdotool" [1]:
vncdotool -s 127.0.0.1::5901 typefile strings_to_be_typed.txt
4. Usually after a few hundred keys are typed, something goes wrong.
I attached a screenshot that it mistypes " hello" to "h ello".
[1] https://github.com/sibson/vncdotool
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1802465/+subscriptions
prev parent reply other threads:[~2021-07-02 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 7:50 [Qemu-devel] [Bug 1802465] [NEW] typing string via VNC is unreliable Zhaocong
2018-11-24 9:49 ` [Qemu-devel] [Bug 1802465] " Gao
2021-05-02 5:51 ` Thomas Huth
2021-06-18 15:38 ` Thomas Huth
2021-07-02 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=162519944002.31921.10962672417038971301.malone@loganberry.canonical.com \
--to=1802465@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 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).