sane-snapscan(5)
π sane-snapscan π
okay so this is the manual page for sane-snapscan, bestie β it lives in section 5 of the SANE docs (Scanner Access Now Easy, iykyk) and it's literally all about getting your AGFA SnapScan flatbed talking to your computer. buckle up π
β¨ NAME β¨
sane-snapscan β the SANE backend for AGFA SnapScan flatbed scanners. that's the whole vibe. π¦
πΈ DESCRIPTION πΈ
the sane-snapscan library implements a SANE backend β and SANE stands for Scanner Access Now Easy, which, slay β that gives you access to AGFA SnapScan flatbed scanners. π
right now, the following scanners are supported from this backend: AGFA SnapScan 300, 310, 600, and 1236s, 1236u, 1212u, e20, e25, e40, e50, e60, Vuego 310s, Acer 300f, 310s, 610s, 610plus, Prisa 620s, Prisa 620u, Prisa 620ut, Prisa 640u, Prisa 640bu, Prisa 1240, Prisa 3300, Prisa 4300, Prisa 5300 and Guillemot Maxi Scan A4 Deluxe (SCSI) (with varying success).
not gonna lie, that last bit β "with varying success" β is doing a LOT of heavy lifting π consider that your vibe check before you plug anything in.
π DEVICE NAMES π
so this backend expects device names shaped like this:
special
where special is the path-name for the special device that corresponds to a SCSI scanner. for SCSI scanners, the special device name has to be a generic SCSI device, or a symlink pointing at one of those. under Linux, a device name like /dev/sga or /dev/sge would work, for example. see sane-scsi(5) for details. π«Ά
for USB scanners, the devicename must contain the keyword "usb" β like in /dev/usbscanner or /dev/usb/scanner0.
for scanners that need a firmware upload before scanning, add a line starting with "firmware" followed by the fully qualified path to your firmware file, like this:
firmware /usr/share/sane/snapscan/firmware.bin
for further details, go read http://snapscan.sourceforge.net π
β CONFIGURATION β
the contents of the snapscan.conf file is a list of device names that correspond to SnapScan scanners. empty lines and lines starting with a hash mark (#) are ignored. see sane-scsi(5) for details on what constitutes a valid device name. β¨
π FILES π
/etc/sane.d/snapscan.confβ the backend configuration file (see also the description ofSANE_CONFIG_DIRbelow)./usr/lib64/sane/libsane-snapscan.aβ the static library implementing this backend./usr/lib64/sane/libsane-snapscan.soβ the shared library implementing this backend (present on systems that support dynamic loading).
π ENVIRONMENT π
SANE_CONFIG_DIRβ this environment variable specifies the list of directories that may contain the configuration file. on NIX systems, the directories are separated by a colon (`:`); under OS/2, they're separated by a semi-colon (`;`). if this variable isn't set, the configuration file is searched in two default directories: first the current working directory ("."), and then/etc/sane.d. if the value of the environment variable ends with the directory separator character, then the default directories are searched *after the explicitly specified directories. for example, settingSANE_CONFIG_DIRto"/tmp/config:"would result in directoriestmp/config,., and/etc/sane.dbeing searched (in this order).SANE_DEBUG_SNAPSCANβ if the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. e.g., a value of255requests all debug output to be printed. smaller levels reduce verbosity. π₯
π BUGS π
the man page doesn't provide much information yet.
yes, that IS the bug. the docs are lowkey under construction π iconic behavior honestly.
π SEE ALSO π
sane(7), sane-scsi(5), http://sourceforge.net/projects/snapscan/ (new development website)
π AUTHOR π
Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot, Mikko Tyolajarvi, David Mosberger-Tang, Wolfgang Goeller, Petter Reinholdtsen, Gary Plewa, Sebastien Sable, Oliver Schwartz and Mikael Magnusson.
Man page by Henning Meier-Geinitz (mostly based on the web pages and source code). π«Ά
okay that's the whole thing, bestie β periodt. β¨ this page is from SANE Scanner Access Now Easy, dated 14 Jul 2008, and yeah it's literally titled sane-snapscan(5) β go scan something cute π
π
π¦ where this page comes from
- centos-stream 10: sane-backends 1.2.1-10.el10 Β· GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
- fedora 43: sane-backends 1.4.0-4.fc43 Β· GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
- fedora 44: sane-backends 1.4.0-6.fc44 Β· GPL-2.0-or-later WITH SANE-exception AND GPL-2.0-or-later AND GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LicenseRef-Fedora-Public-Domain AND IJG AND MIT
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- opensuse-leap 16.0: sane-backends 1.3.0-bp160.1.14 Β· GPL-2.0-or-later AND SUSE-GPL-2.0+-with-sane-exception AND SUSE-Public-Domain
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms