[sane-devel] Erratic connection of frontends to scanner

[Alisdair]

Oliver, I think you may have cracked it.

Snape20.bin permissions were "-rw------- 1 root".
I went "chmod o+rx-w Snape20.bin" so they are now "-rw----r-x".
Xsane was immediately able to shake hands with the scanner from a user desktop.

I'm still not sure why this problem seemed to correct itself - it started straight after I
loaded the new firmware file, but dissappeared suddenly, only to reappear two days later!

Thanks again (here's hoping!)


Alisdair :-)



Oliver Schwartz wrote:
 > Hi,
 >
 > now we're getting somewhere...
 >
 >
 >>Right now scanimage returns:
 >>	[snapscan] Cannot open firmware file
 >>/usr/local/etc/sane.d/Snape20.bin [snapscan] Edit the firmware file
 >>in snapscan.conf
 >
 >
 > Obviously your firmware file entry in snapscan.conf points to
 > /usr/local/etc/sane.d/Snape20.bin, but the file cannot be read by the
 > backend. So make sure you really copied the file to that directory
 > and that the file is world-readable. The filename is case sensitive.
 >
 > Oliver
 > _______________________________________________
 > Sane-devel mailing list
 > Sane-devel@www.mostang.com
 > http://www.mostang.com/mailman/listinfo/sane-devel
 >
 > .
 >