Bug 984631 - Xsane Can't Recognize Scanner
Summary: Xsane Can't Recognize Scanner
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xsane
Version: 19
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-15 15:15 UTC by KitchM
Modified: 2013-11-14 11:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-14 11:04:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.