Page MenuHomeSolus

sane-backends
Closed, ResolvedPublic

Description

This enables my scanner to actually work on Solus.

Related Objects

StatusSubtypeAssignedTask
Spiteikey
Resolvedikey

Event Timeline

I tried this @blaz, adding hpaio to dll.conf, and still no luck. It seems to be more of a device discovery problem I'm having. After adding the line and rebooting it still doesn't see it. I tried 'sane-find-scanner' and it only sees my webcam, not the scanner.

Normally the aio shows up as /dev/usb/lp0, which sane seems to ignore. So I've tried adding udev rules to see if sane could find it. Most of what I've read states udev should create a 'scanner0' for scanners, so I made a rule in /etc/udev/rules.d/sane-rules:

ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="c111", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes", SYMLINK+="scanner0"

I've tried it with the 'SYMLINK' part pointing to /dev/usb and /dev, neither work. Tried it without the 'SYMLINK' part, letting udev decide where to put it, still nothing. Hotplugging, rebooting, doesn't matter.

udev creates the device links when I explicitly name them with the symlink, but doesn't when I don't, or at least not one I can find. I'm thinking that udev sees the idVendor and idProduct are the same as for the printer so it just creates /dev/usb/lp0 and adds it to the scanner user group. I created the group, added myself to it and the usb group, still nothing. Sane just does not see it, only the webcam.

Think ikey was right, sane is anything but. They should have named it "insane".

Right now I'm totally out of ideas.

DataDrake raised the priority of this task from Normal to High.Sep 15 2016, 4:41 AM
ikey raised the priority of this task from High to Unbreak Now!.
ikey added a subscriber: ikey.

P1 - merge tonight.