Bug 646175 - [abrt] gimp-2:2.6.11-1.fc14: get_bounding_box: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gimp-2:2.6.11-1.fc14: get_bounding_box: Process /usr/bin/gimp-2.6 was ...
Keywords:
Status: CLOSED DUPLICATE of bug 627184
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:78a613baed533e307574a5f4a1c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-24 19:27 UTC by Paul Finnigan
Modified: 2010-11-09 15:51 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:51:44 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (32.27 KB, text/plain)
2010-10-24 19:27 UTC, Paul Finnigan 		no flags Details
View All

Description Paul Finnigan 2010-10-24 19:27:19 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gimp /tmp/DSC_2419.NEF_J0MGLV.ufraw
comment: I have not managed to recreate the crash, yet
component: gimp
crash_function: get_bounding_box
executable: /usr/bin/gimp-2.6
kernel: 2.6.35.4-28.fc14.x86_64
package: gimp-2:2.6.11-1.fc14
rating: 4
reason: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1287947214
uid: 500

How to reproduce
-----
1. Edit Photograph in Gimp
2. Select GEGL operation...
3. Go through all the options (I was learning how to use the GEGL options as I do not use them enough)
Comment 1 Paul Finnigan 2010-10-24 19:27:22 UTC 
Created attachment 455360 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:51:44 UTC 

*** This bug has been marked as a duplicate of bug 627184 ***
Comment 3 Karel Klíč 2010-11-09 15:51:44 UTC 
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 #627184.

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