abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: xsane comment: I can scan sometimes 5-6 pages before a crash and sometimes a crash happens after the first page. component: xsane crash_function: gt68xx_line_reader_free_delays executable: /usr/bin/xsane kernel: 2.6.34.6-47.fc13.x86_64 package: xsane-0.997-10.fc13 rating: 4 reason: Process /usr/bin/xsane was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1284354696 uid: 500 How to reproduce ----- 1. Launch xsane 2. Start a multiple page scan to PDF 3. After one or more pages are scanned and saved xsane crashes
Created an attachment (id=447156) File: backtrace
What exact scanner model do you use? Changing component to sane-backends as the crash happens in the scanner driver.
Additionally, please run xsane with debugging enabled for your scanner driver and attach the output, e.g. run this command: env SANE_DEBUG_GT68XX=4 xsane >/tmp/xsane-debug.out 2>&1 Then do whatever you did to make the application crash and attach the file /tmp/xsane-debug.out to this report. Thanks.
Created attachment 447329 [details] Output of running 'SANE_DEBUG_GT68XX=4 xsane >/tmp/xsane-debug.out 2>&1'
Created attachment 447330 [details] Output of 'lsusb -vv'
I just attached the debug output and the output of lsusb -vv to the bug. The scanner is Genius CP-SF600 (I can't find the product page on the Genius' website so here's the one at Newegg - http://www.newegg.com/Product/Product.aspx?Item=N82E16838274001 ).
Just one more comment when I ran xsane with the debug option set the crash happened after the second page was scanned.
*** Bug 642070 has been marked as a duplicate of this bug. ***
Just one more note. I upgraded yesterday to Fedora 14 and can reproduce the bug there as well. Will attach the debug output again.
Created attachment 457580 [details] Debug output from Fedora 14
I'll keep this one and the other bug #653687 open to track this issue for F-13, F-14, but will keep discussion etc. here (for context). Unfortunately I don't have the hardware to test this, but meanwhile upstream release a new version (0.998) which is available in Fedora now. Please check whether you can reproduce this issue on this updated version. Thanks!
I just tested the new version 0.998 and I still got the crash.
A new upstream version with many bugfixes and enhancements has been released. Please check whether you issue persists with this updated package: https://admin.fedoraproject.org/updates/sane-backends-1.0.22-1.fc13
(In reply to comment #13) I updated all of the Sane related packages with the latest available updates in the updates-testing repository but still had a crash. These are the packages that got updated (I'm running Fedora 14 now): sane-backends-1.0.22-1.fc14.x86_64 sane-backends-libs-1.0.22-1.fc14.x86_64 hplip-common-3.11.3a-1.fc14.x86_64 hplip-libs-3.11.3a-1.fc14.x86_64 1:hpijs-3.11.3a-1.fc14.x86_64 xsane-common-0.998-3.fc14.x86_64 xsane-0.998-3.fc14.x86_64 hplip-3.11.3a-1.fc14.x86_64 libsane-hpaio-3.11.3a-1.fc14.x86_64 sane-backends-libs-1.0.22-1.fc14.i686
*** Bug 693828 has been marked as a duplicate of this bug. ***
I uploaded the new backtrace in the new bug and marked it as a duplicate of the current one.
I'll leave this here then: Attachment #490034 [details]
*** Bug 662817 has been marked as a duplicate of this bug. ***
I've writte a patch which makes one of the affected functions a little more robust so the crash shouldn't happen with it. There are some irregularities in the debug output above which I'd like to look at before making this an official update (and the fix of course needs to be verified). Would you please download the scratch packages with the patch which I have built from koji and try them? You can find the builds for your architecture (I've built x86_64 and i686) on the page for the appropriate buildArch dependent task linked from here (for a while -- I don't know right now how often scratch builds get deleted): http://koji.fedoraproject.org/koji/taskinfo?taskID=2997594 Please install the appropriate packages on your system and recreate the debugging output this way: 'SANE_DEBUG_GT68XX=5 xsane >/tmp/sane-gt68xx-debug.out 2>&1' Or like this if you happen to use simple-scan: 'SANE_DEBUG_GT68XX=5 simple-scan >/tmp/sane-gt68xx-debug.out 2>&1' Then attach the resulting file /tmp/sane-gt68xx-debug.out to this bug report. Thanks!
Created attachment 491839 [details] Debug output. Attached is the new output. With the new backend packaged the backend doesn't crash, but the scanner still fails to continue scanning (see line 19858). xsane still works but when you try to scan the next page you get an error message box: "Failed to start scanner: Invalid argument". It's quite an improvement though since simply restarting xsane works fine while before I had to unplug and reconnect the USB cable before I could continue and all of the settings were lost.
*** Bug 719986 has been marked as a duplicate of this bug. ***
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information. Bugs which were found to be similar to this bug: xsane: bug #572041, bug #642070, bug #653687, bug #662817, bug #693828, bug #719986 This comment is automatically generated.
The bugs above are not only similar but they are probably the same ones as each of them have been filed by me and are either marked as duplicates of the current one or have been closed due to the fact that they were filed against an older Fedora release. And just to update, I still have the crashes even with the latest packages on Fedora 16: libksane.x86_64 4.8.1-1.fc16 @updates libsane-hpaio.x86_64 3.12.2-3.fc16 @updates sane-backends.x86_64 1.0.22-8.fc16 @updates sane-backends-drivers-cameras.x86_64 1.0.22-8.fc16 @updates sane-backends-drivers-scanners.x86_64 1.0.22-8.fc16 @updates sane-backends-libs.i686 1.0.22-8.fc16 @updates sane-backends-libs.x86_64 1.0.22-8.fc16 @updates xsane.x86_64 0.998-4.fc16 @anaconda-0 xsane-common.x86_64 0.998-4.fc16 @anaconda-0
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