File	Date	Author	Commit
descriptions	2015-10-07	Paul Newall	[f40d24] updated to suit sane 1.0.25 release
COPYING	2013-05-06	Paul Newall	[50636b] Initial commit Hennings version 08-09-2005
Makefile	2014-12-19	Paul Newall	[3ed460] changed to use gtk3 and updated
README	2014-12-19	Paul Newall	[3ed460] changed to use gtk3 and updated
descriptions.c	2013-05-24	Paul Newall	[cecacb] Added test of udev rules files
descriptions.h	2014-12-19	Paul Newall	[3ed460] changed to use gtk3 and updated
descriptions.o	2015-10-07	Paul Newall	[e35ff8] forgot to recompile
sane-troubleshoot	2015-10-07	Paul Newall	[e35ff8] forgot to recompile
sane-troubleshoot.c	2015-10-07	Paul Newall	[f40d24] updated to suit sane 1.0.25 release
sane-troubleshoot.o	2015-10-07	Paul Newall	[e35ff8] forgot to recompile
sane.h	2013-05-06	Paul Newall	[50636b] Initial commit Hennings version 08-09-2005

Read Me

This is the README of sane-troubleshoot.

* What's the purpose of this program?

It tries to find out what's wrong with your installation of SANE. It checks
for some common mistakes and explains what to do to fix them and where to find
documentation and help. It writes everything it finds out to a logfile.  It's
NOT an installation wizard as it doesn't change any files.

It's intended to be used for scanners, but may also work with other devices
supported by SANE.

Currently it's in alpha stage and has not been widely tested.

* How is it used?

Just run ./sane-troubleshoot. You'll need gtk3 (http://www.gtk.org). If you
get an error about missing libraries you may need to build from source (see
below).

* How to build

You need gtk3 including the development headers. Just enter "make". There
is no installation target yet.

* What kind of tests does it do?

(+ means: works, - means: planned)

+ Checks if SANE libraries, headers and config files are installed
+ Checks for multiple installations
+ Check, if libsane can be loaded
+ Check for the version of sane-backends
+ Try to open the test backend
+ List all scanners that are found by SANE, if the scanner is found:
  + find out the backend
  + enable debugging
  + try to scan a small image, list all errors
+ If the scanner isn't found
  + list known manufacturers + models, select one
  + list known models, select one
  + If the scanner is known:
    + find out the backend that's used
    + check if it's in dll.conf
    + enable debugging and load the backend + get_devices
    + find out the type of scanner
    + check permissions (udev in work)
  + If the scanner isn't known, warn about not supported
    - try to get SCSI/USB sane-find-scanner-like output
    - check libusb, /proc/bus/usb, /proc/scsi/scsi
    - check permissions