Bug 183532

Summary: GRUB error and anacdump supplied
Product: [Fedora] Fedora Reporter: Steve freemantle <steve>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: stelian
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-03 01:30:47 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
Failure - dump from PC when installing Software none

Description Steve freemantle 2006-03-01 20:13:05 UTC 
Description of problem:
Whilst installing Fedora core 4, please note I was overwriting SUSE 10 the 
installation failed and advised I collect the DUMP file (anacdump) and send it 
to redhat bugzilla. Please note the machine was dual boot Windows XP and SUSE 
10 originally - I also have a GRUB loading stage 1.5 ERROR 17. The PC is 
currently unusable.
Version-Release number of selected component (if applicable):Fedora core 4


How reproducible:GRUB error every time


Steps to Reproduce:
1.Boot the machine the GRUB error occurs - I think the GRUB error is as a 
result of software load failure.
2.
3.
  
Actual results:


Expected results:


Additional info:File attached with the DUMP
Comment 1 Steve freemantle 2006-03-01 20:13:05 UTC 
Created attachment 125491 [details]
Failure - dump from PC when installing Software
Comment 2 Jindrich Novy 2006-03-02 12:27:40 UTC 
Please don't report python backtraces (dumps) from anaconda to a dump package.
The dump package takes care about backups and even with the best intentions I
couldn't fix a bug in anaconda in the dump package ;-)

Reassigning to anaconda component.
Comment 3 Jeremy Katz 2006-03-03 01:30:47 UTC 

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