Bug 699264

Summary: [abrt] gthumb-2.12.2-1.fc14.2: g_file_get_path: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Kovalsky <dkovalsk>
Component: gthumbAssignee: Christian Krause <chkr>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: benl, chkr
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cebb6af059df0e21b558ee6cbb654956e92cba69
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:38:29 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 David Kovalsky 2011-04-24 18:51:52 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 19573 bytes
cmdline: gthumb /home/dkovalsk/Desktop/boty/24042011456.jpg
component: gthumb
Attached file: coredump, 23629824 bytes
crash_function: g_file_get_path
executable: /usr/bin/gthumb
kernel: 2.6.35.12-88.fc14.x86_64
package: gthumb-2.12.2-1.fc14.2
rating: 4
reason: Process /usr/bin/gthumb was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303664579
uid: 10625

How to reproduce
-----
1. Click on desktop to open a graphics file
2. Crash. Seems random. Happened only once and can't reproduce it again.
3.
Comment 1 David Kovalsky 2011-04-24 18:51:55 UTC 
Created attachment 494550 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 16:38:29 UTC 
Backtrace analysis found this bug to be similar to bug #678532, closing as duplicate.

Bugs which were found to be similar to this bug: bug #596476, bug #603659, bug #603837, bug #610475, bug #630521, bug #634836, bug #653427, bug #662464, bug #665349, bug #678532

This comment is automatically generated.

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