Skip to content

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

Open
@Enverex

Description

@Enverex

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions