Bug 97408 - xsane hangs about 1" into scan preview on hp scanjet 5300c usb
Summary: xsane hangs about 1" into scan preview on hp scanjet 5300c usb
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-14 20:14 UTC by Patrick
Modified: 2007-04-18 16:54 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:41:08 UTC
Embargoed:


Attachments (Terms of Use)

Description Patrick 2003-06-14 20:14:43 UTC
Description of problem:

When I do a scan to preview the contents of the scan area using xsane, the
program *always* freezes at approximately 1" from the top of the scan preview
area. My scanner is an hp scanjet 5300c with a usb connection.

I have noticed inconsistencies with the 'readiness' of the scanner as well.
Doing a hard reboot seems to reset the scanner into a working state again in
this case. As a result I suspect a problem in the scanner kernel module rather
than in xsane. However, this may be related to the fact that I have to kill the
program and it cannot reset the scanner to a proper state as a result.

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

xsane 0.89-3
sane-backends 1.09-5

How reproducible:

Every time.

Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:

Comment 1 Tim Waugh 2003-06-24 15:19:58 UTC
This doesn't seem to be a particularly well-supported scanner, from a quick search.

Comment 2 Bugzilla owner 2004-09-30 15:41:08 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



Note You need to log in before you can comment on or make changes to this bug.