Bug 1057285 - udev rules not working.
Summary: udev rules not working.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libnfc
Version: 19
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-23 18:40 UTC by Frank Büttner
Modified: 2014-09-23 04:32 UTC (History)
2 users (show)

Fixed In Version: libnfc-1.7.1-4.fc21
Clone Of:
Environment:
Last Closed: 2014-09-19 10:05:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Büttner 2014-01-23 18:40:55 UTC
Description of problem:
The udev rules will not work because of 2 errors:
first the group plugdev is missing.
And second the correct line for example will be:
ATTRS{idVendor}=="04cc", ATTRS{idProduct}=="2533", MODE="0664", GROUP="plugdev",SYMLINK+="nfcreader"

The last part is missing, so that non root users can use the NFC reader.

Version-Release number of selected component (if applicable):
libnfc-1.7.0-1.fc19.x86_64

How reproducible:
Try to use the reader as non root user.

Steps to Reproduce:
call nfc-list -v

Actual results:
An error that no readers are found.

Expected results:
list of readers and tag when present.

Additional info:
the is also an kernel module blacklist file needed:
Content:
/etc/modprobe.d/blacklist-libnfc.conf:
blacklist nfc
blacklist pn533

Comment 1 Jaroslav Škarvada 2014-08-28 10:51:48 UTC
Thanks for spotting this, we need to migrate the rules to uaccess.

Regarding modules blacklist, I will provide example black list file, but I will not install it by default.

Comment 2 Fedora Update System 2014-08-28 16:23:38 UTC
libnfc-1.7.1-4.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/libnfc-1.7.1-4.fc21

Comment 3 Fedora Update System 2014-08-28 16:27:56 UTC
libnfc-1.7.1-4.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libnfc-1.7.1-4.fc19

Comment 4 Fedora Update System 2014-08-28 16:29:57 UTC
libnfc-1.7.1-4.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/libnfc-1.7.1-4.fc20

Comment 5 Fedora Update System 2014-08-29 14:43:13 UTC
Package libnfc-1.7.1-4.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libnfc-1.7.1-4.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-9911/libnfc-1.7.1-4.fc21
then log in and leave karma (feedback).

Comment 6 Frank Büttner 2014-08-29 15:53:35 UTC
Hello I have test the packages for F20.
It will work now.
I only find a little problem with the package documentation about the kernel blacklist file.
This part is documented twice.
On at /usr/share/doc/libnfc/README.fedora and in /usr/share/doc/libnfc/README
But at /usr/share/doc/libnfc/README the path is wrong.
It is written as "sudo cp contrib/linux/blacklist-libnfc.conf /etc/modprobe.d/blacklist-libnfc.conf" But the file live at /usr/share/libnfc/blacklist-libnfc.conf

I mean not very dramatic, but for the next package rebuild it can be fixed.

Comment 7 Jaroslav Škarvada 2014-09-01 08:01:53 UTC
(In reply to Frank Büttner from comment #6)
OK, thanks, I will fix it in rawhide / f21. README is upstream file, I will probably edit the path in it.

Comment 8 Fedora Update System 2014-09-19 10:05:11 UTC
libnfc-1.7.1-4.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-09-19 10:15:36 UTC
libnfc-1.7.1-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2014-09-23 04:32:44 UTC
libnfc-1.7.1-4.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.