How to Install and Uninstall sane-backends-autoconfig Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "sane-backends-autoconfig" package

This guide let you learn how to install sane-backends-autoconfig on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                sane-backends-autoconfig
            
                    
    
    Copied

2. Uninstall "sane-backends-autoconfig" package

This guide let you learn how to uninstall sane-backends-autoconfig on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                sane-backends-autoconfig
            
                    
    
    Copied

3. Information about the sane-backends-autoconfig package on openSuSE Tumbleweed

Information for package sane-backends-autoconfig:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : sane-backends-autoconfig
Version : 1.2.1-2.1
Arch : noarch
Vendor : openSUSE
Installed Size : 72.3 KiB
Installed : No
Status : not installed
Source package : sane-backends-1.2.1-2.1.src
Upstream URL : http://www.sane-project.org/
Summary : USB Scanner Autoconfiguration
Description :
USB scanner autoconfiguration happens via udev.
The file /udev/rules.d/56-sane-backends-autoconfig.rules contains
entries for those USB scanners where the USB IDs are known, which are
supported by a free driver, where the support status is "complete" or
"good", and which do not require firmware upload.
When a USB scanner is connected and its USB IDs match to an entry in
the 56-sane-backends-autoconfig.rules file, the matching scanner driver
is activated (i.e. the driver line in /etc/sane.d/dll.conf is
activated).
It enables scanner drivers but never disables them. The reason is that
enabled drivers do not hurt so that an automated disable would make it
only overcomplicated because when more than one scanner uses the same
driver, a complicated check would be needed to avoid that the driver is
accidentally disabled when only one scanner was disconnected.
If you do not like automated driver activation, do not install this
package or remove it when it is already installed.