Bug 1051403

Summary: [abrt] spyder: _dl_relocate_object(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Eswara Arun Kishore <eakishore>
Component: spyderAssignee: Radek Novacek <rnovacek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ovasik, rnovacek, thozza
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d17b761d43dc0f45c94e22f5edf5bfb2daa7ae1a
Whiteboard: abrt_hash:1965c88143a970ff2a4c29413b19e4ec2638c521
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:19:36 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Eswara Arun Kishore 2014-01-10 08:51:25 UTC 
Description of problem:
I have launched the spyder application (Python IDE) after upgrading my fc19 system to fc20 using fedup and from iso image (followed same procedures as mentioned on fedora fedup portal). 
Many programs did not work after upgradation. Office suite, TeXmacs, Spyder for example. These applications did not even load and crashed when launched. 
This error is generated during launching of spyder application.

Version-Release number of selected component:
spyder-2.2.4-1.fc19

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        /usr/bin/python /usr/bin/spyder
crash_function: _dl_relocate_object
executable:     /usr/bin/python2.7
kernel:         3.12.5-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _dl_relocate_object at /lib64/ld-linux-x86-64.so.2
 #1 dl_open_worker at /lib64/ld-linux-x86-64.so.2
 #2 _dl_catch_error at /lib64/ld-linux-x86-64.so.2
 #3 _dl_open at /lib64/ld-linux-x86-64.so.2
 #4 dlopen_doit at /lib64/libdl.so.2
 #5 _dl_catch_error at /lib64/ld-linux-x86-64.so.2
 #6 _dlerror_run at /lib64/libdl.so.2
 #7 dlopen@@GLIBC_2.2.5 at /lib64/libdl.so.2
 #8 py_dl_open at /usr/lib64/python2.7/lib-dynload/_ctypes.so
 #9 PyEval_EvalFrameEx at /lib64/libpython2.7.so.1.0
Comment 1 Eswara Arun Kishore 2014-01-10 08:51:30 UTC 
Created attachment 848097 [details]
File: backtrace
Comment 2 Eswara Arun Kishore 2014-01-10 08:51:33 UTC 
Created attachment 848098 [details]
File: cgroup
Comment 3 Eswara Arun Kishore 2014-01-10 08:51:35 UTC 
Created attachment 848099 [details]
File: core_backtrace
Comment 4 Eswara Arun Kishore 2014-01-10 08:51:37 UTC 
Created attachment 848100 [details]
File: dso_list
Comment 5 Eswara Arun Kishore 2014-01-10 08:51:40 UTC 
Created attachment 848101 [details]
File: environ
Comment 6 Eswara Arun Kishore 2014-01-10 08:51:42 UTC 
Created attachment 848102 [details]
File: exploitable
Comment 7 Eswara Arun Kishore 2014-01-10 08:51:44 UTC 
Created attachment 848103 [details]
File: limits
Comment 8 Eswara Arun Kishore 2014-01-10 08:51:47 UTC 
Created attachment 848104 [details]
File: maps
Comment 9 Eswara Arun Kishore 2014-01-10 08:51:50 UTC 
Created attachment 848105 [details]
File: open_fds
Comment 10 Eswara Arun Kishore 2014-01-10 08:51:52 UTC 
Created attachment 848106 [details]
File: proc_pid_status
Comment 11 Eswara Arun Kishore 2014-01-10 08:51:54 UTC 
Created attachment 848107 [details]
File: var_log_messages
Comment 12 Radek Novacek 2014-01-10 09:04:25 UTC 
It seems that there was something wrong with your update, try running following commands that should help to pinpoint the cause of your problems:

yum distro-sync

rpm -Va
Comment 13 Fedora End Of Life 2015-05-29 10:25:31 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 14 Fedora End Of Life 2015-06-29 14:19:36 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.