The SANE bug tracker can be used to report bugs or missing
features in sane-backends, sane-frontends or the web pages. Please be as
specific as possible and use an appropriate category. Add as much
information as possible to the report. Have a look at the list of
categories and groups to decide which one to use:
None: If you don't know which category to chose, use
None. One of the SANE developers will select the right
backends (drivers): All bugs concerning the
backends. E.g. if your scans have wrong colors. Please mention the
name of the backend and the manufacturer and name of the
scanner. Example: gt68xx: Artec Ultima 2000 scans are completely
scanimage, xscanimage, and
xcam: For bugs concerning one of these frontends. To
make sure if it's really a frontend problem, check if the bug happens
only with that frontend.
saned: Bugs concerning the SANE network scanning daemon
documentation: Bugs, missing information, spelling
mistakes in the manual pages, READMEs or other documentation coming
website: Wrong or missing information, spelling
mistakes, and dead links on the SANE website.
sanei, porting, and sane
standard are (almost) only relevant for
developers. sanei is used for bugs in the SANE internal
functions. porting is for bugs concerning compilation and
installation of SANE on various platforms. If something should be
changed in our API, sane standard should be used as category.
general: This category should be used for
bugs/feature requests concerning SANE as a whole.
None: Used for most bugs.
wishlist: If you submit a feature request and not a
bug, use this group.
security: Bugs that can affect the security of the
system. E.g. buffer overflows in saned or temporary file issues.
standard-compliance: If a backend or frontend fails
to comply with the SANE standard.