Bug 759296 - Crash when upgrading from Fedora 15 to 16
Summary: Crash when upgrading from Fedora 15 to 16
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-01 22:54 UTC by neopium
Modified: 2012-11-30 03:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-30 03:19:04 UTC
Type: ---


Attachments (Terms of Use)
Bug report (54.36 KB, application/x-gzip)
2011-12-01 22:54 UTC, neopium
no flags Details

Description neopium 2011-12-01 22:54:06 UTC
Created attachment 539420 [details]
Bug report

Description of problem:
I upgraded with preupgrade from F15 to F16.
When restarting with anaconda, everything went well until it cleaned the packages. Then it crashed (see report attached

Version-Release number of selected component (if applicable):
Fedora 16

How reproducible:
Each time I restart the computer, the message appears again

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Adam Williamson 2011-12-02 19:56:02 UTC
anaconda team, my read on this is that it's barfing because the user's existing install is on a GPT-labelled disk with no BIOS boot partition. This is, I think, because it's a Mac. So it's hitting the check for a BIOS boot partition, but the upgrade process either doesn't know to try and create one, or it can't because the disk's full.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Chris Lumens 2012-11-30 03:19:04 UTC
This should no longer be a problem with the new upgrade procedure in F18 (fedup), since we are not using anaconda and anaconda doesn't even know about upgrades anymore.  If you do continue to see this problem with a fresh install, please feel free to reopen this bug.  Thanks.


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