Bug 617736

Summary: [abrt] shotwell-0.5.2-1.fc14: Process /usr/bin/shotwell was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Matt Hooper <matthew.hooper>
Component: shotwellAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:58f43db453625e2c559830c5ad66750b30ce3111
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-17 14:39:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Matt Hooper 2010-07-23 20:15:46 UTC 
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: shotwell file:///media/1TB_Not_RAID/2010-07-23_02_22_53_BST__0001/image_foremost_output/jpg
component: shotwell
executable: /usr/bin/shotwell
global_uuid: 58f43db453625e2c559830c5ad66750b30ce3111
kernel: 2.6.35-0.49.rc5.git2.fc14.x86_64
package: shotwell-0.5.2-1.fc14
rating: 0
reason: Process /usr/bin/shotwell was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Rawhide)
time: 1279915966
uid: 500

comment
-----
Attempted to import a folder containing 8732 recovered files, believed to be JPG's, that may be corrupt. Nautilus had already crashed with this folder (see bug #617735).
Comment 1 Matt Hooper 2010-07-23 20:15:49 UTC 
Created attachment 434057 [details]
File: backtrace
Comment 2 Bug Zapper 2010-07-30 12:48:12 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Matthias Clasen 2010-08-17 14:39:41 UTC 

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