Bug 716449

Summary: [abrt] darktable-0.8-8.fc14: Process /usr/bin/darktable was killed by signal 4 (SIGILL)
Product: [Fedora] Fedora Reporter: Dave B <freddog_de>
Component: darktableAssignee: Edouard Bourguignon <madko>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: madko
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:29e7b3cbf2408e029a83308ea6a2efe7e20be0d9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-24 21:52:09 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 Dave B 2011-06-24 13:43:46 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 88980 bytes
cmdline: /usr/bin/darktable
component: darktable
Attached file: coredump, 513388544 bytes
executable: /usr/bin/darktable
kernel: 2.6.35.13-92.fc14.x86_64
package: darktable-0.8-8.fc14
rating: 4
reason: Process /usr/bin/darktable was killed by signal 4 (SIGILL)
release: Fedora release 14 (Laughlin)
time: 1308922561
uid: 500

comment
-----
Opened Darktable, click on a .cr2 image, after a few seconds get error message & darktable closes itself down.  Next time I try to start Darktable, it trys again to load the same .cr2 with the same result.

Only way I've found to get out of this is to yum erase darktable, and then remove the 3 hidden darktable files.  Then to reinstall darktable.

How to reproduce
-----
1.
2.
3.
Trying to open a raw image.
Comment 1 Dave B 2011-06-24 13:43:49 UTC 
Created attachment 509761 [details]
File: backtrace
Comment 2 Edouard Bourguignon 2011-06-24 21:52:09 UTC 

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