Bug 794812

Summary: [abrt] ipython-0.10.2-1.fc14: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Nirav Joshi <nirav.ipr>
Component: ipythonAssignee: Thomas Spura <tomspur>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alexl, mrunge, shahms, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:4e5390123e76862bd63726d961e9dd94838a5bb4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 16:33:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Nirav Joshi 2012-02-17 17:42:10 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 72849 bytes
cmdline: /usr/bin/python /usr/bin/ipython -pylab -colors LightBG
component: ipython
Attached file: coredump, 141197312 bytes
executable: /usr/bin/python
kernel: 2.6.35.14-106.fc14.x86_64
package: ipython-0.10.2-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1329419634
uid: 500

How to reproduce
-----
1.
2.
3.
crashed without warning.

Comment 1 Nirav Joshi 2012-02-17 17:42:12 UTC
Created attachment 563950 [details]
File: backtrace

Comment 2 Thomas Spura 2012-02-17 18:24:07 UTC
Thanks for the bug report.

What have you done, when ipyhton was crashing?

Did you start ipython and were typing something?
In the backtrace is:

"gtk_file_system_model_sort", message=0x391be10 "assertion failed: (r == n_visible_rows)") at gtestutils.c

So this looks like a gtk bug, but there is also readline in the backtrace...
Other than that f14 is not supported anymore, so I cannot push updates anymore.

It would be best, if you could try to get a reproducer and try to reproduce it also on a newer Fedora again.

If that's not possible, all we can do is to close this bug again as WONTFIX:
http://fedoraproject.org/w/index.php?title=BugZappers/How_to_Triage&oldid=244025#Checklist_for_EOL_Bug_Triage

Comment 3 Thomas Spura 2012-02-17 18:25:14 UTC
CC'ing "Alexander Larsson" because of:
http://mail.gnome.org/archives/gtk-devel-list/2011-March/msg00104.html

Comment 4 Fedora End Of Life 2012-08-16 16:33:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping