Bug 984631
Summary: | Xsane Can't Recognize Scanner | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | KitchM <tech> |
Component: | xsane | Assignee: | Nils Philippsen <nphilipp> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | nphilipp, tech |
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: | 2013-11-14 11:04:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
KitchM
2013-07-15 15:15:43 UTC
Any ideas on getting xsane fixed? I just received an update thru yumex today, so I shutdown, turned on the scanner and rebooted. Upon selecting xsane, it readily opened gimp with the Umax interface showing. However, when I selected to scan, the program froze. I then tried simple scan and it could not find the scanner. This still needs work. Please help. Just tried with latest kernel. Still no joy. This doesn't seem to be a bug in the xsane frontend, the backend (driver) side is dealt with in bug #1028549. Closing this one. |