Version-Release number of selected component: fros-1.1-2.fc23 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/fros --is-available crash_function: XCloseDisplay executable: /usr/bin/python3.4 global_pid: 5258 kernel: 4.1.0-0.rc7.git0.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 XCloseDisplay at /lib64/libX11.so.6 #1 ffi_call_unix64 at /lib64/libffi.so.6 #2 ffi_call at /lib64/libffi.so.6 #3 _ctypes_callproc at /usr/lib64/python3.4/lib-dynload/_ctypes.cpython-34m.so #4 PyCFuncPtr_call at /usr/lib64/python3.4/lib-dynload/_ctypes.cpython-34m.so #5 PyObject_Call at /lib64/libpython3.4m.so.1.0 #6 PyEval_EvalFrameEx at /lib64/libpython3.4m.so.1.0 #7 PyEval_EvalCodeEx at /lib64/libpython3.4m.so.1.0 #8 PyEval_EvalCode at /lib64/libpython3.4m.so.1.0 #9 run_mod at /lib64/libpython3.4m.so.1.0
Created attachment 1038408 [details] File: backtrace
Created attachment 1038409 [details] File: cgroup
Created attachment 1038410 [details] File: core_backtrace
Created attachment 1038411 [details] File: dso_list
Created attachment 1038412 [details] File: environ
Created attachment 1038413 [details] File: limits
Created attachment 1038414 [details] File: maps
Created attachment 1038415 [details] File: mountinfo
Created attachment 1038416 [details] File: namespaces
Created attachment 1038417 [details] File: open_fds
Created attachment 1038418 [details] File: proc_pid_status
I think this actually happens while you're reporting some (other) abrt-caught crash. It doesn't actually result in any failure visible to the user, it's just a 'phantom' crash report.
Adam Williamson is right. At least that is exactly what just happened to me.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
fros-1.1-4.fc23 has been submitted as an update for Fedora 23. https://admin.fedoraproject.org/updates/fros-1.1-4.fc23
Package fros-1.1-4.fc23: * should fix your issue, * was pushed to the Fedora 23 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fros-1.1-4.fc23' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12319/fros-1.1-4.fc23 then log in and leave karma (feedback).
fros-1.1-6.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update fros'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14187
fros-1.1-6.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.