It seems that when 'saned' processes a cancel request, it immediately
closes the connection back to the net backend. This leaves the
frontend (and net backend) confused and stalled.
I don't see why it should close the connection at all -- it's still
valid for the frontend to ask for a new scan, change options, etc.,
after a scan is KO'ed.
(Sorry I don't have time to delve into this deeper right now (i.e.
this week and next), but someone else might have fun poking around...)
-matt m.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com