Bug 588135 - [abrt] crash in numptyphysics-0.3-0.5.20080925svn.fc12: Process /usr/bin/numptyphysics was killed by signal 6 (SIGABRT)
[abrt] crash in numptyphysics-0.3-0.5.20080925svn.fc12: Process /usr/bin/nump...
Status: CLOSED DUPLICATE of bug 553925
Product: Fedora
Classification: Fedora
Component: numptyphysics (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-02 16:08 EDT by Elliot
Modified: 2010-05-24 11:07 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-24 11:07:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (9.92 KB, text/plain)
2010-05-02 16:08 EDT, Elliot
no flags Details

  None (edit)
Description Elliot 2010-05-02 16:08:06 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: numptyphysics
comment: In Numpty Physics I bumped the red ball object out of the screen, without it touching the yellow star goal object.
component: numptyphysics
executable: /usr/bin/numptyphysics
global_uuid: ddb46e85af0066161a8535947ba06963f023616c
package: numptyphysics-0.3-0.5.20080925svn.fc12
rating: 4
reason: Process /usr/bin/numptyphysics was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
Knock the red ball object out of the screen without it coming in contact with the yellow star goal object.
Comment 1 Elliot 2010-05-02 16:08:08 EDT
Created attachment 410848 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-24 11:07:37 EDT

*** This bug has been marked as a duplicate of bug 553925 ***
Comment 3 Karel Klíč 2010-05-24 11:07:37 EDT
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #553925.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.