Bug 611881
| Summary: | [abrt] crash in xsane-0.997-8.fc13: e2_setup_block_mode: Process /usr/bin/xsane was killed by signal 8 (SIGFPE) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | info <info> | ||||||||
| Component: | xsane | Assignee: | Nils Philippsen <nphilipp> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 13 | CC: | nphilipp | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | abrt_hash:312562977f3e83a61e61cb161d98b7dcf36e934d | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-03-07 18:16:33 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
info@kobaltwit.be
2010-07-06 18:54:36 UTC
Created attachment 429857 [details]
File: backtrace
Would you please attach the device settings file /home/goudsmid/.sane/xsane/EpsonCalibrated to this ticket? Please also check, if the issues remains if you move away your complete XSane settings, e.g. rename ~/.sane/xsane to something else, then check again. Thanks. Package: xsane-0.997-8.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Same as my previous report, except I removed .sane directory first Sorry, my previous comment was the result of Abrt. I tried again after I removed the .sane directory, and can crash xsane in pretty much the same way. It may be useful to know the crash only happens with my Epson Perfection 3200 Photo, and not with the scanner in my HP Color Laserjet CM2320. Do you want me to attach the new backtrace as well ? Well, if it's significantly different it might be worthwhile. If you don't know, just attach it, I'll sort it out whether I need it or not ;-). Created attachment 430469 [details]
Backtrace from clean xsane run
The above backtrace is from the clean run (with .sane moved out of the way). I'll let you decide if it contains additional valuable information.
Thank you for analysing this. Xsane is rather important in our workflow here.
Created attachment 430545 [details]
Config file used with xsane
Attached is my EpsonCalibrated.drc file, which is used in when the first backtrace was generated.
I noticed sane-backends comes with two possible backends for Epson scanners: epson and epson2. I tried both of them. Only epson2 is susceptible to the crash.
Also, with the old .sane in place and using the configuration file, the crash seems to happen much more often. Usually the first or second time I set a scan area in the preview window, xsane bails out. With a fresh .sane directory, not using the custom configuration file, I usually have to set the scan area multiple times in a row before it crashes. This is not scientifically established though, just my impression.
Hopefully that helps narrow down the bug location.
Note: although the epson driver seems to work with my scanner, it doesn't give good scan results and the preview is dog slow. Fixing epson2 is definitely a better solution here.
If there is anything more I can do to help you fix this, please let me know.
This bug has been fixed with the xsane updates a couple of days ago. These updates were to fix bug 671534, so I'll mark this one as a duplicate. *** This bug has been marked as a duplicate of bug 671534 *** |