Bug 135174
| Summary: | sane-hp crashes when there are USB errors | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alan Cox <alan> |
| Component: | sane-backends | Assignee: | Nils Philippsen <nphilipp> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | mattdm |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-07-28 14:04:03 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: | |||
|
Description
Alan Cox
2004-10-09 18:53:00 UTC
Changing arch to x86-64... does this happen on x86 too? I've not seen it occur on the x86-32 box yet Is there a stack trace? What SANE-aware application are you using? Try setting SANE_DEBUG_HP=255 to see if there's more information we can get prior to the crash. I didn't get a trace (was just the log). I've had a play with this and I found out a lot more. It only crashes using USB, it only crashes when the USB logs a collection of failures. Looks like its some kind of intolerance to errors. It isn't a 32/64bit problem - I just happened to use SCSI on the 32bit. Please attach what you have. Thanks. The logged segfault is all I have (its from dmesg segfault logging by the kernel) Alan, I don't even know what application you're running. :-) Try setting SANE_DEBUG_HP=255, and run 'scanimage'. It ws running "xsane" when it crashed. Its now plugged into a production system via scsi so the earliest I can try USB again is probably late october. Without debug info it's hard to say very much about this. Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! |