Bug 984631

Summary: Xsane Can't Recognize Scanner
Product: [Fedora] Fedora Reporter: KitchM <tech>
Component: xsaneAssignee: Nils Philippsen <nphilipp>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: 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
Description of problem: A hardware check of the system shows the SCSI card now, and sees the unclaimed Umax scanner.  However, nothing claims it and Xsane does not see it.


Version-Release number of selected component (if applicable):latest


How reproducible:Everytime


Steps to Reproduce:
1.Boot computer and turn on scanner
2.Log in with latest kernel
3.Select xsane

Actual results:
No scanner found

Expected results:
Umax scanner found

Additional info:

Comment 1 KitchM 2013-07-25 14:50:27 UTC
Any ideas on getting xsane fixed?

Comment 2 KitchM 2013-07-26 16:13:40 UTC
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.

Comment 3 KitchM 2013-11-08 18:20:56 UTC
Just tried with latest kernel.  Still no joy.

Comment 4 Nils Philippsen 2013-11-14 11:04:04 UTC
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.