From: kjonca <1618301@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1618301] Re: qemu-input: Mouse stops working in Windows guest
Date: Thu, 04 Jun 2020 07:15:10 -0000 [thread overview]
Message-ID: <159125491033.13773.15199329152668864583.malone@gac.canonical.com> (raw)
In-Reply-To: 20160830031518.12252.40741.malonedeb@chaenomeles.canonical.com
Still exists in QEMU emulator version 5.0.0 (Debian 1:5.0-5) running
on Linux 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) 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/1618301
Title:
qemu-input: Mouse stops working in Windows guest
Status in QEMU:
New
Bug description:
ROCCAT Kone XTD mouse will randomly stop working in the guest until
it's restarted. Windows Event Viewer shows an error in i8042prt, with
the message "Could not set the mouse resolution". The XML log:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="i8042prt" />
<EventID Qualifiers="49157">23</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-08-30T02:52:00.354536300Z" />
<EventRecordID>5708</EventRecordID>
<Channel>System</Channel>
<Computer>cronus</Computer>
<Security />
</System>
- <EventData>
<Data />
<Binary>000008000100000000000000170005C03205000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Host is running Linux 4.7.2 with QEMU 2.6.1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1618301/+subscriptions
next prev parent reply other threads:[~2020-06-04 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 3:15 [Qemu-devel] [Bug 1618301] [NEW] qemu-input: Mouse stops working in Windows guest nivekuil
2019-04-30 19:41 ` [Qemu-devel] [Bug 1618301] " kjonca
2020-06-04 7:15 ` kjonca [this message]
2020-09-13 6:44 ` kjonca
2020-09-16 9:55 ` kjonca
2021-05-04 8:05 ` 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=159125491033.13773.15199329152668864583.malone@gac.canonical.com \
--to=1618301@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.