Bug 700518

Summary: [abrt] gthumb-2.12.2-1.fc14.2: Process /usr/bin/gthumb was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Mike Parker <mikethepsych>
Component: gthumbAssignee: Christian Krause <chkr>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: chkr
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2c29102ad99df39ad1fba2d23b711d0dfb56f7a6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 18:01:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Mike Parker 2011-04-28 15:14:31 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 113185 bytes
cmdline: gthumb
component: gthumb
Attached file: coredump, 109121536 bytes
crash_function: Exiv2::Internal::TiffDirectory::doWrite
executable: /usr/bin/gthumb
kernel: 2.6.35.12-90.fc14.x86_64
package: gthumb-2.12.2-1.fc14.2
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304003166
uid: 500

How to reproduce
-----
1. Opened Gthumb
2. Browsed to /usr/share/backgrounds/nature
3. Manually selected all images (14) in directory and clicked Tools -> Resize Images
4. Selected desired destination folder. All other settings left at default (640x480, preserve aspect ratio)
5. Clicked Execute
Comment 1 Mike Parker 2011-04-28 15:14:36 UTC 
Created attachment 495565 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 18:01:02 UTC 
Backtrace analysis found this bug to be similar to bug #680690, closing as duplicate.

Bugs which were found to be similar to this bug: bug #680690, bug #711138

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 680690 ***