Bug 669361

Summary: [abrt] xsane-0.998-1.fc13: strlen: Process /usr/bin/xsane was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: igraszka <i-graszka>
Component: xsaneAssignee: Nils Philippsen <nphilipp>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: nphilipp
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7cc424672f24a4c6b153481c219a6610c01b3363
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-31 11:06:58 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 igraszka 2011-01-13 13:30:56 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: xsane
comment: This occures everytime i want to scan more than one page using gscan2pdf or xsane, especially when i want to save scanned images.
component: xsane
crash_function: strlen
executable: /usr/bin/xsane
kernel: 2.6.34.7-66.fc13.i686
package: xsane-0.998-1.fc13
rating: 4
reason: Process /usr/bin/xsane was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1294923770
uid: 500

How to reproduce
-----
1. while using xsane and gscan2pdf
2. after few pages the programme crashed
3. nothing has been saved and programme turned off

Comment 1 igraszka 2011-01-13 13:31:02 UTC
Created attachment 473320 [details]
File: backtrace

Comment 2 Bug Zapper 2011-05-30 11:56:39 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 3 Nils Philippsen 2011-05-31 11:06:58 UTC
Seems like a duplicate of bug #655613 to me.

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