Bug 1138593

Summary: [abrt] istanbul: gst_istximage_src_ximage_get(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: rjimenez
Component: istanbulAssignee: Jef Spaleta <jspaleta>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jspaleta
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9977fe5cfaaa926f79c147fbdd112ab303969ba3
Whiteboard: abrt_hash:ae0b08a6abf8fe013311b365f0f6ef6bfdf26311
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:23:50 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 rjimenez 2014-09-05 09:23:17 UTC 
Description of problem:
Trying to run the program

Version-Release number of selected component:
istanbul-0.2.2-20.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/istanbul
crash_function: gst_istximage_src_ximage_get
executable:     /usr/bin/python2.7
kernel:         3.15.10-201.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 gst_istximage_src_ximage_get at gstximagesrc.c:361
 #1 gst_istximage_src_create at gstximagesrc.c:716
 #2 gst_base_src_get_range at gstbasesrc.c:2188
 #3 gst_base_src_loop at gstbasesrc.c:2445
 #4 gst_task_func at gsttask.c:327
 #6 g_thread_proxy at gthread.c:798
Comment 1 rjimenez 2014-09-05 09:23:21 UTC 
Created attachment 934709 [details]
File: backtrace
Comment 2 rjimenez 2014-09-05 09:23:23 UTC 
Created attachment 934710 [details]
File: cgroup
Comment 3 rjimenez 2014-09-05 09:23:24 UTC 
Created attachment 934711 [details]
File: core_backtrace
Comment 4 rjimenez 2014-09-05 09:23:26 UTC 
Created attachment 934712 [details]
File: dso_list
Comment 5 rjimenez 2014-09-05 09:23:27 UTC 
Created attachment 934713 [details]
File: environ
Comment 6 rjimenez 2014-09-05 09:23:28 UTC 
Created attachment 934714 [details]
File: exploitable
Comment 7 rjimenez 2014-09-05 09:23:29 UTC 
Created attachment 934715 [details]
File: limits
Comment 8 rjimenez 2014-09-05 09:23:31 UTC 
Created attachment 934716 [details]
File: maps
Comment 9 rjimenez 2014-09-05 09:23:33 UTC 
Created attachment 934717 [details]
File: open_fds
Comment 10 rjimenez 2014-09-05 09:23:34 UTC 
Created attachment 934718 [details]
File: proc_pid_status
Comment 11 rjimenez 2014-09-05 09:23:35 UTC 
Created attachment 934719 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 12:48:05 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 13 Fedora End Of Life 2015-06-29 22:23:50 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.