Mailinglist Archive: opensuse-bugs (15878 mails)

< Previous Next >
[Bug 299809] New: Fingerprint Sensor (AuthenTec) get detect as Scanner ( create_hal_global_fdi_for_scanners parses unsupported.desc file)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 13 Aug 2007 08:43:41 -0600 (MDT)
  • Message-id: <bug-299809-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=299809

           Summary: Fingerprint Sensor (AuthenTec) get detect as Scanner
                    (create_hal_global_fdi_for_scanners  parses
                    unsupported.desc file)
           Product: openSUSE 10.3
           Version: Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: jsmeix@xxxxxxxxxx
        ReportedBy: dgollub@xxxxxxxxxx
         QAContact: qa@xxxxxxx
          Found By: ---


On initial login in KDE the suseplugger popup and detects the Fingerprint
Sensor as "Scanner" - and ask if the YaST scanner module should be started.

The root of this problem is in

/usr/share/sane/create_hal_global_fdi_for_scanners

which got executed on post install of the sane-backends package. 
( Output got piped into /etc/hal/fdi/policy/10osvendor/70-scanner.fdi )


DESCRIPTION_FILES="/usr/share/sane/descriptions/*.desc" contains also the file 
/usr/share/sane/descriptions/unsupported.desc

The AutehnTec Fingerprint sensor (:usbid "0x08ff" "0x2580") is listed in this
file as well. I guess this file should be excluded from the
create_hal_global_fdi_for_scanners script. Otherwise the capability property
"scanner" would get part of the 70-scanner.fdi file. And HAL would merge this
capability into this not as scanner intended device. And suseplugger wouldn't
get called...

(removing the unsupported.desc and executing the script again - definitely
solved the problem.)

( Isn't that an insane sane bug? )


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >