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 845222 - Cursor unusable after vdagent gets killed
Summary: Cursor unusable after vdagent gets killed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Arnon Gilboa
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-02 10:45 UTC by Tomas Jamrisko
Modified: 2019-10-10 14:19 UTC (History)
7 users (show)

Fixed In Version: vdagent-win-0.1-12
Doc Type: Bug Fix
Doc Text:
Killing just the vdagent and not vdservice on a windows 7 guest resulted in the cursor being unusable.An update has been made to ensure that the vdagent starts correctly and these problems will no longer occur. As a result the guest's mouse will now respond correctly to user input.
Clone Of:
Environment:
Last Closed: 2012-12-04 18:19:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vdservice: restart vdagent if killed manually (1.45 KB, patch)
2012-09-16 11:04 UTC, Arnon Gilboa
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1502 0 normal SHIPPED_LIVE new package: spice-vdagent-win 2012-12-04 23:07:17 UTC

Description Tomas Jamrisko 2012-08-02 10:45:19 UTC
Description of problem:

Killing just vdagent and not vdservice on a windows 7 guest results in cursor being unusable.

Version-Release number of selected component (if applicable):
vdagent-win-0.1-11

How reproducible:
always 

Steps to Reproduce:
1. Make sure both vdservice and vdagent are running on your VM
2. Kill only vdagent, keep vdservice running 
  
Actual results:
Cursor is pretty much unusable (it only changes it's appearance, does not respond to clicks)

Expected results:
Service should either either start agent again or it should terminate itself (cursor falls back in that case)

Comment 1 Christophe Fergeau 2012-08-06 09:29:47 UTC
Most likely a duplicate of bug #839564. See also http://thread.gmane.org/gmane.comp.emulators.spice.devel/10410

Comment 2 Arnon Gilboa 2012-09-16 11:04:32 UTC
Created attachment 613396 [details]
vdservice: restart vdagent if killed manually

Comment 7 errata-xmlrpc 2012-12-04 18:19:07 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-2012-1502.html


Note You need to log in before you can comment on or make changes to this bug.