Red Hat Bugzilla – Bug 73132
Install Crash RedHat v7.3
Last modified: 2007-04-18 12:46:13 EDT
Description of Problem: Crash or abort during v7.3 install. Install repeated
multiple times mostly in graphic mode. Always crashed after disk format. Last
install in text mode completed disk format; image transfer process was about 50-
70% complete. A dump to floppy was requested but failed to occur after multiple
attempts. The following error information (found between the *** lines)was
produced with a recommendation to submit a report.
Trackback (innermost last):
File /usr/bin/anaconda, line 633 is ?
intf.run(id, dispatch, configFileData)
File /usr/lib/anaconda/text.py, line 427, in run
File /usr/lib/anaconda/dispatch.py, line 144, in gotoNext
File /usr/lib/anaconda/dispatch.py, line 209, in moveStep
rc = apply(func, self.bindArgs(args))
File /usr/lib/anaconda/packages.py, line 536, in doInstall
File /usr/lib/anaconda/ packages.py, line 338, in sortPackages
TypeError: read-only character buffer, None
Version-Release number of selected component (if applicable):
How Reproducible: Have run install multiple times, the last time in text mode.
Assumedly prior results were all the same.
Steps to Reproduce:
1. Standard install accepted all defaults
2. Accepted system partitioning
3. Accepted Grub Loader
4. Accepted Gnome with minimal other packages
Additional Information - Only OS on the PC. Disk size about 4.3Gb
devhda1 1 6 47 ext3 /boot yes
devhda2 7 537 38xx ext3 / yes
devhda3 538 1xx swp yes
Please test your installation media:
Closing due to inactivity.
Please reopen this bug report if you continue to have problems.
The media was tested immediately after testing was suggested and tested just
fine. The CD Drive was changed under the pretext that perhaps it was not fast
enough. But installation was still unsuccessful even with default
installation, including default partitioning. Default partitioning sets the
boot partition at 47MB, and yet the system to be loaded at 1300-1400 MB.
My assumption is the files/system in excess of 47MB would be loaded in the next
partition. The next item that could be a possible problem is the Video - its
on board and takes 4MB out of the 128MB system. The Video and 4MB memory is
recognized so one would assume it is handled properly. But since I have not had
a chance to look under the covers I am not able to check this item or see what
is going on.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.