Bug 495367 - Fedora-11-Snap1-x86_64-Live.iso - anaconda None exception report
Summary: Fedora-11-Snap1-x86_64-Live.iso - anaconda None exception report
Keywords:
Status: CLOSED DUPLICATE of bug 495144
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-12 12:03 UTC by Flóki Pálsson
Modified: 2009-04-13 14:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-13 14:18:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Fedora-11-Snap1-x86_64-Live.iso - anaconda None exception report (151.15 KB, text/plain)
2009-04-12 12:03 UTC, Flóki Pálsson
no flags Details

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 ***


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