Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 119699 - Anaconda crashes upgrading FC1 -> FC2t2, Inspiron 5100
Summary: Anaconda crashes upgrading FC1 -> FC2t2, Inspiron 5100
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: FC2Blocker FC3Target
TreeView+ depends on / blocked
 
Reported: 2004-04-01 16:18 UTC by Justin Moore
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-01 16:17:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Upgrade log from failed FC1 -> FC2t2 upgrade. (deleted)
2004-04-01 16:20 UTC, Justin Moore 		no flags Details
View All

Description Justin Moore 2004-04-01 16:18:30 UTC 
Description of problem:
I have a Dell Inspiron 5100 laptop with a fully up-to-date FC1
installation.  I downloaded the i386 binary CDs and used them to
successfully upgrade my AMD desktop at home (they passed the media
check).  When I try to upgrade my laptop, though, the installer
crashes.  Anaconda detects my installation, finds the bootloader, and
works its way through the RPM setup process.  When it actually starts
to upgrade the packages, though, it crashes while upgrading to
libgcc-3.3.3-3.i386 (the first package).  Anaconda exits and the
system reboots.  Fortunately I was able to reboot into FC1 with no
problems.

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


How reproducible:
Every time.

Steps to Reproduce:
1. Attempt to upgrade FC1 to FC2test2.
2. Watch as anaconda crashes.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Justin Moore 2004-04-01 16:20:26 UTC 
Created attachment 99045 [details]
Upgrade log from failed FC1 -> FC2t2 upgrade.

upgrade.log.syslog is empty.
Comment 2 Bill Nottingham 2004-04-05 21:15:44 UTC 
Is there an installer traceback at all?
Comment 3 Justin Moore 2004-04-05 21:21:35 UTC 
There's no traceback; it's not a 'hard' crash.  It gets to the screen
with the big Fedora logo on the left half of the screen and the names
of the packages it's upgrading at the bottom.  It starts to upgrade
libgcc-3.3.3-3.i386, but then exits the installer and reboots.
Comment 4 Justin Moore 2004-04-05 21:23:16 UTC 
Garg.  The Fedora logo is on the /right/ half of the screen, not the
left.  Huked n fonics werkd fur mi.
Comment 5 Jeremy Katz 2004-04-05 21:47:30 UTC 
Is this reproducible?  Is there any text about "unexpected error"? 
How much ram?
Comment 6 Justin Moore 2004-04-06 15:11:33 UTC 
Right before it crashes, on terminal four it prints out a message
about an audit error of some sort.  It happens too quickly for me to
copy it verbatum, but it appears to be an error with python trying to
write to the partition it's upgrading.  An SELinux error, perhaps? 
The laptop reboots immediately after it hits this error, so there's no
time to copy it down.
Comment 7 Jeremy Katz 2004-04-11 17:08:16 UTC 
How about if you hit ctrl-s right as X crashes?  Also, does it happen
in text mode?
Comment 8 Justin Moore 2004-05-05 17:55:23 UTC 
I haven't tried it in text mode yet, but hitting Ctrl-S doesn't do
anything.  This problem is also present in a FC1 -> FC2test3 upgrade
attempt, but the error message has been helpfully removed (AFAICT). 
The installer can upgrade other packages, but only crashes on the
libgcc package.  Fortunately, I have all sorts of nifty FC2 artwork,
and Metacity claims to be logging me into FC2.  Whee. :)
Comment 9 Kevin Kofler 2004-05-30 21:20:54 UTC 
Is this the same as Bug 109389?
Comment 10 Jeremy Katz 2004-09-22 19:12:28 UTC 
Is this better now?
Comment 11 Jeremy Katz 2004-11-01 16:17:33 UTC 
Closing due to inactivity.  Please reopen if you have further
information to add to this report.
Note You need to log in before you can comment on or make changes to this bug.