Red Hat Bugzilla – Bug 71980
Kickstart 7.3: %packages parameters causes crash
Last modified: 2007-04-18 12:45:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
Description of problem:
When using %packages --resolvedeps in my kickstart file for RedHat 7.3,
anaconda crashes with signal 11 and immediately boots. There are no
suspicious log messages on vt3/vt4. %packages --ignoredeps crashes
as well, and so does %packages --anystring. Using %packages without
parameters works fine, but prompts default non-automatic behaviour
during install.Chosing "resolve dependancies" in this stage works.
The box is a PIII 800 Mhz with ide-disks. I use http install.
Kickstart file is attached.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Use kickstart file with %packages parameters
Actual Results: Immediate "install exited abnormally -- received signal 11"
from Anaconda. DHCP, Retrieval of kickstartfile and loading of modules completed
Created attachment 71624 [details]
kickstart file reproducing problem
Your kickstart config doesn't happen to have any dos newlines in it, does it?
(can't depend on html upload to not corrupt those :/)
That was one of my initial thoughts as well, but a quick run though 'od -b' does
not reveal any dos newlines. Are there any other special chars I should look
for?(typically ones invisible to emacs in shell-script mode).
Slight Ooops on my part, as the attached kickstart file does not reproduce the
problem. A couple of %post commands were left out due to an oversight in my m4
compilation - mera culpa.
I have now determined what exactly makes anaconda choke. The missing %post lines
contained \\n (backslash newline) for formatting. This produces the error
whenever %packages is used with a parameter.
Further attachments folllow.
Created attachment 72207 [details]
Created attachment 72208 [details]
This does not work
Created attachment 72209 [details]
Formatting newlines work without --resolvedeps
This bug has been inappropriately marked MODIFIED. Please review the bug life
cycle information at
This is a duplicate.
*** This bug has been marked as a duplicate of 71115 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.