From godfreyhkchung at gmail.com  Sun Aug  6 23:56:16 2023
From: godfreyhkchung at gmail.com (Godfrey Chung)
Date: Mon, 7 Aug 2023 14:56:16 +0800
Subject: [Pcsclite-muscle] acsccid 1.1.10 Released
Message-ID: <CAF8Lfw+jmdwvAW1+hXQU8JJt_8MZyMhrR3x5aT65k355yZUOcw@mail.gmail.com>

Dear All

I would like to inform you that acsccid 1.1.10 had been released.

v1.1.10 (1/8/2023)
- Add the following readers support:
  ACR40U ICC Reader
  SCR FW_Upgrade
  ACR1552 1S CL Reader
  ACR1552 CL Reader
  ACR1552 USB FW_Upgrade
- Enable ACR1552U-M1 (composite device) as multi-slot reader.
- Enable the 2nd interface of ACR1552U-M1 as SAM slot.
- Fix missing initialization in get_end_points().
- Update _usbDevice.has_interrupt in get_end_points().
- Initialize multislot for interrupt endpoint only in OpenUSBByName().
- Detect a card on macOS for interrupt endpoint only in OpenUSBByName().
- Simplify the code for delaying the write operation.
- Allow ACR38 or the reader which needs write delay in WriteUSB().
- Check the packet size to avoid infinite loop in WriteUSB().
- Use #pragma pack(1) for all platforms in src/ifdhandler.c.

Please download it from http://acsccid.sourceforge.net/.

Regards

Godfrey


From johannes at sipsolutions.net  Wed Aug 16 00:09:50 2023
From: johannes at sipsolutions.net (Johannes Berg)
Date: Wed, 16 Aug 2023 09:09:50 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
Message-ID: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>

Hi,

I've been using a yubikey for years now with pcscd to use gpg/ssh, and
sadly this issue hasn't really been getting any better; if anything, it
has gotten worse throughout time. Could be something kernel related too,
I suppose.

Anyway, almost every time I boot my machine, I need to manually restart
pcscd before it will talk to my yubikey. Originally I thought maybe it's
related to whether I have it plugged in while booting or not, but really
it isn't, I normally don't have it plugged in, and yet it won't work
until I've restarted pcscd. Which is then fine until I reboot again. For
the record, this is with various recent versions of Fedora, and 

pcsc-lite version 1.9.9.
Copyright (C) 1999-2002 by David Corcoran <corcoran at musclecard.com>.
Copyright (C) 2001-2022 by Ludovic Rousseau <ludovic.rousseau at free.fr>.
Copyright (C) 2003-2004 by Damien Sauveron <sauveron at labri.fr>.
Report bugs to <pcsclite-muscle at lists.infradead.org>.
Enabled features: Linux x86_64-redhat-linux-gnu libsystemd serial usb
libudev usbdropdir=/usr/lib64/pcsc/drivers ipcdir=/run/pcscd filter
configdir=/etc/reader.conf.d
MAX_READERNAME: 128, PCSCLITE_MAX_READERS_CONTEXTS: 16


I'm not sure how I can generate the logs, certainly I couldn't run with
--foreground since the issue only ever happens with the pcscd instance
that starts during boot. Could also be something permissions related, I
suppose, but I honestly don't even know where to start looking.

Has anyone encountered such an issue before, or have any ideas where to
start looking?

Thanks,
johannes


From ludovic.rousseau at gmail.com  Wed Aug 16 02:00:57 2023
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Wed, 16 Aug 2023 11:00:57 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
Message-ID: <CAGstE8AorwxVTC1Na+vMz=NYCtJQjKTDV1hFR_ZiwmFsXn7iDQ@mail.gmail.com>

Le mer. 16 ao?t 2023 ? 09:11, Johannes Berg
<johannes at sipsolutions.net> a ?crit :
>
> Hi,

Hello,

> I've been using a yubikey for years now with pcscd to use gpg/ssh, and
> sadly this issue hasn't really been getting any better; if anything, it
> has gotten worse throughout time. Could be something kernel related too,
> I suppose.
>
> Anyway, almost every time I boot my machine, I need to manually restart
> pcscd before it will talk to my yubikey. Originally I thought maybe it's
> related to whether I have it plugged in while booting or not, but really
> it isn't, I normally don't have it plugged in, and yet it won't work
> until I've restarted pcscd. Which is then fine until I reboot again. For
> the record, this is with various recent versions of Fedora, and
>
> pcsc-lite version 1.9.9.
> Copyright (C) 1999-2002 by David Corcoran <corcoran at musclecard.com>.
> Copyright (C) 2001-2022 by Ludovic Rousseau <ludovic.rousseau at free.fr>.
> Copyright (C) 2003-2004 by Damien Sauveron <sauveron at labri.fr>.
> Report bugs to <pcsclite-muscle at lists.infradead.org>.
> Enabled features: Linux x86_64-redhat-linux-gnu libsystemd serial usb
> libudev usbdropdir=/usr/lib64/pcsc/drivers ipcdir=/run/pcscd filter
> configdir=/etc/reader.conf.d
> MAX_READERNAME: 128, PCSCLITE_MAX_READERS_CONTEXTS: 16
>
>
> I'm not sure how I can generate the logs, certainly I couldn't run with
> --foreground since the issue only ever happens with the pcscd instance
> that starts during boot. Could also be something permissions related, I
> suppose, but I honestly don't even know where to start looking.
>
> Has anyone encountered such an issue before, or have any ideas where to
> start looking?

Without logs it is hard to know what is happening.
Have a look into /var/log/syslog or other files in /var/log/

Also read "GnuPG and PC/SC conflicts"
https://blog.apdu.fr/posts/2019/06/gnupg-and-pcsc-conflicts/

Bye

-- 
 Dr. Ludovic Rousseau


From wolfgang at sweet-haven.com  Wed Aug 16 07:19:42 2023
From: wolfgang at sweet-haven.com (Lew Wolfgang)
Date: Wed, 16 Aug 2023 07:19:42 -0700
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
Message-ID: <9ccb8e20-1764-1100-d121-dacb81373281@sweet-haven.com>

On 8/16/23 00:09, Johannes Berg wrote:
> Hi,
>
> I've been using a yubikey for years now with pcscd to use gpg/ssh, and
> sadly this issue hasn't really been getting any better; if anything, it
> has gotten worse throughout time. Could be something kernel related too,
> I suppose.
>
> Anyway, almost every time I boot my machine, I need to manually restart
> pcscd before it will talk to my yubikey. Originally I thought maybe it's
> related to whether I have it plugged in while booting or not, but really
> it isn't, I normally don't have it plugged in, and yet it won't work
> until I've restarted pcscd. Which is then fine until I reboot again. For
> the record, this is with various recent versions of Fedora, and
>
> pcsc-lite version 1.9.9.
> Copyright (C) 1999-2002 by David Corcoran <corcoran at musclecard.com>.
> Copyright (C) 2001-2022 by Ludovic Rousseau <ludovic.rousseau at free.fr>.
> Copyright (C) 2003-2004 by Damien Sauveron <sauveron at labri.fr>.
> Report bugs to <pcsclite-muscle at lists.infradead.org>.
> Enabled features: Linux x86_64-redhat-linux-gnu libsystemd serial usb
> libudev usbdropdir=/usr/lib64/pcsc/drivers ipcdir=/run/pcscd filter
> configdir=/etc/reader.conf.d
> MAX_READERNAME: 128, PCSCLITE_MAX_READERS_CONTEXTS: 16
>
>
> I'm not sure how I can generate the logs, certainly I couldn't run with
> --foreground since the issue only ever happens with the pcscd instance
> that starts during boot. Could also be something permissions related, I
> suppose, but I honestly don't even know where to start looking.
>
> Has anyone encountered such an issue before, or have any ideas where to
> start looking?

This reminds me of a rinetd problem with systemd that I encountered on
openSUSE Leap.? One of our guys fixed the issue, rinetd was starting too
soon in the boot sequence.? But I'm not systemd fluent and don't remember
how it was fixed.? We haven't had any issues with pcscd and smartcards
on openSUSE.

Regards,
Lew



From johannes at sipsolutions.net  Wed Aug 16 07:43:57 2023
From: johannes at sipsolutions.net (Johannes Berg)
Date: Wed, 16 Aug 2023 16:43:57 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
Message-ID: <67fb4ecd5624997ceda7828532f8a7d846e55efe.camel@sipsolutions.net>

Hi,

Sorry, I messed up the list settings and didn't get your emails
directly, so am breaking the thread for the replies.

@Lew:
> This reminds me of a rinetd problem with systemd that I encountered on
> openSUSE Leap.  One of our guys fixed the issue, rinetd was starting too
> soon in the boot sequence.  But I'm not systemd fluent and don't remember
> how it was fixed.  We haven't had any issues with pcscd and smartcards
> on openSUSE.

I would've thought something similar, but it's not actually 100%? There
are some times where it actually works. Well, at least there used to be,
now it generally doesn't, I'd have to check. But yeah, it's possible,
but without even a USB device plugged in yet at boot, what could pcscd
depend on?


@Ludovic:
> Without logs it is hard to know what is happening.
> Have a look into /var/log/syslog or other files in /var/log/

Right, but there aren't really any logs.

# journalctl --system -b | grep pcscd
Aug 16 08:25:02 machine systemd[1]: Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket.
Aug 16 08:25:10 machine systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon.
Aug 16 08:25:10 machine audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 16 08:56:37 machine systemd[1]: Stopping pcscd.service - PC/SC Smart Card Daemon...
Aug 16 08:56:37 machine systemd[1]: pcscd.service: Deactivated successfully.
Aug 16 08:56:37 machine systemd[1]: Stopped pcscd.service - PC/SC Smart Card Daemon.
Aug 16 08:56:37 machine audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 16 08:56:37 machine systemd[1]: pcscd.service: Consumed 2.715s CPU time.
Aug 16 08:56:37 machine systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon.
Aug 16 08:56:37 machine audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 16 08:56:51 machine pcscd[6563]: 00000000 winscard.c:286:SCardConnect() Error Reader Exclusive
Aug 16 08:56:51 machine pcscd[6563]: 00015974 winscard.c:286:SCardConnect() Error Reader Exclusive
Aug 16 08:56:51 machine pcscd[6563]: 00017059 winscard.c:286:SCardConnect() Error Reader Exclusive

That last error message repeats, but it continues working anyway. No
messages between the start and stop.

Which is kind of why I was wondering about how to enable the logging if
I cannot run the --foreground listed on the website; maybe just add
similar command line options to the systemd unit so it starts like that
on boot?


> Also read "GnuPG and PC/SC conflicts"
> https://blog.apdu.fr/posts/2019/06/gnupg-and-pcsc-conflicts/

I'll try that too, thanks.

Thanks,
johannes


From ludovic.rousseau at gmail.com  Wed Aug 16 09:05:57 2023
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Wed, 16 Aug 2023 18:05:57 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <67fb4ecd5624997ceda7828532f8a7d846e55efe.camel@sipsolutions.net>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net> <67fb4ecd5624997ceda7828532f8a7d846e55efe.camel@sipsolutions.net>
Message-ID: <CAGstE8CF_MNzMWgEP1VqNs43s0qMTtQ92AGy2sHo+pisU6Myqw@mail.gmail.com>

Le mer. 16 ao?t 2023 ? 16:45, Johannes Berg
<johannes at sipsolutions.net> a ?crit :
> @Ludovic:
> > Without logs it is hard to know what is happening.
> > Have a look into /var/log/syslog or other files in /var/log/
>
> Right, but there aren't really any logs.
>
> # journalctl --system -b | grep pcscd
> Aug 16 08:25:02 machine systemd[1]: Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket.
> Aug 16 08:25:10 machine systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon.
> Aug 16 08:25:10 machine audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Aug 16 08:56:37 machine systemd[1]: Stopping pcscd.service - PC/SC Smart Card Daemon...
> Aug 16 08:56:37 machine systemd[1]: pcscd.service: Deactivated successfully.
> Aug 16 08:56:37 machine systemd[1]: Stopped pcscd.service - PC/SC Smart Card Daemon.
> Aug 16 08:56:37 machine audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Aug 16 08:56:37 machine systemd[1]: pcscd.service: Consumed 2.715s CPU time.
> Aug 16 08:56:37 machine systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon.
> Aug 16 08:56:37 machine audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Aug 16 08:56:51 machine pcscd[6563]: 00000000 winscard.c:286:SCardConnect() Error Reader Exclusive
> Aug 16 08:56:51 machine pcscd[6563]: 00015974 winscard.c:286:SCardConnect() Error Reader Exclusive
> Aug 16 08:56:51 machine pcscd[6563]: 00017059 winscard.c:286:SCardConnect() Error Reader Exclusive
>
> That last error message repeats, but it continues working anyway. No
> messages between the start and stop.

"SCardConnect() Error Reader Exclusive" indicates that a program asked
for a exclusive access to the reader.
And another program tried to also use the same reader.
The second program will receive an error and will not be able to use the reader.

I would suggest to increase the log level of gpg and your other
applications that use the smart card reader.
I guess one of the application will complain.

> Which is kind of why I was wondering about how to enable the logging if
> I cannot run the --foreground listed on the website; maybe just add
> similar command line options to the systemd unit so it starts like that
> on boot?

You can use the --debug argument.
See "pcscd arguments" in
https://blog.apdu.fr/posts/2021/08/pcsc-lite-configuration-using/

Bye

-- 
 Dr. Ludovic Rousseau


From johannes at sipsolutions.net  Thu Aug 17 00:32:39 2023
From: johannes at sipsolutions.net (Johannes Berg)
Date: Thu, 17 Aug 2023 09:32:39 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <CAGstE8CF_MNzMWgEP1VqNs43s0qMTtQ92AGy2sHo+pisU6Myqw@mail.gmail.com>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
	 <67fb4ecd5624997ceda7828532f8a7d846e55efe.camel@sipsolutions.net>
	 <CAGstE8CF_MNzMWgEP1VqNs43s0qMTtQ92AGy2sHo+pisU6Myqw@mail.gmail.com>
Message-ID: <5a132fe999303d1adf9c65337806f0b748176da2.camel@sipsolutions.net>

On Wed, 2023-08-16 at 18:05 +0200, Ludovic Rousseau wrote:
> 
> "SCardConnect() Error Reader Exclusive" indicates that a program asked
> for a exclusive access to the reader.
> And another program tried to also use the same reader.
> The second program will receive an error and will not be able to use the reader.

Right. I think I got rid of that with the previous link, but the whole
behaviour persists as is.

> I would suggest to increase the log level of gpg and your other
> applications that use the smart card reader.
> I guess one of the application will complain.

I'm not sure that's the case, I don't see anything like that. See below,
I believe pcscd is connecting to the reader in both good and bad cases,
at least I see "Using the reader polling thread" and "Card ATR" log
messages etc.

Hey, I might very well be doing something completely stupid, and
honestly I've long forgotten how I even set this up.

But if I just stop pcscd, it gets restarted automatically by socket
activation when I actually try to use the key for ssh, and then it
actually works, so it's not that I don't need it at all and it's just
fighting for a key when other apps want to use it directly. So maybe I
should just always set it to socket activation ;-)


> > Which is kind of why I was wondering about how to enable the logging if
> > I cannot run the --foreground listed on the website; maybe just add
> > similar command line options to the systemd unit so it starts like that
> > on boot?
> 
> You can use the --debug argument.

Right, thanks. I hope this log didn't end up containing my password or
something, but if it does I guess I can just change it :)


I booted

Aug 17 09:12:21 machine systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon.

logged in (I think this is something I have in my session connecting):

Aug 17 09:12:22 machine pcscd[2280]: 00605117 winscard_svc.c:340:ContextThread() Authorized PC/SC client

(here I also tried to use it for ssh a few times just to see what would
happen in the log)

and plugged in the yubikey

Aug 17 09:13:54 machine pcscd[2280]: 00292149 hotplug_libudev.c:647:HPEstablishUSBNotifications() USB Device add
...
Aug 17 09:13:54 machine pcscd[2280]: 00000005 ccid_usb.c:757:OpenUSBByName() bNumDataRatesSupported is 0
Aug 17 09:13:54 machine pcscd[2280]: 00017265 ifdhandler.c:389:IFDHGetCapabilities() tag: 0xFB3, usb:1050/0407:libudev:2:/dev/bus/usb/007/006 (lun: 0)
Aug 17 09:13:54 machine pcscd[2280]: 00000012 readerfactory.c:398:RFAddReader() Using the reader polling thread
Aug 17 09:13:54 machine pcscd[2280]: 00000256 ifdhandler.c:389:IFDHGetCapabilities() tag: 0xFAE, usb:1050/0407:libudev:2:/dev/bus/usb/007/006 (lun: 0)
Aug 17 09:13:54 machine pcscd[2280]: 00000007 ifdhandler.c:487:IFDHGetCapabilities() Reader supports 1 slot(s)
Aug 17 09:13:54 machine pcscd[2280]: 00000515 ifdhandler.c:1246:IFDHPowerICC() action: PowerUp, usb:1050/0407:libudev:2:/dev/bus/usb/007/006 (lun: 0)
Aug 17 09:13:54 machine pcscd[2280]: 00000269 eventhandler.c:289:EHStatusHandlerThread() powerState: POWER_STATE_POWERED
Aug 17 09:13:54 machine pcscd[2280]: 00000013 Card ATR: 3B F8 13 00 00 81 31 FE 15 59 75 62 69 6B 65 79 34 D4


but now it doesn't work, I tried a few times to use it for ssh login.

Then I restarted pcscd and basically the same things happen, except it
works?

Full log here:
https://p.sipsolutions.net/01897e99bf26357a.txt

Thanks,
johannes


From ludovic.rousseau at gmail.com  Thu Aug 17 01:51:31 2023
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Thu, 17 Aug 2023 10:51:31 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <5a132fe999303d1adf9c65337806f0b748176da2.camel@sipsolutions.net>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
 <67fb4ecd5624997ceda7828532f8a7d846e55efe.camel@sipsolutions.net>
 <CAGstE8CF_MNzMWgEP1VqNs43s0qMTtQ92AGy2sHo+pisU6Myqw@mail.gmail.com> <5a132fe999303d1adf9c65337806f0b748176da2.camel@sipsolutions.net>
Message-ID: <CAGstE8ATSuQyYf_e5GcDt8xnm5Ro3BzAMZJMfSEjCHHT4C8P8Q@mail.gmail.com>

Le jeu. 17 ao?t 2023 ? 09:34, Johannes Berg
<johannes at sipsolutions.net> a ?crit :
> but now it doesn't work, I tried a few times to use it for ssh login.

You need to find the application that is causing troubles.
I suggest to use list_pcsc_applications.sh from
https://github.com/LudovicRousseau/PCSC-contrib/blob/master/list_pcsc_applications.sh

> Then I restarted pcscd and basically the same things happen, except it
> works?

Yes, because the application that was blocking has "released" the reader.

> Full log here:
> https://p.sipsolutions.net/01897e99bf26357a.txt

Nothing interesting in the log.
The problem is on the applications side.

Bye

-- 
 Dr. Ludovic Rousseau


From johannes at sipsolutions.net  Thu Aug 17 23:59:44 2023
From: johannes at sipsolutions.net (Johannes Berg)
Date: Fri, 18 Aug 2023 08:59:44 +0200
Subject: [Pcsclite-muscle] need to restart pcscd for USB after boot
In-Reply-To: <CAGstE8ATSuQyYf_e5GcDt8xnm5Ro3BzAMZJMfSEjCHHT4C8P8Q@mail.gmail.com>
References: <14ff04f0b6449af51038c8eb3414e79d9fb9a1b7.camel@sipsolutions.net>
	 <67fb4ecd5624997ceda7828532f8a7d846e55efe.camel@sipsolutions.net>
	 <CAGstE8CF_MNzMWgEP1VqNs43s0qMTtQ92AGy2sHo+pisU6Myqw@mail.gmail.com>
	 <5a132fe999303d1adf9c65337806f0b748176da2.camel@sipsolutions.net>
	 <CAGstE8ATSuQyYf_e5GcDt8xnm5Ro3BzAMZJMfSEjCHHT4C8P8Q@mail.gmail.com>
Message-ID: <0a7afbd1c340c7501ff89e59a0877b683c3817f3.camel@sipsolutions.net>

On Thu, 2023-08-17 at 10:51 +0200, Ludovic Rousseau wrote:
> Le jeu. 17 ao?t 2023 ? 09:34, Johannes Berg
> <johannes at sipsolutions.net> a ?crit :
> > but now it doesn't work, I tried a few times to use it for ssh login.
> 
> You need to find the application that is causing troubles.
> I suggest to use list_pcsc_applications.sh from
> https://github.com/LudovicRousseau/PCSC-contrib/blob/master/list_pcsc_applications.sh
> 
> > Then I restarted pcscd and basically the same things happen, except it
> > works?
> 
> Yes, because the application that was blocking has "released" the reader.

> The problem is on the applications side.
> 

Right. That turned out to be gsd-smartcard, and armed with that
knowledge you can actually find others who have the same problem, e.g.
this old bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1893131

I'm guessing removing opensc will fix the issue for me too ...

Thanks!

johannes


