abrt detected a crash. How to reproduce ----- 1. 2. 3. Additional information ====== Attached files ---- backtrace cmdline ----- /usr/bin/python -E /usr/bin/sealert -b component ----- setroubleshoot executable ----- /usr/bin/sealert kernel ----- 2.6.31-40.fc12.x86_64 package ----- setroubleshoot-server-2.2.30-1.fc12 uuid ----- b28c0171
Created attachment 362686 [details] File: backtrace
Any idea how/when this happened?
Yeah, seems to happen when it starts... Happens every time I login, and/or every time I run Applications->System Tools->SELinux Troubleshooter
+1
Not sure its related, but I'm seeing these from abrt: type=AVC msg=audit(1253916540.408:274): avc: denied { write } for pid=1444 comm="abrtd" name="rpm" dev=dm-0 ino=18 scontext=system_u:system_r:abrt_t:s0 tcontext=system_u:object_r:rpm_var_lib_t:s0 tclass=dir type=SYSCALL msg=audit(1253916540.408:274): arch=c000003e syscall=21 success=yes exit=0 a0=202c5f0 a1=2 a2=0 a3=0 items=0 ppid=1 pid=1444 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="abrtd" exe="/usr/sbin/abrtd" subj=system_u:system_r:abrt_t:s0 key=(null) type=AVC msg=audit(1253916540.415:275): avc: denied { read write } for pid=1444 comm="abrtd" name="__db.001" dev=dm-0 ino=12840 scontext=system_u:system_r:abrt_t:s0 tcontext=system_u:object_r:rpm_var_lib_t:s0 tclass=file type=AVC msg=audit(1253916540.415:275): avc: denied { open } for pid=1444 comm="abrtd" name="__db.001" dev=dm-0 ino=12840 scontext=system_u:system_r:abrt_t:s0 tcontext=system_u:object_r:rpm_var_lib_t:s0 tclass=file type=SYSCALL msg=audit(1253916540.415:275): arch=c000003e syscall=2 success=yes exit=0 a0=204c4c0 a1=2 a2=0 a3=0 items=0 ppid=1 pid=1444 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="abrtd" exe="/usr/sbin/abrtd" subj=system_u:system_r:abrt_t:s0 key=(null) and/or #============= abrt_t ============== allow abrt_t rpm_var_lib_t:dir { write add_name }; allow abrt_t rpm_var_lib_t:file { read write create open lock }; [root@tlondon ~]#
I downgraded the python-slip packages (from 0.2.5-1.fc12-> 0.2.4-1.fc12) and I believe sealert started working (at least from the command line).
downgrading python-slip just deffers the crash till you try to use sealert to report a bug (won't report the abrt-detected crash since it has my bugzilla password in it)
I consider this essential for debugging selinux related problems. The currect test candidate for F12 beta has this problem. Therefore, I am adding F12Beta as a blocker
Fixed in python-slip-0.2.6-1.fc12