Red Hat Bugzilla – Bug 962369
[abrt] policycoreutils-2.1.13-59.fc18: policydb_destroy: Process /usr/sbin/semodule was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-11 15:11:48 EDT
Description of problem:
I was running a local fix from sealert # semodule -i F18lightdm01.pp
Segmentation fault (core dumped)
Version-Release number of selected component:
cmdline: semodule -i F18lightdm01.pp
runlevel: N 5
Thread no. 1 (4 frames)
#2 policydb_destroy at policydb.c:1337
#3 sepol_policydb_free_internal at policydb_public.c:82
#4 semanage_direct_commit at direct_api.c:1007
#5 semanage_commit at handle.c:485
Created attachment 747151 [details]
Created attachment 747152 [details]
Created attachment 747153 [details]
Created attachment 747154 [details]
Created attachment 747155 [details]
Created attachment 747156 [details]
Created attachment 747157 [details]
Created attachment 747158 [details]
Created attachment 747159 [details]
Created attachment 747160 [details]
Was this done on a limited memory system?
8 gb ram, quad 2 core
That looks fine. Is this repeatable?
(In reply to comment #13)
> That looks fine. Is this repeatable?
Haven't managed to cause another crash, even with Azureus\Vuze running.
Ok I am going to close with Insufficient data, since I can not find the problem.
Reopen if it happens again