Red Hat Bugzilla – Bug 139488
Installer exits with "install exited unexpectedly"
Last modified: 2007-11-30 17:10:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Description of problem:
When using kiskstart with FC3, if "part" is defined, installer
crashes with "install exited unexpectedly" with no traceback.
If "part" is not defined in the kickstart file, the partition
information is requested and everything proceeds to install ok.
If Fedora/base/*, isolinux/* and .discinfo are taken from FC2 and
replace FC3's version, everything is as expected. The same happens
on the i386 version, so it is not a 64bit issue. Attached are a copy
of ks.cfg and isolinux/isolinux.cfg that are the only changes to the
FC3 iso images.
This is not an issue with FC2.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Take FC3 disc1 ISO image
2.Add ks.cfg in root of iso image
4.Burn new iso and try to build system
Actual Results: Build gets as far as preparing rpms for installation
and then crashes with "install exited unexpectedly"
Expected Results: The install should successfully complete
5.Comment out the 3 "part" lines from ks.cfg and retry - now all
works after using Disk Druid.
Created attachment 106789 [details]
I do not believe that the packages selected make any difference - one of the
iterations was to use only the loaded packes on a built FC3 system - which
Created attachment 106790 [details]
*** This bug has been marked as a duplicate of 137533 ***
OK, but I am not doing this from a hard-disc install, and I am pretty
confident that I do not go this code path - in particular, I am not
using /dev within the ks.cfg file.
I also did not get glibc complaining about any double frees etc.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.