Glad I could help. Unfortunately, the epson2 backend is supposed to be a replacement for epson, so I'd like to get to the bottom of this, if you have the time? Should not be very complicated to get a log of where epson2 goes wrong...
allan On Wed, Jun 9, 2010 at 10:27 PM, Richard C. Steffens <rsteff at comcast.net> wrote: > m. allan noah wrote: >> >> It is possible that there is a problem with the sane backend used to >> talk to the scanner. What is the output of the command >> sane-find-scanner, run as root? >> > > found SCSI scanner "EPSON Perfection600 V2.4" at /dev/sg2 > >> If it shows a line containing epson2, you could try editing >> /etc/sane.d/dll.conf, and '#' the epson2 line, and remove any '#' in >> front of the epson line, and try scanning again. >> > > Even though the above output does not contain epson2 I followed up on your > idea and did switch dll.conf so that epson is uncommented and epson2 is > commented. That solved my problem. > > Thank you very much! > > -- > Regards, > > Dick Steffens > > > -- "The truth is an offense, but not a sin"
