Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 590209 - [abrt] crash in gimp-2:2.6.8-1.fc12: file_save_cmd_callback: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gimp-2:2.6.8-1.fc12: file_save_cmd_callback: Process /usr/bin...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:92eb07981bd4bfab980582f162e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-08 04:52 UTC by qte125
Modified: 2010-05-26 12:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-26 12:22:37 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (33.53 KB, text/plain)
2010-05-08 04:52 UTC, qte125
no flags Details

Description qte125 2010-05-08 04:52:40 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gimp-2.6 '/home/notask/Desktop/\xe9\x87\x91\xe5\x85\x88\xe5\x8f\x8b.psd'
component: gimp
crash_function: file_save_cmd_callback
executable: /usr/bin/gimp-2.6
global_uuid: 92eb07981bd4bfab980582f162eeb61acf559c62
kernel: 2.6.32.11-99.fc12.i686
package: gimp-2:2.6.8-1.fc12
rating: 4
reason: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 qte125 2010-05-08 04:52:43 UTC
Created attachment 412483 [details]
File: backtrace

Comment 2 Nils Philippsen 2010-05-26 12:22:37 UTC
Closing due to insufficient data. Please supply the following information if you want to reopen this bug:

How reliably can you reproduce the crash? What were you doing at the time of the crash? Please supply step-by-step instructions how to reproduce this problem. Thanks.


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