Bug 1231482

Summary: [abrt] fros: XCloseDisplay(): python3.4 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: iliketurtlesbro
Component: frosAssignee: Jakub Filak <jfilak>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: awilliam, bugs.michael, davidpocina, debugger94, igeo.cu, jberan, jfilak, jirinek, leinfeva, satellitgo, twohotis, vondruch, willymacha13
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0a361508dd7efd364258efe174c9941763ea1a6c
Whiteboard: abrt_hash:601f7547a3eb2c5f398db62891db2ddb94934841
Fixed In Version: 1.1-6.fc23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-06 17:05:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description iliketurtlesbro 2015-06-13 20:46:27 UTC
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

Comment 1 iliketurtlesbro 2015-06-13 20:46:30 UTC
Created attachment 1038408 [details]
File: backtrace

Comment 2 iliketurtlesbro 2015-06-13 20:46:30 UTC
Created attachment 1038409 [details]
File: cgroup

Comment 3 iliketurtlesbro 2015-06-13 20:46:31 UTC
Created attachment 1038410 [details]
File: core_backtrace

Comment 4 iliketurtlesbro 2015-06-13 20:46:32 UTC
Created attachment 1038411 [details]
File: dso_list

Comment 5 iliketurtlesbro 2015-06-13 20:46:33 UTC
Created attachment 1038412 [details]
File: environ

Comment 6 iliketurtlesbro 2015-06-13 20:46:33 UTC
Created attachment 1038413 [details]
File: limits

Comment 7 iliketurtlesbro 2015-06-13 20:46:34 UTC
Created attachment 1038414 [details]
File: maps

Comment 8 iliketurtlesbro 2015-06-13 20:46:35 UTC
Created attachment 1038415 [details]
File: mountinfo

Comment 9 iliketurtlesbro 2015-06-13 20:46:36 UTC
Created attachment 1038416 [details]
File: namespaces

Comment 10 iliketurtlesbro 2015-06-13 20:46:37 UTC
Created attachment 1038417 [details]
File: open_fds

Comment 11 iliketurtlesbro 2015-06-13 20:46:38 UTC
Created attachment 1038418 [details]
File: proc_pid_status

Comment 12 Adam Williamson 2015-06-17 19:51:40 UTC
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.

Comment 13 David Pocina 2015-06-28 14:41:25 UTC
Adam Williamson is right. At least that is exactly what just happened to me.

Comment 14 Jan Kurik 2015-07-15 14:00:35 UTC
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

Comment 15 Fedora Update System 2015-07-29 15:32:17 UTC
fros-1.1-4.fc23 has been submitted as an update for Fedora 23.
https://admin.fedoraproject.org/updates/fros-1.1-4.fc23

Comment 16 Fedora Update System 2015-07-30 02:07:09 UTC
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).

Comment 17 Fedora Update System 2015-08-26 04:25:58 UTC
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

Comment 18 Fedora Update System 2015-09-06 17:05:44 UTC
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.