Bug 590645 - [abrt] crash in scigraphica-2.1.0-9.fc12: raise: Process /usr/bin/scigraphica was killed by signal 11 (SIGSEGV)
[abrt] crash in scigraphica-2.1.0-9.fc12: raise: Process /usr/bin/scigraphica...
Status: CLOSED DUPLICATE of bug 554383
Product: Fedora
Classification: Fedora
Component: scigraphica (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Deji Akingunola
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-10 08:04 EDT by jose maturana
Modified: 2010-05-25 06:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 06:22:08 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 (17.09 KB, text/plain)
2010-05-10 08:04 EDT, jose maturana
no flags Details

  None (edit)
Description jose maturana 2010-05-10 08:04:15 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/scigraphica
comment: I just start the program  for first time and receive a message, "sorry, failed to rescue the project"
component: scigraphica
crash_function: raise
executable: /usr/bin/scigraphica
global_uuid: 847e2f76b89434d417ccd6d4677e032be8d532c0
package: scigraphica-2.1.0-9.fc12
rating: 4
reason: Process /usr/bin/scigraphica was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Just open it, that's all
Comment 1 jose maturana 2010-05-10 08:04:17 EDT
Created attachment 412809 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 06:22:08 EDT

*** This bug has been marked as a duplicate of bug 554383 ***
Comment 3 Karel Klíč 2010-05-25 06:22:08 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 #554383.

Sorry for the inconvenience.

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