[sane-devel] help compiling sane

Rafe DiDomenico rafe101 at gmail.com
Tue Mar 10 08:26:00 UTC 2015

Thanks again, all, for trying to help me with this.

I started fresh with sane by uninstalling the packages and cleaning out
the sane locations in /usr/lib and /etc. I can confirm that the backend
is 1.0.25git. I checked the genesys.conf and the LIDE 220 is there. I
also made an entry for the udev rules for it to match the product ID.

I am attaching a log gathered while root. Without still
shows some permission problems I haven't straightened out yet, but the end result is no different with

On 03/08/2015 09:29 PM, Stef wrote:
> On 08/03/2015 11:36, Rafe DiDomenico wrote:
>> So, I did dump all the conf files in a folder and reinstalled. The
>> genesys.conf does have a 220 entry now, but I still can't get any
>> further:
>> scanimage (sane-backends) 1.0.25git; backend version 1.0.25
>> found USB scanner (vendor=0x04a9, product=0x190f, chip=GL848+?) at
>> libusb:002:002
>>   # Your USB scanner was (probably) detected. It may or may not be
>> supported by
>> No scanners were identified. If you were expecting something different,
>> check that the scanner is plugged in, turned on and detected by the
>> sane-find-scanner tool (if appropriate).
>     Hello,
>     are your udev rules updated ? I had to manually update
> 80-libsane.rules to have this new scanner handled by udev. You could
> try to run scanimage -L as root to check if it is permission problem.
>     If not, run scanimage -L with debug traces by exporting the
> following environment variables:
> scanimage -L 2>probe.log
> And send us the probe.log file.
> Regards,
>     Stef

-------------- next part --------------
A non-text attachment was scrubbed...
Name: probe (root).log
Type: text/x-log
Size: 53385 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20150310/38c7fbe3/attachment-0001.bin>

More information about the sane-devel mailing list