[NTLUG:Discuss] Scanner issues (and partial solution to Scanners on Suse 10.x)

[Stephen Davidson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings.

Getting this scanner working has been a slow & painful process, but I
have been making progress.  Found some hints at;
http://www.linux.com/feature/57798

The solution so far;
"Presetup"
Make sure scanner is working on server for the root user, and that
xinitd is configured to accept incoming sane connections.  The above
link can be helpful for this part, especially for configuring xinitd if
you don't have SuSE Yast2 for quick configuration.

1) Modify /etc/udev/rules.d/55-libsane.rules -- change group 'lp' to
group 'scanner'  (Don't know why, but ALL scanners listed here belong to
group 'lp' -- btw, this was in the file posted to this list under the
thread "Scanners on SuSE 11.0 -- do they work?".
2)
  a) Reboot the server
  b) have a user log in to the desktop (Otherwise, the scanner will not
be recognized as connected)
3) On the client machine(s), modify /etc/sane.d/dll.conf, uncommenting
'net' to allow usage of network scanners.  (Q: Why is this disabled by
default????)
4) On the client machine(s), add the machine with the scanner to
/etc/sane.d/net.conf,
ex. blue.j2eeguys.com
(Apparently, no such thing as an "autoscan of the network here)
5) On the client machine,
~>scanimage -L
device `net:blue.j2eeguys.com:genesys:libusb:002:003' is a Canon LiDE
35/40/50 flatbed scanner

WHOOHOO!  After this long song & dance, Client machine now sees scanner
on Server!

Attempts to acquire an image (using the "Acquire" module in Gimp, a
wrapper for scanimage) results in hangs on both client and server.
Total log:
Feb  9 10:20:11 blue xinetd[4445]: Started working: 1 available service
Feb  9 10:20:41 blue saned[4456]: saned (AF-indep+IPv6) from
sane-backends 1.0.19 ready
Feb  9 10:20:41 blue saned[4456]: check_host: access by remote host:
192.168.1.2
Feb  9 10:20:41 blue saned[4456]: init: access granted to
saned-user at 192.168.1.2

The only way to recover is to kill the saned process and restart xinitd.
Now what????  And that only allows for the scanner to be used on the
server -- NOT THE CLIENT.

So, now what needs to be done?  (Apparently, I missed at least one step
somewhere).

(On a different note, what does the '+' mean in the directory listing;
blue:~ # ls -l /dev/bus/usb/002/003
crw-rw-r--+ 1 root scanner 189, 130 Feb  9 10:38 /dev/bus/usb/002/003
)


Regards,
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFJkF0wSphIUSiVzgYRAhTcAJ4oy08bkAxvNNa05GERTXDYLSBH0QCguRVc
eRBntiSAxaivinkbv+/5Ahs=
=6VUV
-----END PGP SIGNATURE-----