Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"error libnfc.driver.acr122_usb Invalid RDR_to_PC_DataBlock frame" spam #4

Open
Enverex opened this issue Aug 30, 2017 · 2 comments
Open

Comments

@Enverex
Copy link

Enverex commented Aug 30, 2017

The program itself seems to work fine, but it's constantly outputting the following text making logging useless. It seems to happen every 5 seconds if a NFC tag isn't present on the reader:

Aug 30 10:47:38 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:47:43 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:47:48 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:47:53 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:47:58 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:48:03 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:48:09 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:48:14 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame
Aug 30 10:48:19 arcade nfc-eventd[4160]: error        libnfc.driver.acr122_usb        Invalid RDR_to_PC_DataBlock frame

If it's not possible to fix this, is it at least possible to have nfc-eventd ignore the message from libnfc so that it doesn't fill the log?

@Enverex
Copy link
Author

Enverex commented Aug 30, 2017

It looks like disabling all errors in libnfc itself mutes this, but would it be possible to have nfc-eventd catch these into it's own debug logging rather than having to disable it in libnfc globally on the system?

@work40
Copy link

work40 commented Jan 29, 2018

Use patch for libnfc from here https://gist.github.com/danieloneill/3be43d5374c80d89ea73 to solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants