Bug 515202 - Bootloader error: No module named kudzu
Summary: Bootloader error: No module named kudzu
Keywords:
Status: CLOSED DUPLICATE of bug 497088
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-boot
Version: 11
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-03 10:27 UTC by Britta Stabenow
Modified: 2009-08-04 10:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-04 10:01:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Crashdump report for bootloader (6.63 KB, text/plain)
2009-08-03 10:28 UTC, Britta Stabenow
no flags Details

Description Britta Stabenow 2009-08-03 10:27:20 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4) Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4




Computer system (dual-boot with Windows) does not load the bootloader at start-up but boots straight into Fedora.

Trying to access the bootloader from menu System -> Administration produces the crashdump report (see attachment).

This is possibly not a Fedora bug - but I'm not sure and thought I better report it.
I had a failed/botched openSUSE install which left me unable to boot into either Windows or Linux. I installed Fedora 11 onto that same Linux partition - the installation was successful apart from the still non-functioning bootloader.





m

Reproducible: Always

Steps to Reproduce:
1. Access Bootloader from menu (System/Administration)
2. Prompt for root password - enter password and OK.
3. The crashdump report is presented.
Actual Results:  
Crashdump (attached). No access to bootloader.

Expected Results:  
Be able to run system-config-boot or point to repair options.

My first bug report - hope I've done it correctly.

Comment 1 Britta Stabenow 2009-08-03 10:28:48 UTC
Created attachment 355986 [details]
Crashdump report for bootloader

Comment 2 Britta Stabenow 2009-08-03 22:13:05 UTC
Update: I managed to boot into Windows successfully, so the bootloader is working at start-up.

Therefore it does look like a genuine bug after all: no access to system-config-boot as described above.

Comment 3 Harald Hoyer 2009-08-04 10:01:59 UTC
update your system

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


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