Description of problem: Trying to run gnome-abrt on Rawhide Version-Release number of selected component: python3-3.4.3-1.fc23 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/gnome-abrt crash_function: XCloseDisplay executable: /usr/bin/python3.4 global_pid: 11677 kernel: 4.1.0-0.rc0.git14.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at pon 2015-03-23 18:36:15 CET, end at wto 2015-04-28 12:39:40 CEST. -- Truncated backtrace: Thread no. 1 (10 frames) #0 XCloseDisplay at ClDisplay.c:51 #1 ffi_call_unix64 at ../src/x86/unix64.S:76 #2 ffi_call at ../src/x86/ffi64.c:525 #3 _call_function_pointer at /usr/src/debug/Python-3.4.3/Modules/_ctypes/callproc.c:811 #4 _ctypes_callproc at /usr/src/debug/Python-3.4.3/Modules/_ctypes/callproc.c:1149 #5 PyCFuncPtr_call at /usr/src/debug/Python-3.4.3/Modules/_ctypes/_ctypes.c:3848 #6 PyObject_Call at /usr/src/debug/Python-3.4.3/Objects/abstract.c:2040 #7 do_call at /usr/src/debug/Python-3.4.3/Python/ceval.c:4495 #8 call_function at /usr/src/debug/Python-3.4.3/Python/ceval.c:4293 #9 PyEval_EvalFrameEx at /usr/src/debug/Python-3.4.3/Python/ceval.c:2862
Created attachment 1020624 [details] File: backtrace
Created attachment 1020625 [details] File: cgroup
Created attachment 1020626 [details] File: core_backtrace
Created attachment 1020627 [details] File: dso_list
Created attachment 1020628 [details] File: environ
Created attachment 1020629 [details] File: limits
Created attachment 1020630 [details] File: maps
Created attachment 1020631 [details] File: mountinfo
Created attachment 1020632 [details] File: namespaces
Created attachment 1020633 [details] File: open_fds
Created attachment 1020634 [details] File: proc_pid_status
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Looks like a bug in gnome-abrt, not Python3 itself. Let me know if the Python team can assist.
Marking this as duplicate of 1188002. Undo if you think this is not correct. *** This bug has been marked as a duplicate of bug 1188002 ***