Bug 678462 - [abrt] gimp-2:2.6.11-7.fc15: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gimp-2:2.6.11-7.fc15: Process /usr/bin/gimp-2.6 was killed by signal 1...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: rawhide
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e1469e504ce00c29b277d6ed65a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-18 02:37 UTC by Luya Tshimbalanga
Modified: 2012-09-19 19:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-19 19:35:37 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (30.22 KB, text/plain)
2011-02-18 02:37 UTC, Luya Tshimbalanga
no flags Details

Description Luya Tshimbalanga 2011-02-18 02:37:51 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 30941 bytes
cmdline: gimp-2.6
comment: Gimp crashed when attempting to save new file
component: gimp
Attached file: coredump, 63225856 bytes
executable: /usr/bin/gimp-2.6
kernel: 2.6.38-0.rc4.git7.1.fc15.i686
package: gimp-2:2.6.11-7.fc15
rating: 3
reason: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1297994400
uid: 500

How to reproduce
-----
1.Attempt to save as new file
2.
3.

Comment 1 Luya Tshimbalanga 2011-02-18 02:37:53 UTC
Created attachment 479443 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 17:38:20 UTC
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information.

Bugs which were found to be similar to this bug: 
  gimp: bug #637334, bug #672738, bug #704655
  gtk2: bug #630405

This comment is automatically generated.

Comment 3 Luya Tshimbalanga 2012-09-19 19:35:37 UTC
Closing bug now that fc15 reached end of life.


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