<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Spice stops processing mouse input when in relative mode"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103226">103226</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Spice stops processing mouse input when in relative mode
</td>
</tr>
<tr>
<th>Product</th>
<td>Spice
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>server
</td>
</tr>
<tr>
<th>Assignee</th>
<td>spice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>geoff@hostfission.com
</td>
</tr></table>
<p>
<div>
<pre>I am writing a spice client from scratch that only connects to the main and
input channels for sending mouse and keyboard events.
I have discovered two issues with spice/qemu and a Windows 10 guest.
1) If the tablet and mouse are attached and SPICE_MOUSE_MODE_SERVER is in use,
sending SPICE_MSGC_INPUTS_MOUSE_PRESS performs it at the location of the tablet
rather then the location of the cursor, causing the cursor to jump back to it's
original location.
2) If SPICE_MOUSE_MODE_CLIENT is in use, applications that need relative input
event's do not work properly, first person games for example only allow a 180
degree turn due to the cursor hitting the x/y bounds.
After removing the tablet and setting to SPICE_MOUSE_MODE_SERVER both 1 & 2 are
worked around, but this exposes what looks like a more major bug in Spice or
qemu, I am not sure where the fault lies.
3) With SPICE_MOUSE_MODE_SERVER, only a generic mouse attached, if the mouse is
moved around and SPICE_MSGC_INPUTS_KEY_DOWN/UP messages are sent, the guest
cursor quickly stops responding and never recovers.
It seems spice-server continues to perform properly as it continues to send
SPICE_MSG_INPUTS_MOUSE_MOTION_ACK every 4 mouse messages, and keyboard events
continue to function properly. This indicates it is not a problem with my
client, but a failure between spice-server and qemu.
I will continue to dig into qemu/spice to try to discover what is broken here,
but it would be great if someone with more experience with spice could have a
look too.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>