Bug 832647
| Summary: | [abrt] simple-scan-3.4.1-1.fc17: Process /usr/bin/simple-scan was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Nowak <mnowak> | ||||||||
| Component: | simple-scan | Assignee: | Rahul Sundaram <metherid> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | bugzilla-redhat, hugh, i39d13bf, metherid, nicolas.gif, ohudlick, santiagobear | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:4253a35437e79d3ef59ca14c4712226860d89805 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-01 04:48:02 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
Michal Nowak
2012-06-16 09:27:44 UTC
Created attachment 592295 [details]
File: maps
Created attachment 592296 [details]
File: dso_list
Created attachment 592297 [details]
File: backtrace
Just scanning from a network Hp scanner backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I was scanning some notes from a friend. When finished one bundle, I saved it as a multipage PDF. Then I started a new file to scan the next bundle. The first page scans without any problems, but after initiating the second page, Simple-Scan quits and the scanner stopped scanning without returning the scanbar to its initial position. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Multiple page scan, started sencond page, and exited. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Scanning multiple documents. Had just saved and then New. Started scanning and simple-scan window just disappeared about 10% into the scan. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Just crashed when trying to scan a second document. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Scaning all pages from feeder, text, custom page crop. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Scaned one more package after the previous. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Upped the text resolution of text to 300dpi, scanned 6 pages, divided among 4 documents, of which two were single-page, and one was a three-page document, and saved to disc. As I was scanning the second page of a three-page document (the 7th page scanned), Simple Scan crashed. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) It crashes every time between the end of a job and the beginning of the next backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) While scanning a page simple-scan crashed. backtrace_rating: 4 Package: simple-scan-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I got this one too. I had finished a scan, saved the document, and started another. It crashed with the double-free after starting (and perhaps finishing) scanning the first page. A couple of minutes ago I experienced https://bugzilla.redhat.com/show_bug.cgi?id=831481 I presume this is the same bug (also a double-free). Interestingly, Automatic Bug Reporting Tool took me to these two different bz entries for two different crashes, even though they look the same to me. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |