Bug 60347 - VNC can't be started after reboot
Summary: VNC can't be started after reboot
Keywords:
Status: CLOSED DUPLICATE of bug 58990
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: vnc
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-26 11:34 UTC by Bernd Bartmann
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-02-26 11:34:39 UTC
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.