Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 563954

Summary: Liveinst doesn't start
Product: [Fedora] Fedora Reporter: Radek Novacek <rnovacek>
Component: anacondaAssignee: Ales Kozumplik <akozumpl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: jonathan, jzeleny, ovasik, vanmeeuwen+fedora
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: 2010-02-11 16:41:04 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:
Attachments:
Description Flags
Traceback none

Description Radek Novacek 2010-02-11 16:21:26 UTC
Created attachment 390289 [details]
Traceback

Description of problem:
Liveinst doesn't start. It only throws Python traceback.

Version-Release number of selected component (if applicable):
KDE live snapshot - kde-i386-20100209.16.iso
Runned from VirtualBox OSE
Anaconda 13.25-1.fc13.i686

How reproducible:
Just run livecd and hit the button on the desktop.

Actual results:
Nothing happened (traceback when runned from terminal).

Expected results:
Live installer started.

Additional info:
Tried both as liveuser and root.

Comment 1 Radek Novacek 2010-02-11 16:41:04 UTC
This problem was caused by bug #563348. rsyslog failed to start and anaconda can't connect to it. With new version of rsyslog it liveinst works. So closing NOT-A-BUG.

Comment 2 Chris Lumens 2010-02-12 00:46:12 UTC

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