Bug 718511

Summary: vncserver fails to start after reboot following a forced powerdown
Product: [Fedora] Fedora Reporter: redhatbug <mjmccaffrey>
Component: tigervncAssignee: Orphan Owner <extras-orphan>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: atkac, extras-orphan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 12:13:04 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description redhatbug 2011-07-03 14:36:16 EDT
Description of problem:
If a machine acting as a vncserver has to be shutdown in a disorderly manner (e.g. by switching off the power after a hang or crash) then when the machine is rebooted the vncserver fails to start.

I think this is the same problem as discussed here:
       http://forums.fedoraforum.org/showthread.php?t=264147
(I do not think the proposed fix at the end of these posts is correct)

The vncserver can be made to start again by logging into the vncserver machine after reboot, deleting the relevant socket (in my case X2) in /tmp/.X11-unix, and then starting/restarting the vncserver (which ofcourse creates a new socket)

Shouldn't the vncserver restart regardless (within reason) of how orderly or disorderly the shutdown of the machine running the vncserver? 

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

tigervnc-1.0.90-4.fc15.x86_64
tigervnc-license-1.0.90-4.fc15.noarch
tigervnc-server-module-1.0.90-4.fc15.x86_64
tigervnc-server-minimal-1.0.90-4.fc15.x86_64
tigervnc-server-1.0.90-4.fc15.x86_64

How reproducible:
Every time vncserver machine is shut down in a disorderly manner

Steps to Reproduce:
1. On a machine configured to run a vncserver on boot switch the power off while it is up and running

2. Switch on the machine running the server and wait until it has booted

3. Login and run "systemctl status vncserver.service". Systemctl will advise that it has failed as indeed it has.
  
Actual results:
vncserver does not start at boot

Expected results:
vncserver starts at boot

Additional info:
Comment 1 Fedora End Of Life 2012-08-07 12:13:06 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping