https://bugzilla.novell.com/show_bug.cgi?id=344534
Summary: provide also scanner testing via "scanimage -d...
>/dev/null" in yast2-scanner
Product: openSUSE 11.0
Version: unspecified
Platform: All
OS/Version: openSUSE 10.3
Status: ASSIGNED
Severity: Enhancement
Priority: P5 - None
Component: Other
AssignedTo: jsmeix@novell.com
ReportedBy: jsmeix@novell.com
QAContact: qa@suse.de
Found By: Development
Currently the scanning test in yast2-scanner is done via
"scanimage -d... -T" but there are possible problems,
see this (shortended) mail:
-------------------------------------------------------------------------
Date: Tue, 20 Nov 2007 08:01:05 -0500
From: m. allan noah ...
To:
On Nov 19 15:38 m. allan noah wrote (shortened):
why are you trying to use the -T?
I thought "scanimage -d... -T" is the right way to do a test?
I use it in the YaST scanner config tool to provide a [Test] option for the user to test if his scanner/backend combination works.
Should I better use "scanimage -d... >/dev/null" for a test?
the -T test just tries using a variety of buffer sizes during the data transfer, followed by a cancel (instead of completing the scan) IIRC. This might put some scanners/backends into a funk, as they dont properly implement the cancel. i would not assume that every scanner/backend combination will act properly with -T. ------------------------------------------------------------------------- Up to now I don't know about any report that the current test in yast2-scanner had such bad consequences but to be safe I like to provide both kind of tests in yast2-scanner. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.