Version-Release number of selected component: gnome-abrt-0.2.8-1.fc18 Additional info: backtrace_rating: 4 cmdline: python /usr/bin/gnome-abrt crash_function: dlmmap_locked executable: /usr/bin/python2.7 kernel: 3.8.4-202.fc18.i686 uid: 1000 ureports_counter: 2 Truncated backtrace: Thread no. 1 (10 frames) #0 dlmmap_locked at ../src/closures.c:437 #1 dlmmap at ../src/closures.c:477 #2 sys_alloc at ../src/dlmalloc.c:3515 #3 dlmalloc at ../src/dlmalloc.c:4245 #4 ffi_closure_alloc at ../src/closures.c:543 #5 g_callable_info_prepare_closure at girepository/girffi.c:363 #6 _pygi_make_native_closure at pygi-closure.c:578 #7 _wrap_pyg_hook_up_vfunc_implementation at gimodule.c:346 #8 PyCFunction_Call at /usr/src/debug/Python-2.7.3/Objects/methodobject.c:116 #9 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4098
Created attachment 717431 [details] File: backtrace
Created attachment 717432 [details] File: cgroup
Created attachment 717433 [details] File: core_backtrace
Created attachment 717434 [details] File: dso_list
Created attachment 717435 [details] File: environ
Created attachment 717436 [details] File: limits
Created attachment 717437 [details] File: maps
Created attachment 717438 [details] File: open_fds
Created attachment 717439 [details] File: proc_pid_status
Created attachment 717440 [details] File: var_log_messages
Created attachment 717441 [details] File: xsession_errors
Thanks for filing this bug report. Seems like a bug in selinux-policy (see bug #697223, bug #815228). Do you have any AVC similar to some of AVCs in comments of bug #697223?
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.