I just did a few successful scans! The patch does indeed make the scanner work,
with two caveats:
1) Only every other call to scanimage results in a successful scan, the 2nd,
4th, 6th, etc scan fails the same way as before.
2) Even during successful scans the debug output contains an 'Error duri
Anyone seen this?
Dec 31 19:00:26 raspberry-pi dbus-daemon: Encountered error 'Error in file
/etc/dbus-1/system.d/scanbd_dbus.conf, line 4, column 25: not well-formed
(invalid token)#012' while parsing '/etc/dbus-1/system.d/scanbd_dbus.conf'
--
View this message in context:
http://sane.10972.
Assembled Wisdom!
I am sure that this question has a simple answer. My situation:
I bought a Canon imageCLASS MF4770n all-in-one
printer(scanner/copier/fax) on Friday. It took me a while to get
my CUPS and lpadmin commands so that it would print, but thanks
to the documentation provided by Canon
I have attached a minor patch to the backend. The idea is to send
commands in the same order as the windows driver, starting with get
hardware status. If this does not fix it, I will move on to set
window, which looks like it should be after the initial coarse
calibration payload.
allan
On Mon, M
Hmm- the scanner is upset that we tried to send window data. Perhaps
it wants some other command to be sent first. I will look at your pcap
again and come up with a patch
allan
On Mon, Mar 16, 2015 at 3:30 AM, Jonas Neubert wrote:
> I believe all debug output I sent so far (both SANE and Windows
I believe all debug output I sent so far (both SANE and Windows) was with
300dpi setting, for scanimage it's the default value for the --resolution
option in the output of 'scanimage -h'. Anyway, ran it again, this time with
resolution and mode options explicitly set, still same behavior, see de
