RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 725734 - Spice vdagent: cannot move the mouse after leaving alone the spice window for a while
Summary: Spice vdagent: cannot move the mouse after leaving alone the spice window for...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Arnon Gilboa
QA Contact: Desktop QE
URL:
Whiteboard:
: 727349 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-26 12:26 UTC by Golita Yue
Modified: 2019-10-10 14:20 UTC (History)
13 users (show)

Fixed In Version: vdagent-win-0.1-8
Doc Type: Bug Fix
Doc Text:
Previously, if you were running the SPICE agent on Windows guests and left the SPICE session idle, the mouse would become unavailable because the driver would complete pending read operations, which resulted in error codes that made the agent hang. The agent has been updated to ignore these particular error codes and the mouse now behaves as expected.
Clone Of:
Environment:
Last Closed: 2011-12-15 15:37:03 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1818 0 normal SHIPPED_LIVE Windows Guest Tools bug fix and enhancement update 2011-12-15 20:35:23 UTC

Description Golita Yue 2011-07-26 12:26:12 UTC 
Description of problem:
The mouse has not reaction when put the spice window stay away about 30 secs.
At the same time, the keyboard are available.

When you first boot up the vm, the mouse are available.
If you always move the mouse or click the mouse from beginning, the mouse will available. But once you do other work and leave alone the spice window for a while, then use mouse to click inside guest and the mouse has not any reaction.
 
Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-13
(https://brewweb.devel.redhat.com/buildinfo?buildID=173687)
vdagent-win-0.1-7
(https://brewweb.devel.redhat.com/buildinfo?buildID=173451)
qxl driver:  1.0.46561.0
(used the rhel5 release driver)
driver date: 7/1/2010

How reproducible:
100%

Steps to Reproduce:
1. boot up vm with cmd
2. install qxl driver, vdagent-win, virtio-serial driver in guest
3. leave alone the spice window for 30 secs
  
Actual results:
the mouse has reaction

Expected results:
can not move or click mouse in guest, the mouse has not reaction. 
but keyboard is available.

Additional info:
cmd:
qemu-kvm  -m 2G -smp 2 -drive file=kvm_autotest_root/images/winXP-32-virtio.raw,if=none,id=test,cache=none,format=raw -device virtio-blk-pci,drive=test -cpu qemu64,+sse2,+x2apic -boot c -netdev tap,id=idfBjQau,vhost=on,ifname='t0-142230-puVQ',script='/etc/qemu-ifup',downscript='no' -device virtio-net-pci,netdev=idfBjQau,mac=9a:3b:07:97:db:16,id=ndev00idfBjQau,bus=pci.0,addr=0x4  -spice port=5930,disable-ticketing -vga qxl -monitor stdio -device virtio-serial-pci,id=virtio-serial1 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial1.0,nr=3,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -usb
Comment 2 Marian Krcmarik 2011-07-26 13:23:59 UTC 
I've reproduced that on Win7 guest with:
virtio-win-prewhql-0.1-13
vdagent-win-0.1-7
qxl-win-0.1-7

This occurs in 0.1-13 and 0.1-12 serial driver in my case. I did not observer that with 0.1-11 earlier.

I can see cursor mostly but I am not able to click.
Comment 3 Marian Krcmarik 2011-07-29 17:27:10 UTC 
Reproduced in situation:
Virtio-serial 0.1-13 + QXL driver

Not reproduced in situation:
Virtio-serial 0.1-13 + VGA driver
Virtio-serial 0.1-11 + QXL driver
Comment 8 Arnon Gilboa 2011-08-01 10:18:46 UTC 
Spice Windows guest agent fixed accordingly, in vdagent-win-0.1-8.
Comment 9 Golita Yue 2011-08-01 11:08:48 UTC 
Tested with vdagent-win-0.1-8, passed. 
So verified in vdagent-win-0.1-8.
Comment 10 Miya Chen 2011-08-02 02:41:18 UTC 
(In reply to comment #9)
> Tested with vdagent-win-0.1-8, passed. 
> So verified in vdagent-win-0.1-8.

set this bug back to ON_QA as desktop_qa is accountable for the verification and needs to do acceptance testing and regression testing for it.
Comment 11 Arnon Gilboa 2011-08-02 06:56:09 UTC 
*** Bug 727349 has been marked as a duplicate of this bug. ***
Comment 12 Marian Krcmarik 2011-08-03 14:32:30 UTC 
Verified on rhev-guest-tools-iso-3.0-10.noarch.rpm which includes vdagent-win-0.1-8.
Comment 13 Kate Grainger 2011-12-12 01:06:58 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, if you were running the SPICE agent on Windows guests and left the SPICE session idle, the mouse would become unavailable because the driver would complete pending read operations, which resulted in error codes that made the agent hang. The agent has been updated to ignore these particular error codes and the mouse now behaves as expected.
Comment 14 errata-xmlrpc 2011-12-15 15:37:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1818.html
Note You need to log in before you can comment on or make changes to this bug.