Bug 1217823

Summary: [abrt] python3: Py_FatalError(): python3.4 killed by SIGABRT
Product: [Fedora] Fedora Reporter: rendi7936 <rendi.7936>
Component: python3Assignee: Matej Stuchlik <mstuchli>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: bkabrda, jberan, mstuchli, pviktori, rkuska, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/53511fb21a2a57fee1612fed56e9627995ed5da2
Whiteboard: abrt_hash:c59e41dd852aaf2021860608662bae7eef377244
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 19:49:57 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: open_fds
none
File: proc_pid_status none

Description rendi7936 2015-05-01 19:21:42 UTC 
Version-Release number of selected component:
python3-3.4.1-16.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/bin/python3.4 /home/rendi7936/Other/Software/pycharm-community-4.0.6/helpers/generator3.py -d /root/.PyCharm40/system/python_stubs/-1247971765/ -s /usr/lib64/python3.4:/usr/lib64/python3.4/plat-linux:/usr/lib64/python3.4/lib-dynload:/usr/lib64/python3.4/site-packages:/usr/lib/python3.4/site-packages zlib /usr/lib64/python3.4/lib-dynload/zlib.cpython-34m.so
crash_function: Py_FatalError
executable:     /usr/bin/python3.4
kernel:         3.19.3-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0
var_log_messages: [System Logs]:\n-- Logs begin at Tue 2015-04-14 06:57:08 WIB, end at Thu 2015-04-23 05:54:21 WIB. --

Truncated backtrace:
Thread no. 1 (3 frames)
 #2 Py_FatalError at /usr/src/debug/Python-3.4.1/Python/pythonrun.c:2641
 #3 _Py_InitializeEx_Private at /usr/src/debug/Python-3.4.1/Python/pythonrun.c:468
 #4 Py_Main at /usr/src/debug/Python-3.4.1/Modules/main.c:654
Comment 1 rendi7936 2015-05-01 19:21:47 UTC 
Created attachment 1021011 [details]
File: backtrace
Comment 2 rendi7936 2015-05-01 19:21:49 UTC 
Created attachment 1021012 [details]
File: cgroup
Comment 3 rendi7936 2015-05-01 19:21:50 UTC 
Created attachment 1021013 [details]
File: core_backtrace
Comment 4 rendi7936 2015-05-01 19:21:52 UTC 
Created attachment 1021014 [details]
File: dso_list
Comment 5 rendi7936 2015-05-01 19:21:54 UTC 
Created attachment 1021015 [details]
File: environ
Comment 6 rendi7936 2015-05-01 19:21:55 UTC 
Created attachment 1021016 [details]
File: limits
Comment 7 rendi7936 2015-05-01 19:21:57 UTC 
Created attachment 1021017 [details]
File: maps
Comment 8 rendi7936 2015-05-01 19:21:59 UTC 
Created attachment 1021018 [details]
File: open_fds
Comment 9 rendi7936 2015-05-01 19:22:01 UTC 
Created attachment 1021019 [details]
File: proc_pid_status
Comment 10 Fedora Admin XMLRPC Client 2015-05-12 12:02:46 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 11 Petr Viktorin (pviktori) 2015-05-13 11:03:32 UTC 
Python crashes with a fatal error: "Py_Initialize: can't initialize sys standard streams", due to the initstdio() function failing.
Judging from the cmdline args, the script seems to be run from PyCharm, which suggests a pretty exotic the environment.
I can see initstdio() has safeguards against stdin/stdout/stderr not being connected, but in this case it's apparently not enough.

It does like this happens before Python even looks at the script to run, so it might be a bug in Python, but without steps to reproduce, a core dump, or even stderr it's difficult to tell what went wrong here.
Comment 12 Fedora End Of Life 2015-11-04 12:00:29 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Jan Kurik 2015-12-02 19:50:00 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.