Bug 495367

Summary: Fedora-11-Snap1-x86_64-Live.iso - anaconda None exception report
Product: [Fedora] Fedora Reporter: Flóki Pálsson <flokip>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, pjones, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-13 14:18:44 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
Fedora-11-Snap1-x86_64-Live.iso - anaconda None exception report none

Description Flóki Pálsson 2009-04-12 12:03:07 UTC
Created attachment 339229 [details]
Fedora-11-Snap1-x86_64-Live.iso - anaconda None exception report

Description of problem:
When installing from Fedora-11-Snap1-x86_64-Live.iso then there was an error.
"anaconda None exception report ...". See attachment. -
Default settings where used except keyboard and language ( IS ).

Version-Release number of selected component (if applicable):
Fedora-11-Snap1-x86_64-Live.iso

How reproducible:
Once.
On repeated install then this error did not appear.  

Steps to Reproduce:
1.
Install from Fedora-11-Snap1-x86_64-Live.iso 
2.
3.
  
Actual results:
Error offering to post to bugzilla.  

Expected results:
Install of F11

Additional info:
Error was saved using gmail. 

In fdisk - l report there is a warning
"Partition 1 does not end on cylinder boundary."
on /dev/sdc1  which is install partition. 
See in bottom of atthachment. 

On second and third install then this error does not show up,
install finish, but when rebooting then booting sops in grub.

Comment 1 Chris Lumens 2009-04-13 14:18:44 UTC

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