From: Frederick Metzengerstein <merak@quantentunnel.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1828272] [NEW] 4.0 breaks keyboard autorepeat in guests with xserver
Date: Wed, 08 May 2019 17:47:22 -0000 [thread overview]
Message-ID: <155733764243.16739.6026352756192984678.malonedeb@gac.canonical.com> (raw)
Public bug reported:
Description:
In a linux/bsd guest within X, pressing and holding a key for a short time causes an endless repeat of that key in the guest. The release of the key gets ignored.
Example 1: pressing and holding 'a' for a few seconds results in typing of 'aaaaaaaaaaaa...' endlessly.
Example 2: pressing and holding 'Backspace' for a few seconds results in deleting all your previously typed text.
It doesn't happen within a VT in the guest. It also doesn't happen with
guests that run windows, reactos or haiku for example.
The problem goes away, when disabling xorgs autorepeat function via "xset -r" in the host.
Normally, this setting should not have any effect on the guest, since it has it's own autorepeat setting. So there is some conflict here.
Steps to reproduce:
Start any linux/bsd guest system with xserver, open a terminal, press and hold a key for a short time: Look how it gets typed endlessly (Try a few times if it doesn't happen immediately).
The easiest way is to run a linux live cd, like this (Link to example iso :http://download.grml.org/grml64-full_2018.12.iso)
$ qemu-system-x86_64 -enable-kvm -m 512 -net none -boot d -cdrom grml64-full_2018.12.iso
Qemu version info:
QEMU emulator version 4.0.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
System info:
Linux **** 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux
** Affects: qemu
Importance: Undecided
Status: New
** Description changed:
Description:
In a linux/bsd guest within X, pressing and holding a key for a short time causes an endless repeat of that key in the guest. The release of the key gets ignored.
Example 1: pressing and holding 'a' for a few seconds results in typing of 'aaaaaaaaaaaa...' endlessly.
Example 2: pressing and holding 'Backspace' for a few seconds results in deleting all your previously typed text.
It doesn't happen within a VT in the guest. It also doesn't happen with
guests that run windows, reactos or haiku for example.
The problem goes away, when disabling xorgs autorepeat function via "xset -r" in the host.
Normally, this setting should not have any effect on the guest, since it has it's own autorepeat setting. So there is some conflict here.
Steps to reproduce:
Start any linux/bsd guest system with xserver, open a terminal, press and hold a key for a short time: Look how it gets typed endlessly (Try a few times if it doesn't happen immediately).
The easiest way is to run a linux live cd, like this (Link to example iso :http://download.grml.org/grml64-full_2018.12.iso)
$ qemu-system-x86_64 -enable-kvm -m 512 -boot d -cdrom grml64-full_2018.12.iso
-
Qemu version info:
QEMU emulator version 4.0.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
+
+ System info:
+ Linux **** 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828272
Title:
4.0 breaks keyboard autorepeat in guests with xserver
Status in QEMU:
New
Bug description:
Description:
In a linux/bsd guest within X, pressing and holding a key for a short time causes an endless repeat of that key in the guest. The release of the key gets ignored.
Example 1: pressing and holding 'a' for a few seconds results in typing of 'aaaaaaaaaaaa...' endlessly.
Example 2: pressing and holding 'Backspace' for a few seconds results in deleting all your previously typed text.
It doesn't happen within a VT in the guest. It also doesn't happen
with guests that run windows, reactos or haiku for example.
The problem goes away, when disabling xorgs autorepeat function via "xset -r" in the host.
Normally, this setting should not have any effect on the guest, since it has it's own autorepeat setting. So there is some conflict here.
Steps to reproduce:
Start any linux/bsd guest system with xserver, open a terminal, press and hold a key for a short time: Look how it gets typed endlessly (Try a few times if it doesn't happen immediately).
The easiest way is to run a linux live cd, like this (Link to example iso :http://download.grml.org/grml64-full_2018.12.iso)
$ qemu-system-x86_64 -enable-kvm -m 512 -net none -boot d -cdrom grml64-full_2018.12.iso
Qemu version info:
QEMU emulator version 4.0.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
System info:
Linux **** 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1828272/+subscriptions
next reply other threads:[~2019-05-08 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 17:47 Frederick Metzengerstein [this message]
2019-05-08 17:54 ` [Qemu-devel] [Bug 1828272] Re: 4.0 breaks keyboard autorepeat in guests with xserver Frederick Metzengerstein
2019-05-08 18:01 ` Frederick Metzengerstein
2019-05-09 9:41 ` Daniel Berrange
2019-08-15 18:43 ` 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=155733764243.16739.6026352756192984678.malonedeb@gac.canonical.com \
--to=merak@quantentunnel.de \
--cc=1828272@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).