Mailinglist Archive: opensuse-bugs (12871 mails)

< Previous Next >
[Bug 462639] access permissions for scsi scanners missing
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 20 Jan 2009 01:20:46 -0700 (MST)
  • Message-id: <20090120082046.AD3C0CC7CD@xxxxxxxxxxxxxxxxxxxxxx>

User jsmeix@xxxxxxxxxx added comment

Johannes Meixner <jsmeix@xxxxxxxxxx> changed:

What |Removed |Added
Info Provider| |dkukawka@xxxxxxxxxx

--- Comment #28 from Johannes Meixner <jsmeix@xxxxxxxxxx> 2009-01-20 01:20:44
MST ---
I.e. you mean that the new hal package provides now both
- a generic ACL rule for SCSI devices with SCSI type "scanner"
- tons of rules for all the USB scanners in 70-scanner.fdi

Regarding the latter (USB scanner entries):

As there is no generic USB device class for scanners,
there cannot be a generic rule for USB scanners
so that USB scanners must be listed one by one
an this list must be maintained all the time.

Such a list of USB scanners depends on the current versions
of the scanner driver packages (which models are currently
known and supported by a scanner driver package).
Currently our scanner driver packages are
sane-backends, hplip, iscan-free, and iscan.

The 70-scanner.fdi file which I provide in sane-backends
is made from driver description files of all our
scanner driver packages.
Therefore I have in the sane-backend sources the files
- models.dat (driver description for the hpaio driver in hplip)
- epkowa.desc (driver description for the epkowa driver in iscan*)

I assume you won't like to update your hal package for each
new version of a scanner driver package?

Furthermore really unsupported models which are also listed
in the driver description files must be specially excluded
from the list, see bug #439193.

Do you think that I should really remove 70-scanner.fdi completely
from the sane-backends package?
If yes, you alone (more precisely the hal package maintainer)
would become responsible when there is no scanner device access
for normal desktop users.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >