Bug 670068

Summary: [abrt] simple-scan-2.32.0-1.fc14: sane_genesys_open: Process /usr/bin/simple-scan was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Eric Work <work.eric>
Component: simple-scanAssignee: Rahul Sundaram <metherid>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: metherid
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:34ead1050999592dcc9659a6739c442b09d3af04
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 17:30:46 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 Eric Work 2011-01-17 04:13:36 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: simple-scan
component: simple-scan
crash_function: sane_genesys_open
executable: /usr/bin/simple-scan
kernel: 2.6.35.10-74.fc14.x86_64
package: simple-scan-2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/simple-scan was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295236820
uid: 500

comment
-----
I have a Brother DSmobile 600 scanner.  It's a clone of the Pentax DSmobile 600.  It works with the scanimage CLI program and also gimp using xsane.  This leads me to believe that sane is setup properly.

$ sane-find-scanner
found USB scanner (vendor=0x04f9 [Brother], product=0x2038 [DSmobile 600], chip=GL842?) at libusb:002:002

$ scanimage -L
device `genesys:libusb:002:002' is a Pentax DSmobile 600 flatbed scanner

sane-backends-1.0.21-5.fc14.x86_64
sane-backends-libs-1.0.21-5.fc14.x86_64
sane-backends-libs-gphoto2-1.0.21-5.fc14.x86_64
xsane-common-0.998-1.fc14.x86_64
xsane-gimp-0.998-1.fc14.x86_64
simple-scan-2.32.0-1.fc14.x86_64

How to reproduce
-----
1. Start simple-scan
2. Tried to do a scan
3. Seg fault
Comment 1 Eric Work 2011-01-17 04:13:38 UTC 
Created attachment 473755 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 17:30:46 UTC 
Backtrace analysis found this bug to be similar to bug #660352, closing as duplicate.

Bugs which were found to be similar to this bug: bug #591752, bug #596678, bug #612390, bug #615282, bug #630353, bug #660352, bug #692630

This comment is automatically generated.

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