Bug 1000943

Summary: Run "subscription-manager-gui" twice quickly will launch two subscription-manager-gui window.
Product: Red Hat Enterprise Linux 5 Reporter: xingge <gxing>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED WONTFIX QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.10CC: ckozak, jsefler, ldai, liliu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-26 13:45:28 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:
Attachments:
Description Flags
the two gui window none

Description xingge 2013-08-26 07:31:24 UTC
Created attachment 790316 [details]
the two gui window

Description of problem:
Run "subscription-manager-gui" twice quickly will launch two subscription-manager-gui window.

Version-Release number of selected component (if applicable):
subscription-manager-gui-1.8.21-1.el5
subscription-manager-firstboot-1.8.21-1.el5
subscription-manager-1.8.21-1.el5
python-rhsm-1.8.17-1.el5

How reproducible:
always

Steps to Reproduce:
1.Open two CLI window and type cmd 
#subscription-manager-gui
2.quickly execute both cmd in the two CLI window


Actual results:
Two subscription-manager-gui window will show. Please see the attachment.

Expected results:
Only one window should show and the other should say
"subscription-manager-gui is already running"

Additional info:
If I execute the cmd "subscription-manager-gui" once and wait untill the GUI window shows then run the cmd "subscription-manager-gui" in another CLI window, the result is right no more GUI window would show.

Comment 1 Carter Kozak 2013-08-26 13:45:28 UTC
They must be opened < .25 seconds or so apart.  If two gui windows do open, they will mirror certificates within 2 seconds of a certificate change (register/attach/remove), so I don't think this is a problem.