Bug 465221

Summary:	cyberjack usb device node wrong permissions
Product:	[openSUSE] openSUSE 11.1	Reporter:	Wolfgang Rosenauer <wolfgang>
Component:	Other	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	lnussel
Version:	RC 1
Target Milestone:	---
Hardware:	All
OS:	openSUSE 11.1
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	fdi

Description Wolfgang Rosenauer 2009-01-11 20:29:53 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5
Build Identifier: 

In the past the cyberjack cardreader was accessible from people using the desktop by defining a hal policy.
(see package ctapi-cyberjack file /etc/hal/fdi/policy/10osvendor/80-cyberjack.fdi)

This doesn't seem to work on 11.1 anymore.

Reproducible: Always

Comment 1 Wolfgang Rosenauer 2009-01-11 22:58:44 UTC

Ok, I've found bug 438867 which seems to be basically the same issue.
But I'm not completely sure what needs to be done for the cyberjack reader.

20-acl-management.fdi contains no sections for cardreaders but actually they are similar to fingerprint-readers.

Comment 2 Wolfgang Rosenauer 2009-01-12 08:35:37 UTC

Created attachment 264408 [details]
fdi

With the information in the other bug I created this fdi file and copied it to /usr/share/hal/fdi/policy/20thirdparty. But either the location or the content is bad since it doesn't help anything.
Interestingly lshal still shows the resmgr.class for the device even when I've deleted the /etc/hal/fdi file where it was defined. I couldn't find out where this information is still cached or similar.

Comment 3 Wolfgang Rosenauer 2009-01-12 08:37:42 UTC

Assigning to Stanislav as maintainer.
Ludwig, could you please give a hint what's wrong and what's the right way to do that?

Comment 4 Ludwig Nussel 2009-01-12 10:09:46 UTC

dup of 438131

*** This bug has been marked as a duplicate of bug 438131 ***