|
Bugzilla – Full Text Bug Listing |
| Summary: | Fingerprint Sensor not recognized | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Holger Sickenberg <holgi> |
| Component: | YaST2 | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | info, jsuchome |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | hwinfo.txt | ||
|
Description
Holger Sickenberg
2008-04-22 10:43:08 UTC
Created attachment 209530 [details]
hwinfo.txt
Ok, added some more sensors. What do we do with those, btw? Is there some tool using them and has it a list of supported devices? YaST Fingerprint Reader uses SCR::Read (.probe.fingerprint) call to check if the device is present. This call should be the YaST way to get the info equivalent to "hwinfo --fingerprint". The list of supported devices could provide Timo, I hope. The Authentec devices are not yet supported. Unfortunately this will not change until OS11 is gold. However, I'll start developing support sometime soon and will provide an OBS repo for that. Good morning, There is a driver for the reader aes2501: http://home.gna.org/aes2501/index_fr.html The equipment is recognized at home on the 10.3 but the application fprint (yast) tells me that there was no reader. I posted a bug on this topic: https://bugzilla.novell.com/show_bug.cgi?id=381633 It was marked as RESOLVED - INVALID ????? If it can help you? Hey Michel, We just don't have the integration ready for 11.0. Even if YaST recognizes the device as a fingerprint reader, we do not yet have the PAM stuff ready so that the device could be used for authentication. Please bear with us until I found time to implement it. It's likely that I will provide backported packages for OS11.0. It's not really a bug but a feature request. That's all -- and that's also what the bug states: RESOLVED - FEATURE. Ok Thank you |