Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230745 - new install stalling at "installing kernel-2.6.20-1.2949.fc7.x86_64"
Summary: new install stalling at "installing kernel-2.6.20-1.2949.fc7.x86_64"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-03-02 17:09 UTC by ericm24x7
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-02 17:38:18 UTC


Attachments (Terms of Use)
syslog (deleted)
2007-03-02 17:09 UTC, ericm24x7
no flags Details
anaconda log (deleted)
2007-03-02 17:10 UTC, ericm24x7
no flags Details
vncserver log (deleted)
2007-03-02 17:11 UTC, ericm24x7
no flags Details

Description ericm24x7 2007-03-02 17:09:51 UTC
Description of problem:
During fresh vnc install, the process stall at 
"Installing kernel-2.6.20-1.2949.fc7.x86_64"

Version-Release number of selected component (if applicable):
anaconda-11.2.0.27-1.x86_64

How reproducible:
persistent

Steps to Reproduce:
1. start fresh vnc install
2. select default packages
  
Actual results:
the process stop at installing kernel module/package

Expected results:
should process without stalling

Additional info:
attached files: syslog, anaconda.log, vncserver.log

Comment 1 ericm24x7 2007-03-02 17:09:51 UTC
Created attachment 149133 [details]
syslog

Comment 2 ericm24x7 2007-03-02 17:10:59 UTC
Created attachment 149134 [details]
anaconda log

Comment 3 ericm24x7 2007-03-02 17:11:29 UTC
Created attachment 149135 [details]
vncserver log

Comment 4 ericm24x7 2007-03-02 17:38:18 UTC
The latest development build (dated 3.2.07) seem to fix the problem. 


Note You need to log in before you can comment on or make changes to this bug.