Hi,
having the same issue here I found out that the rule in
/lib/udev/rules.d/99-saned.rules should set the GROUP to "scanner" rather than
"saned"
e.g. replace
ENV{libsane_matched}=="yes", GROUP="saned"
by
ENV{libsane_matched}=="yes", GROUP="scanner"
It solve the problem on my system.
--
You re
Remote access does not work as well e.g. by using the Windows client
SaneTwain
I'm uncertain if this is related to previuos issue. But it worked in
Ubuntu 16.04.
Error message in syslog is:
Mar 17 08:18:00 my-desktop saned[26802]: saned (AF-indep+IPv6) from
sane-backends 1.0.27 starting up
Mar
Finally, the following is what works for me:
It seems that there is the need to change users to root at several
places:
1. /etc/scanbd/scanbd.conf
Change user so that it is 'root' instead of 'saned'
# drop priviliges to this user
#=
# Linux (m
I made the next step.
After I have changed the user from saned to root in scanbd.conf I am
able to start scanbd and it starts polling the usb device.
scanbd.conf looks like this now:
# drop priviliges to this user
#=
# Linux (most distributions use the saned user):
#
I've just tried to configure scanbd under Ubuntu 18.10 and ran into same
trouble.
Scanner device is available:
# scanimage -L
device `plustek:libusb:002:007' is a Canon CanoScan LiDE25 flatbed scanner
But after starting scanbd it terminates with message that it is not
available:
# scanbd -f -d 7
Thank you for your report and sorry for your troubles. The Debian bug
you referenced is not what you are experiencing, though, since Chris
confirmed this was gone in the package that was eventually uploaded as
1.4.4-2
** Changed in: scanbd (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: scanbd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747115
Title:
sca