-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2010-12-05 01:55, Julien BLACHE wrote:
> Olaf Meeuwissen <olaf.meeuwis...@avasys.jp> wrote:
>> For some reason the device is saying that it received a cancel request
>> (did someone push a cancel button on the device?). Protocol-wise, the
>> backend is supposed to send a CAN in that case before anything else.
>
> Looks like one or both of
> 506c1be1a4252e9b640bd966869f8f68830d78c0
> 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955
> could be at fault here.
The former doesn't seem to be at fault.
The latter only goes part of the way. In case of an FSG_STATUS_FER or
FSG_STATUS_NOT_READY one should not request any image data anymore and
that is what the backend seems to be doing. However, in case you get an
FSG_STATUS_CANCEL_REQ you have to send a CAN. The backend only sets the
SANE_STATUS_CANCELLED flag and returns. As a result e2_scan_finish gets
called but that doesn't send a CAN.
Obviously, e2_scan_finish cannot know that it should. So I'd make
e2_ext_read send the CAN (by calling e2_cancel) before it returns
SANE_STATUS_CANCELLED.
> If someone with hardware access could look into this and report back,
> that'd be great.
I'll have a look at the logs Soren sent.
- --
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkz8JJYACgkQt5qrxaZLMnIHzgCfSQ3kheFvnAHu7jnugjqbWdNw
xHcAnjwQAgONZYF7KCu3jvpYWF01iXrq
=eg4R
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
