Bug 660352 - [abrt] simple-scan-2.32.0-1.fc14: init_options: Process /usr/bin/simple-scan was killed by signal 11 (SIGSEGV)
Summary: [abrt] simple-scan-2.32.0-1.fc14: init_options: Process /usr/bin/simple-scan ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: simple-scan
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8ca4360b807f7b98057453bcdcb...
: 670068 692630 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-06 16:18 UTC by Bug Reporter
Modified: 2012-08-16 19:26 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 19:26:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (110.18 KB, text/plain)
2010-12-06 16:19 UTC, Bug Reporter
no flags Details

Description Bug Reporter 2010-12-06 16:18:42 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: simple-scan
component: simple-scan
crash_function: init_options
executable: /usr/bin/simple-scan
kernel: 2.6.35.9-64.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: 1291652041
uid: 500

How to reproduce
-----
1.I changed several options
2. I closed the option window
3. The programme crashed

Comment 1 Bug Reporter 2010-12-06 16:19:00 UTC
Created attachment 465011 [details]
File: backtrace

Comment 2 Bug Reporter 2010-12-06 16:20:04 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I started the scan.
2. the programme crashed
3.

Comment 3 Stefan Hellermann 2010-12-30 20:09:27 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Start Simple-Scan
2. See it crashing :-(
3.

Comment 4 myemail 2011-01-11 21:13:24 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.scan image using simple scan
2. 
3.


Comment
-----

Comment 5 Scott Marshall 2011-01-20 05:04:21 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Attempted scan using Canon LIDE 50 USB scanner
2.
3.

Comment 6 arild 2011-02-13 12:49:00 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Star "Simple Scan"
2. Click "Scan" (Photo mode)

Comment 7 Scott Marshall 2011-03-06 00:59:59 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Plugged in Canon LIDE-50 scanner (USB)
2. Loaded "Simple Scan" application
3. Checked Preferences: Source=Canon LiDE 35/40/50, TextRes=600dpi, PhotoRes=600dpi, ScanSide=Front, PageSize=A4
4. Scan > Single Page (Photo)

Comment 8 Scott Marshall 2011-03-06 01:01:14 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Plugged in Canon LIDE-50 scanner (USB)
2. Loaded "Simple Scan" application
3. Checked Preferences: Source=Canon LiDE 35/40/50, TextRes=600dpi, PhotoRes=600dpi, ScanSide=Front, PageSize=A4
4. Scan > Single Page (Text)

Comment 9 Scott Marshall 2011-03-06 01:29:53 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. The same as prevously (Canon LiDE 50 USB scanner)
2. This time, the locking switch was disengaged - previously the locking switch on the scanner was active.
3. Otherwise, same settings as before (clicked the SCAN) button after selecting "Text" mode.
4. ABRT generates a different crash-dump entry, rather than incrementing the previous crash count.

Comment 10 Scott Marshall 2011-03-06 22:55:32 UTC
Package: simple-scan-2.32.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Upgraded to new SANE backends (now running with v1.0.21-6-x86_64-fc14)
2. Tried another scan from Canon LiDE 50
3. Same result - another SIGSEGV crash in simplescan.


Comment
-----
SANE packages are now as follows:
sane-backends.x86_64 0:1.0.21-6.fc14             
sane-backends-libs.x86_64 0:1.0.21-6.fc14        
sane-backends-libs-gphoto2.x86_64 0:1.0.21-6.fc14

Simple Scanner package is still:
simple-scan-2.32.0-1.fc14.x86_64

Comment 11 abrt-bot 2012-03-21 17:30:46 UTC
*** Bug 670068 has been marked as a duplicate of this bug. ***

Comment 12 abrt-bot 2012-03-21 17:30:56 UTC
*** Bug 692630 has been marked as a duplicate of this bug. ***

Comment 13 Fedora End Of Life 2012-08-16 19:26:50 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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