Hi Markus,
Thank you for your reply.
Yes, the users I was running scanimage/xsane from were members of the machine scanner
group - I'm sorry I forgot to mention that. All files in /etc/sane.d and /usr/share/sane
are owned by root:root and have 644 permissions (755 for directories), as far as
Hi JM,
On 21.01.2018 13:13, ripero84 wrote:
Hello,
Apologies if this is the wrong list to ask for help with this issue.
feel welcome
I have an old Agfa SnapScan 1212u which was working fine when connected to an
old computer A. A debian dist-upgrade went wrong on A, and all my attempts
Hello,
Apologies if this is the wrong list to ask for help with this issue.
I have an old Agfa SnapScan 1212u which was working fine when connected to an old computer
A. A debian dist-upgrade went wrong on A, and all my attempts to scan since then have failed.
So far I have tried to scan
-BEGIN PGP SIGNED MESSAGE-
Hello!
I have a box with Kernel 2.4.17 (hotplugged with agfafirm) and sane 1.0.14.
To control the scanner I'm using the scanner.o module. With libusb happens
the same...
The point is: when I take a few gray scans all is working fine. In color mode
the first
Hi,
there's a known bug in the snapscan backend of sane-1.0.14 that results in
red scans when using libusb. I'm not sure if the bug also shows up when
using the scanner module. See http://alioth.debian.org/tracker/index.php?
func=detailaid=300753group_id=30186atid=410366 for more details.
The
