Bug 2011128

Summary:	pcscd spam syslog when the laptop is undocked and the reader is connected through the dock
Product:	[Fedora] Fedora	Reporter:	Santiago Gala <sgala>
Component:	pcsc-lite	Assignee:	Red Hat Crypto Team <crypto-team>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	34	CC:	crypto-team, jjelen, klember, rrelyea
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-07 20:34:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Santiago Gala 2021-10-06 04:42:31 UTC

Description of problem: pcscd spams journalctl logs if the cardreader is connected to the dock, every time the laptop is undocked. 

$ journalctl --boot -t pcscd | wc -l
304372
$ journalctl --boot -t pcscd | tail -6
oct 06 05:03:29 user pcscd[52231]: 00400073 ccid_usb.c:858:WriteUSB() write failed (3/4): -4 LIBUSB_ERROR_NO_DEVICE
oct 06 05:03:29 user pcscd[52231]: 00000010 ifdwrapper.c:364:IFDStatusICC() Card not transacted: 617
oct 06 05:03:30 user pcscd[52231]: 01000094 eventhandler.c:336:EHStatusHandlerThread() Error communicating to: Alcor Micro AU9540 00 00
oct 06 05:03:30 user pcscd[52231]: 00000056 ccid_usb.c:1343:InterruptRead() libusb_submit_transfer failed: LIBUSB_ERROR_NO_DEVICE
oct 06 05:03:31 user pcscd[52231]: 00400082 ccid_usb.c:858:WriteUSB() write failed (3/4): -4 LIBUSB_ERROR_NO_DEVICE
oct 06 05:03:31 user pcscd[52231]: 00000010 ifdwrapper.c:364:IFDStatusICC() Card not transacted: 617



Version-Release number of selected component (if applicable): 1.9.1-1.fc34


How reproducible:

Connect a card reader, and then disconnect it. It might be needed to connect/disconnect a couple of times

Actual results:

Every second 2 messages appear in logs, they keep appearing until the daemon is restarted

Expected results:

After a few errors the daemon should assume the reader is not there, or at least logs less noise.

Comment 1 Jakub Jelen 2021-10-06 15:47:04 UTC

Thank you for the report. I agree that this is a bit noisy. I will raise the issue upstream and we will see if there is something that can be done (except dropping verbosity of these logs).

Comment 2 Jakub Jelen 2021-10-11 13:03:55 UTC

Can you check if you can still reproduce the issue with the following builds from my copr? There are two packages pcsc-lite and pcsc-lite-ccid and change in the second one depends on the first one to work

https://copr.fedorainfracloud.org/coprs/jjelen/pcsc-lite-future/

If you will still see the issue, can you provide more verbose log (either here or in the upstream issue) when you receive this message every two seconds? You should be able to collect such logs by stopping pcscd.socket and pcscd.service and starting pcscd from commandline

   sudo LIBCCID_ifdLogLevel=0x000F pcscd --foreground --debug | tee log.txt

Comment 3 Jakub Jelen 2022-02-08 16:13:51 UTC

The upstream issue is closed and it looks like the problem is not related to the pcsc, but to the dock/firmware.

The Fedora 36 has already update pcsc-lite package. Did it somehow improve or is it still the issue?

I am not sure what would be the component to change this bug to, which is taking care of the dock connection? Should it be kernel or something else?

Comment 4 Ben Cotton 2022-05-12 15:03:12 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ben Cotton 2022-06-07 20:34:19 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.