[Lunar-bugs] [Lunar Linux 0000167]: udev/sane-backends: USB scanner support (libusb, /dev/sg0, cdrom group etc.)

[Lunar bug reports list]

The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.lunar-linux.org/view.php?id=167 
====================================================================== 
Reported By:                jannis
Assigned To:                
====================================================================== 
Project:                    Lunar Linux
Issue ID:                   167
Category:                   module
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Moonbase Version:           20060111.14 
Core Tools:                 Theedge 
Core Tools Version:         20061110 
====================================================================== 
Date Submitted:             01-28-2007 18:37 CET
Last Modified:              01-28-2007 18:37 CET
====================================================================== 
Summary:                    udev/sane-backends: USB scanner support (libusb,
/dev/sg0, cdrom group etc.)
Description: 
I've been trying to configure USB scanners (from Epson and Canon) on two
machines lately. On both I had the same problems:

  * sane-find-scanner detects them, but scanimage does not
  * No /dev/scanner* or /dev/usbscanner* device nodes exist, instead
    the scanners both seem to be using /dev/sg0
  * /var/lock/sane is missing

The last point is related to sane-backends and can be easily fixed in the
BUILD script. The others are more complicated.

First of all, the scanners are using /dev/sg0. There is only one udev rule
existing in 50-udev.rules (line 38), which assigns /dev/sg0 to the "cdrom"
group. /etc/security/console.perms states that /dev/sg0 may only be
accessed by root.cdrom.

We probably need to add a rule which creates /dev/scanner%e (or something
similar) for USB scanners and assigns them to the group "scanner" (or
whatever we might want to call it). 

Another problem I had was that, after these tweaks, scanimage still didn't
allow normal users (or users in group "cdrom"/"scanner") to access the
scanner. This was solved by applying chmod a+rw to /dev/bus/usb/001/006
(in this case). It's likely that something similar to this would have to
be added to the udev scanner rule as well, so that the scanner group has
full access to all scanner devices.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-28-07 18:37  jannis         New Issue                                    
01-28-07 18:37  jannis         Moonbase Version          => 20060111.14     
01-28-07 18:37  jannis         Core Tools                => Theedge         
01-28-07 18:37  jannis         Core Tools Version        => 20061110        
======================================================================