Bug 60347

Summary:	VNC can't be started after reboot
Product:	[Retired] Red Hat Linux	Reporter:	Bernd Bartmann <bernd.bartmann>
Component:	vnc	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED DUPLICATE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-02-26 11:34:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bernd Bartmann 2002-02-26 11:34:35 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
When doing a "reboot" when VNC is running, /tmp/.X11-unix/X1 is not deleted and 
so when the system comes up again I get an error saying that VNC can't be 
started. The init scripts should remove the stale X11 socket .

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. service vncserver start
2. reboot or poweroff
3. watch the boot messages
	

Additional info:

Comment 1 Tim Waugh 2002-02-26 12:01:57 UTC


*** This bug has been marked as a duplicate of 58990 ***