Bug 590367 - [abrt] crash in gthumb-2.10.11-9.fc12: raise: Process /usr/bin/gthumb was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gthumb-2.10.11-9.fc12: raise: Process /usr/bin/gthumb was kil...
Keywords:
Status: CLOSED DUPLICATE of bug 539722
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:66bd81df2df6fcf505b43a33bb8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-09 07:42 UTC by robert fairb
Modified: 2010-05-25 09:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:31:31 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (23.71 KB, text/plain)
2010-05-09 07:42 UTC, robert fairb 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description robert fairb 2010-05-09 07:42:11 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gthumb '/home/robert/.cache/.fr-qkm6ES/saki 61/credits61.png'
component: gthumb
crash_function: raise
executable: /usr/bin/gthumb
global_uuid: 66bd81df2df6fcf505b43a33bb8e8b2d82b346ab
kernel: 2.6.32.11-99.fc12.i686
package: gthumb-2.10.11-9.fc12
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.i opened a picture in a zip file i got from a torrent 
2.it worked but then i closed it and it crashed
3.
Comment 1 robert fairb 2010-05-09 07:42:13 UTC 
Created attachment 412603 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:31:31 UTC 

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

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