Bug 599457
Summary: | Net Installer Crashed After Retrieving install.img | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | roshnic | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 13 | CC: | anaconda-maint-list, jonathan, vanmeeuwen+fedora | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 612232 (view as bug list) | Environment: | |||||||
Last Closed: | 2010-08-09 19:45:15 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
roshnic
2010-06-03 09:52:55 UTC
The important frames... 0x8058114 - /usr/src/debug/anaconda-13.42/loader/selinux.c:47 0x80527d9 - /usr/src/debug/anaconda-13.42/loader/loader.c:2142 42 if (!(pid = fork())) { 43 setenv("LD_LIBRARY_PATH", LIBPATH, 1); 44 execl("/sbin/load_policy", 45 "/sbin/load_policy", "-q", NULL); 46 logMessage(ERROR, "exec of load_policy failed: %m"); 47 exit(1); 48 } This is a pretty strange place to get a crash, but it seems obvious what the problem is - load_policy failed. When you get this crash, can you jump over to tty3 and tty4, take a picture, and attach them to this bug report? Created attachment 421115 [details]
screenshot of tty3
Created attachment 421116 [details]
screenshot of tty4
Are you perhaps trying to install an x86_64 distribution on an i386 machine? I've been completely unable to reproduce this problem in any installations here, and we have not gotten widespread reports of it. So I don't know what could be going on. |