Bug 757774

Summary: gnome-system-monitor fails to start repeatedly with a socket in /tmp
Product: Red Hat Enterprise Linux 5 Reporter: Tomas Jamrisko <tjamrisk>
Component: gnome-system-monitorAssignee: David King <dking>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.8CC: ovasik, tjamrisk
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: 2014-06-25 21:05:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tomas Jamrisko 2011-11-28 16:58:26 UTC 
Description of problem:
Connecting to a RHEL5.8 system using ssh with X forwarding, running gnome-system-monitor and terminating it results in it failing to start after starting a new session

Version-Release number of selected component (if applicable):
gnome-system-monitor-2.16.0-4.el5

How reproducible:
Always 

Steps to Reproduce:
1. ssh -Y rhel5.8 system
2. $ gnome-system-monitor
3. terminate it (ctrl+c)
4. try running and terminating a few more times (should work so far)
5. there should be a gnome-system-monitor socket in /tmp
6. $ exit (note that the ssh should hang by now and needs to be terminated)
7. reconnect to the same machine 
8. $ gnome-system-monitor (should start)
9. terminate again
10. run again
  
Actual results:
gnome-system-monitor doesn't start


Expected results:
it starts
Comment 1 RHEL Program Management 2014-03-07 13:56:21 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 3 Ondrej Vasik 2014-06-25 21:05:10 UTC 
I take it as no need to escalate - as this doesn't qualify for production phase 3, closing WONTFIX for RHEL 5, thanks for reply.