Bug 615282 - [abrt] crash in simple-scan-1.0.2-1.fc13: init_options: Process /usr/bin/simple-scan was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in simple-scan-1.0.2-1.fc13: init_options: Process /usr/bin/simp...
Keywords:
Status: CLOSED DUPLICATE of bug 630353
Alias: None
Product: Fedora
Classification: Fedora
Component: simple-scan
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:36e7212774df697a9ecec3dbd51...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-16 10:57 UTC by jojo
Modified: 2010-11-09 16:52 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:52:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (84.52 KB, text/plain)
2010-07-16 10:57 UTC, jojo 		no flags Details
View All

Description jojo 2010-07-16 10:57:35 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: simple-scan
comment: I just use my scanjet G2410 to scan a photo via simple scan and when i push scan button the crash happen .
component: simple-scan
crash_function: init_options
executable: /usr/bin/simple-scan
global_uuid: 36e7212774df697a9ecec3dbd516682c73675f6a
kernel: 2.6.33.6-147.fc13.x86_64
package: simple-scan-1.0.2-1.fc13
rating: 4
reason: Process /usr/bin/simple-scan was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.use hp scanjet G2410
2.open simple scan
3.use scan button and hopa crash happen ..
Comment 1 jojo 2010-07-16 10:57:46 UTC 
Created attachment 432355 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:52:31 UTC 

*** This bug has been marked as a duplicate of bug 630353 ***
Comment 3 Karel Klíč 2010-11-09 16:52:31 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #630353.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.