Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 868254

Summary: vdagent-win exits if two users are logged in simultaneously
Product: Red Hat Enterprise Linux 8 Reporter: David Jaša <djasa>
Component: spice-vdagent-winAssignee: Arnon Gilboa <agilboa>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: ---CC: cfergeau, dblechte, dyasny, italkohe, jbiddle, mbarta
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdagent-win-0.1-15 Doc Type: Bug Fix
Doc Text:
Previously, when a second user logged into a Windows guest, the RHEV SPICE Agent service terminated the previous vdagent instance, but mistakenly also the newly created vdagent on the current active session. Now, the vdagent termination event is reset after previous agent termination, so each new agent is no longer terminated.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-10 20:26:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
on XP, set process handle for vdagent launched on session>0
none
vdagent log for windows 7 guest
none
vdservice log for Windows 7 guest
none
vdservice: reset vdagent stop event after wait for termination none

Description David Jaša 2012-10-19 10:55:11 UTC 
Description of problem:
vdagent-win exits if two users are logged in simultaneously

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

How reproducible:
always

Steps to Reproduce:
1. log in to windows
2. use "switch user" feature and log in as another user
3.
  
Actual results:
agent features stop working for both accounts

Expected results:
the active user is able to use agent features

Additional info:
tested just on XP guest
Comment 1 Arnon Gilboa 2012-11-25 15:08:02 UTC 
Created attachment 651552 [details]
on XP, set process handle for vdagent launched on session>0
Comment 3 Milan Barta 2013-02-21 15:15:35 UTC 
This bug is fixed for Windows XP in vdagent-win-0.1-14, however for Windows 7 guest, this fix has introduced a very similar issue. 

Basically the steps to reproduce are the same as above plus one more user switch back to user one. With this done, the vdagent goes into a loop of switching off and on, eventually staying off (see logs attached).

With vdagent-win-0.1.12 or 0.1.13 no such behaviour could be reproduced (Win7 guest).

Switching the bug back to Assigned as this seems to be a regression.
Comment 4 Milan Barta 2013-02-21 15:16:27 UTC 
Created attachment 700597 [details]
vdagent log for windows 7 guest
Comment 5 Milan Barta 2013-02-21 15:17:08 UTC 
Created attachment 700598 [details]
vdservice log for Windows 7 guest
Comment 6 Arnon Gilboa 2013-02-26 09:49:40 UTC 
(In reply to comment #3)
> This bug is fixed for Windows XP in vdagent-win-0.1-14, however for Windows
> 7 guest, this fix has introduced a very similar issue. 
> 
> Basically the steps to reproduce are the same as above plus one more user
> switch back to user one. With this done, the vdagent goes into a loop of
> switching off and on, eventually staying off (see logs attached).
> 
> With vdagent-win-0.1.12 or 0.1.13 no such behaviour could be reproduced
> (Win7 guest).
> 
> Switching the bug back to Assigned as this seems to be a regression.

Thanks Milan. Sure it's a regression. Working on a patch.
Comment 7 Arnon Gilboa 2013-02-26 15:57:19 UTC 
Created attachment 702992 [details]
vdservice: reset vdagent stop event after wait for termination
Comment 10 Marian Krcmarik 2013-03-17 21:52:23 UTC 
*** Bug 922421 has been marked as a duplicate of this bug. ***
Comment 14 errata-xmlrpc 2013-06-10 20:26:38 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/RHSA-2013-0924.html