From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.5-9 i686; en-US; rv:0.9.1)
Description of problem:
Anaconda fails at the very end of the installation after the post installation.
Using graphical install with custom setup and manual diskdruid filesystem
setup it installs everything and performs the post installation. Right at
the end of that or right after it (scrollbar is at 100%) i get the attached
I selected grub as bootloader if that helps, but the system didn't come up
afterewards, so i guess it has something to do with that.
Here my partition layout:
Disk /dev/hda: 255 heads, 63 sectors, 3737 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 66 530113+ 82 Linux swap
/dev/hda2 67 328 2104515 83 Linux
/dev/hda3 329 590 2104515 83 Linux
/dev/hda4 591 3737 25278277+ 83 Linux
I installed on /dev/hda2.
Steps to Reproduce:
1.Run installation as described
2.Wait till the very end for the traceback
Actual Results: System was basically completely installed but didn't boot
Expected Results: Installation should have finished.
Created attachment 21928 [details]
Seen this before - katzj is testing with an older python package. Thinking that
recomilation has caused bad code generation.
I'm going to tag onto this one; apologies if it's not the same thing.
TUI install of Fairfax beta1 over FTP.
Twice in a row, same thing.
At the very end, when the "Performing post install configuration" progress bar
is filled red for the first six spaces, [Exception Occurred]:
Traceback (innermost last)
File "/usr/bin/anaconda", line 561, in ?
File "/tmp/11581-i386/install//usr/lib/anaconda/text.py", line 386, in run
File "/tmp/11581-i386/install//usr/lib/anaconda/dispatch.py", line 120, in
File "/tmp/11581-i386/install//usr/lib/anaconda/dispatch.py", line 185, in
File "/tmp/11581-i386/install//usr/lib/anaconda/packages.py", line 572, in
File "/tmp/11581-i386/install//usr/lib/anaconda/packages.py", line 713, in
ValueError: unpack tuple of wrong size
The VT's don't seem to contain anything exceptional.
Same result with HTTP install. See bug 47039 for how I'm configuring TCP/IP,
and bug 46746 for how it autopartitioned (I'm just accepting the default
partitioning now; only steps 1-3 of that bug apply to this bug).
*** This bug has been marked as a duplicate of 46450 ***
oops, duped wrong bug
Brent - this is a different bug, please refile your unpack tuple bug as another bug.
Done; see bug 47126. Sorry for the pollution. :-)
*** Bug 47126 has been marked as a duplicate of this bug. ***
*** Bug 47082 has been marked as a duplicate of this bug. ***
This defect considered MUST-FIX for Fairfax gold-release.
No real progress on this one yet - msw has enabled some code which should help
isolate it (if it would just happen again).
Well, this has a complex history; I tacked onto this bug, was told my problem
was different; created a new bug 47126, which was then marked as a duplicate of
I would be happy to test here, on the hardware where it happened, if you have an
updates disk with the new code.
*** Bug 49862 has been marked as a duplicate of this bug. ***
fixed a double free in the rpm python binding that was causing this.