Bug 681951

Summary: [abrt] ipython-0.10.1-3.fc13: int_format: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Phil V <pv.bugzilla>
Component: ipythonAssignee: Bryan Kearney <bkearney>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: bkearney, shahms, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:dfa9c384605289338013da3ef055e705096f099c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 12:05:20 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 Phil V 2011-03-03 17:11:01 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/ipython -pylab
component: ipython
crash_function: int_format
executable: /usr/bin/python
kernel: 2.6.34.7-66.fc13.x86_64
package: ipython-0.10.1-3.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1298953703
uid: 500

How to reproduce
-----
1. unsure
2.
3.

Comment 1 Phil V 2011-03-03 17:11:04 UTC
Created attachment 482119 [details]
File: backtrace

Comment 2 Phil V 2011-03-03 17:12:09 UTC
Package: ipython-0.10.1-3.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. unsure
2.
3.

Comment 3 Thomas Spura 2011-03-03 23:15:39 UTC
What exactly did you run?

The crash happend with "ipython -pylab" started.
When only running that command, I can't reproduce the crash (f13.x86_64.

Where you typing something on the ipython console?
If yes, what?

Some string format crashed somewhere, but where, I can't tell without a way on what you did.

Comment 4 Phil V 2011-03-04 03:58:30 UTC
However I have recently been experiencing kernel crashes and crashes in gnome-terminal as well as crashes in ipython. 

Please see bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=681953
https://bugzilla.redhat.com/show_bug.cgi?id=681951
https://bugzilla.redhat.com/show_bug.cgi?id=678802

abrt doesn't give reference info for the kernel oops reports, but:
kernel oops General Protection Fault 0000 [#1] SMP
kernel BUG at drivers/gpu/drm/i915/i915_gem.c:4213!
kernel BUG: unable to handle kernel NULL pointer dereference at 00000000000000130

Comment 5 Bug Zapper 2011-05-30 11:08:15 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 6 Bug Zapper 2011-06-27 12:05:20 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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