Bug 694961

Summary: Installer will not continue, presents error message
Product: [Fedora] Fedora Reporter: Chris Jones <foxmulder881>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-11 10:32:55 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Chris Jones 2011-04-09 03:07:16 EDT
Description of problem:

Upon attempting to install Fedora 15, anaconda presents me with an error message.

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

How reproducible:

I could reproduce this error message each and every time on launch and use of anaconda installer.

Steps to Reproduce:
1. Launch anaconda
2. Attempt F15 install with anaconda
Actual results:

I get the following error message. See error message here: http://pastebin.com/chZ8J2mk

Expected results:

I expected to be able to install Fedora 15 for early testing.

Additional info:
Comment 1 Chris Lumens 2011-04-11 10:30:18 EDT
anaconda 15.27 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/account_gui.py", line 91, in setCapsLockLabel
    if _isys.isCapsLockEnabled():
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/account_gui.py", line 72, in getScreen
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1338, in setScreen
    new_screen = self.currentWindow.getScreen(anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1258, in nextClicked
    self.setScreen ()
RuntimeError: XOpenDisplay failed
Comment 2 Chris Lumens 2011-04-11 10:32:55 EDT

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