pcscd.socket is disabled after installation

[Ubucolors]

[ Impact ]

The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers.

This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots).

This is especially painful for users that require Smart Authentication for login.

[ Test Plan ]

Steps to reproduce:

1. If installed, remove and do a fresh install of the package pcscd
(the sole version released for jammy is 1.9.5-3).

2. Verify that the pcscd.socket is disabled:

$ systemctl status pcscd.socket
○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket
     Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled)
     Active: inactive (dead)
   Triggers: ● pcscd.service
     Listen: /run/pcscd/pcscd.comm (Stream)

3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work.

Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention.

[ Where problems could occur ]

This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal.

The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket.

[ Other Info ]

This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS.

Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this.

As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug:
 - jammy
 - kinetic
 - lunar

[Ludovic Rousseau (ludovic-rousseau-gmail)]

I just made a fresh install of Ubuntu 22.04.
For an unknown reason pcscd.socket is DISABLED.
$ systemctl status pcscd.socket
○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket
     Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled)
     Active: inactive (dead)
   Triggers: ● pcscd.service
     Listen: /run/pcscd/pcscd.comm (Stream)

To solve the problem you can do:
sudo systemctl enable pcscd.socket

Then reboot, or run "sudo systemctl start pcscd.socket".

[Ubucolors (ubucolors)]

Hi, thanks. I shall try this.
This enabling of the pcscd.socket stays persistent trough restarts i may hope ?
Is this a bug in pcscd-lite or elsewhere ?

[Ubucolors (ubucolors)]

I will post the contents of the 2 systemd configuration files: "pcscd.service" and "pcscd.socket" later.
I saw that they where not totally the same like in your blog.
But now i'am on Ubuntu 18.04 and I saw that they where the same.

[Ubucolors (ubucolors)]

both files from /lib/systemd/system/> <
>pcscd.service<
[Unit]
Description=PC/SC Smart Card Daemon
Requires=pcscd.socket
Documentation=man:pcscd(8)

[Service]
ExecStart=/usr/sbin/pcscd --foreground --auto-exit $PCSCD_ARGS
ExecReload=/usr/sbin/pcscd --hotplug
EnvironmentFile=-/etc/default/pcscd

[Install]
Also=pcscd.socket

>pcscd.socket<
[Unit]
Description=PC/SC Smart Card Daemon Activation Socket

[Socket]
ListenStream=/run/pcscd/pcscd.comm
SocketMode=0666

[Install]
WantedBy=sockets.target

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Schmitt (unixtippse)]

We're seeing this same issue. The postinst script in the 22.04 package seems to be missing a few lines that were still there in 21.10, one of which would be the one that executes systemctl enable pcscd.socket.

[Ubucolors (ubucolors)]

Good news for Belgians who connect to the government site with there id card.

[Ludovic Rousseau (ludovic-rousseau-gmail)]

On a different Ubuntu 22.04 system I DO NOT reproduce the problem.
pcscd was working fine with no extra manual operation.

This time I used a real laptop and not a virtual machine. But that should not have an effect.
The problem may not be easy to understand.

[Ubucolors (ubucolors)]

Perhaps due to different type of hardware ?
Here i used a Dell E5550.

[Ludovic Rousseau (ludovic-rousseau-gmail)]

I reinstalled Ubuntu 22.04 in another VM (still using VirtualBox) and I do NOT get the problem.
So it is not related to the hardware (I was expecting this result).

Strange.

[S. Jansen (tineidae)]

I had this issue but it was a different reason, if you use the yubioath-desktop snap, all certificate readers are grabbed by that snap and pcscd cant see any devices. It doesnt matter if its just an YubiKey or a different device like a NitroKey.

After killing yubioath-desktop and reinsert the smartcard, pcscd is able to claim the device.

[apinunt (apinunt)]

We've been having to run "service pcscd start" manually to use the ACS ACR39U card reader each time.
Man pcscd seems to say the service is started at boot, which it is not, though ideally we would like it to start when the reader is plugged into the computer and stop when it is unplugged.

[apinunt (apinunt)]

Forgot to say, but the same problem exists on both a Dell G5, running Ubuntu Mate 21.10 and a Dell Latitude 3190 running Ubuntu Mate 22.04.

[Ludovic Rousseau (ludovic-rousseau-gmail)]

@apinunt, pcscd is not started at boot but when an application is calling the WinSCard API.
See https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

Where do you find that pcscd manpage indicates it is started at boot?

Interesting to know that this bug was already present in Ubuntu 21.10.

[Seth Tanner (sjtanner)]

We're seeing the same behavior with Dell Precision 3600 series desktops and HID Global OMNIKEY 3x21 Smart Card Readers
We did not encounter the issue with 18.04 or 20.04, only in 22.04.
sudo systemctl enable pcscd.socket
does not seem to resolve the issue for us
sudo systemctl start pcscd.service
must be run after every reboot, we haven't seen any solution that persists a reboot.

[Ludovic Rousseau (ludovic-rousseau-gmail)]

Seth, what is the output of the command: systemctl status pcscd.socket

[Seth Tanner (sjtanner)]

Ludovic,
Please find the output you requested below.

systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
     Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-09-15 10:58:12 PDT; 1min 26s ago
   Triggers: ● pcscd.service
     Listen: /run/pcscd/pcscd.comm (Stream)
     CGroup: /system.slice/pcscd.socket

systemctl status pcscd.service
● pcscd.service - PC/SC Smart Card Daemon
     Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled)
     Active: active (running) since Thu 2022-09-15 10:58:16 PDT; 1min 31s ago
TriggeredBy: ● pcscd.socket
       Docs: man:pcscd(8)
   Main PID: 2544 (pcscd)
      Tasks: 7 (limit: 38174)
     Memory: 1.5M
        CPU: 73ms
     CGroup: /system.slice/pcscd.service
             └─2544 /usr/sbin/pcscd --foreground --auto-exit

Let me provide additional information on the behavior that we are seeing
If we use
sudo systemctl enable pcscd.socket

then we must issue either
sudo systemctl restart pcscd.socket
sudo systemctl stop pcscd.socket; sudo systemctl start pcscd.socket

almost every time we want to use smartcard authentication at gnome login screen

We have observed this behavior after the following events:
reboot
lock screen (seems to respond better to a stop and start of the socket rather than a restart, e.g. we can get multiple locks where we are able to log back in, if we stop and start the socket, whereas a restart just lets us get logged back in once)
log out

output from /var/log/auth.log
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received for user test.user: 7 (Authentication failure)
Sep 15 11:29:10 test-jammy gdm-password]: pam_pkcs11(gdm-password:auth): no suitable token available
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=test.user
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received for user test.user: 7 (Authentication failure)
Sep 15 11:29:19 test-jammy gdm-smartcard]: pam_sss(gdm-smartcard:auth): User info message: Please insert smart card

Commandline tools on the other hand seem to work as expected once the socket has been enabled, no additional socket restarts are needed
opensc-tool --list-readers
pkcs11-tool --list-token-slots
pkcs11_listcerts debug

[Ludovic Rousseau (ludovic-rousseau+ubuntu-one)]

Seth, pcscd.socket is already enabled. You should not have to run "sudo systemctl enable pcscd.socket" again.

In your output I see that pcscd is already running.
I would like to get the results of the following commands when you *have* the problem and before you try to fix it.

systemctl status pcscd.socket
systemctl status pcscd.service
ls -l /run/pcscd/
journalctl --no-pager --unit=pcscd.socket
journalctl --no-pager --unit=pcscd.service

[Seth Tanner (sjtanner)]

Ludovic,
We'll get a fresh install up and running and provide the output you have requested.

[Ondrej Vachálek (vacho81)]

Hello, a simple code helped me. From now on, pcscd.socket always starts for me

$sudo -i
#systemctl enable pcscd.socket
#sudo systemctl start pcscd.socket

Repeat exactly, the second sudo must also be.

[Peter Surda (surda)]

The bug described here looks like the one I'm experiencing. I have multiple yubikeys which I use for SSH and GPG (occasionally U2F but that doesn't appear to be affected by this). If I just enable the pcscd service, the daemon doesn't auto-start after a reboot. Running ssh or gpg commands fails to access the key. I also need to enable the socket. Then the daemon auto-starts and I can use ssh/gpg:

$ systemctl enable pcscd
# after a reboot, pcscd is stopped, ssh/gpg unable to access the key. Need to start pcscd manually.

$ systemctl enable pcscd.socket
# now after reboot both the socket and the service are running and ssh/gpg works

It wasn't like this with 20.04, there enabling pcscd.service was enough.

Hope this helps others with the issue, and/or the maintainers to address it.

[Andris Berzins (pkix)]

The same issue on two freshly installed Ubuntu 22.04 machines (whether the reader is connected to a machine is not relevant here).

These two commands fixed the problem (pcscd automatically starts now):
$ sudo systemctl enable pcscd
$ sudo systemctl enable pcscd.socket

[Christophe Bourez (ropieur)]

Hello,

I am facing a very similar issue
I managed to make it work on fresh install but it stopped working after a reboot
The two commands above do not resolve on my laptop

========================================================
$ sudo service pcscd status
○ pcscd.service - PC/SC Smart Card Daemon
     Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled)
     Active: inactive (dead) since Wed 2022-10-26 13:52:17 CEST; 6min ago
TriggeredBy: ● pcscd.socket
       Docs: man:pcscd(8)
   Main PID: 88997 (code=exited, status=0/SUCCESS)
        CPU: 13ms

oct 26 13:50:59 dadbert systemd[1]: Started PC/SC Smart Card Daemon.
oct 26 13:51:06 dadbert pcscd[88997]: 00000000 ccid_usb.c:886:WriteUSB() write failed (3/3): LIBUSB_ERROR_TIMEOUT
oct 26 13:51:11 dadbert pcscd[88997]: 05000646 ccid_usb.c:886:WriteUSB() write failed (3/3): LIBUSB_ERROR_TIMEOUT
oct 26 13:51:16 dadbert pcscd[88997]: 05000454 ccid_usb.c:886:WriteUSB() write failed (3/3): LIBUSB_ERROR_TIMEOUT
oct 26 13:51:16 dadbert pcscd[88997]: 00000036 ifdhandler.c:202:CreateChannelByNameOrChannel() failed
oct 26 13:51:16 dadbert pcscd[88997]: 00000277 readerfactory.c:1138:RFInitializeReader() Open Port 0x200000 Failed (usb:0a5c/5842:libudev:1:/dev/bus/usb/003/003)
oct 26 13:51:16 dadbert pcscd[88997]: 00000017 readerfactory.c:380:RFAddReader() Broadcom Corp 58200 [Contacted SmartCard] (0123456789ABCD) init failed.
oct 26 13:51:16 dadbert pcscd[88997]: 00000112 hotplug_libudev.c:538:HPAddDevice() Failed adding USB device: Broadcom Corp 58200
oct 26 13:52:17 dadbert systemd[1]: pcscd.service: Deactivated successfully.

========================================================
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0a5c:5842 Broadcom Corp. 58200
...
========================================================
$ pcscd --version
pcsc-lite version 1.9.5.
Copyright (C) 1999-2002 by David Corcoran <email address hidden>.
Copyright (C) 2001-2018 by Ludovic Rousseau <email address hidden>.
Copyright (C) 2003-2004 by Damien Sauveron <email address hidden>.
...
========================================================

OS: Ubuntu 22.04
Dell Precision 7670

[Christophe Bourez (ropieur)]

Incomprehensible, a new reboot solved my issue

[Ludovic Rousseau (ludovic-rousseau+ubuntu-one)]

I wrote a blog article about this issue
https://ludovicrousseau.blogspot.com/2022/10/ubuntu-2204-and-pcscd-auto-start-failure.html

[Ludovic Rousseau (ludovic-rousseau-gmail)]

The problem MAY be related to Debian issue #1034209 "pcscd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034209

[Tony Espy (awe)]

I ran into this bug earlier this week while trying to setup my new Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad running 22.04 LTS.

I've confirmed that the upstream commit from 1.9.9-2 fixes the problem, and am uploading this as a patch.

[Ubucolors (ubucolors)]

Good news Tony, almost 1 year after the release of Ubuntu 22.04 finally a
solution that works.

Op vr 12 mei 2023 om 17:31 schreef Tony Espy <email address hidden>:

> I ran into this bug earlier this week while trying to setup my new
> Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad
> running 22.04 LTS.
>
> I've confirmed that the upstream commit from 1.9.9-2 fixes the problem,
> and am uploading this as a patch.
>
> ** Patch added: "Backported packaging fix from upstream 1.9.9-2"
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+attachment/5672739/+files/0001-Fix-dh_installsystemd-doesn-t-handle-files-in-usr-li.patch
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971984
>
> Title:
> pcscd 1.9.5-3 do not start automatically, only manual
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
>
>

[Sebastien Bacher (seb128)]

The issue is fixed in mantic by https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/1.9.9-2

ubuntu-sponsors is subscribed but the change is a patch without the packaging integration or the changelog entry, could you perhaps add a debdiff for each serie instead?

[Ubucolors (ubucolors)]

Good news !
But i stay on Ubuntu Jammy and shall use the work around i did. See first post of me.

[Lucas Kanashiro (lucaskanashiro)]

Anyone willing to provide a debdiff (changes + changelog) to fix this issue in Jammy, Kinetic and Lunar? As Sebastien mentioned in comment #29, this bug has ~ubuntu-sponsors subscribed but there is no "ready-to-upload" debdiff attached.

[Steve Langasek (vorlon)]

Currently nothing to be sponsored, so unsubscribing the team. Tony, if you want to provide a matching patch for SRU to the stable series, please feel free to resubscribe ubuntu-sponsors once it's available.

[Brian Murray (brian-murray)]

I uploaded this the other day and its now waiting review from an SRU team member.

[Łukasz Zemczak (sil2100)]

Hello Ubucolors, or anyone else affected,

Accepted pcsc-lite into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pcsc-lite/1.9.9-1ubuntu0.23.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Ubucolors, or anyone else affected,

Accepted pcsc-lite into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pcsc-lite/1.9.9-1ubuntu0.22.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Ubucolors, or anyone else affected,

Accepted pcsc-lite into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pcsc-lite/1.9.5-3ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubucolors (ubucolors)]

Thank you Lukasz !

Op do 29 jun 2023 om 10:03 schreef Łukasz Zemczak <
<email address hidden>>:

> Hello Ubucolors, or anyone else affected,
>
> Accepted pcsc-lite into jammy-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/pcsc-
> lite/1.9.5-3ubuntu1 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed. Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> jammy to verification-done-jammy. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-jammy. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971984
>
> Title:
> pcscd.socket is disabled after installation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
>
>

[Tony Espy (awe)]

I enabled -proposed on jammy, and updated pcscd to 1.9.5-3ubuntu1. I verified that the socket is now enabled:

$ systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
     Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset: enabled)
     Active: active (listening) since Fri 2023-07-21 12:57:49 EDT; 6s ago
   Triggers: ● pcscd.service
     Listen: /run/pcscd/pcscd.comm (Stream)
     CGroup: /system.slice/pcscd.socket
Jul 21 12:57:49 brain systemd[1]: Listening on PC/SC Smart Card Activation Socket.

I also verified that when I plug in my Nitrokey HSM2, that it's now recognized by the system:

$ sc-hsm-tool
Using reader with a card: Nitrokey Nitrokey HSM (...)

[Ubucolors (ubucolors)]

Thank you Tony

Op vr 21 jul 2023 om 19:16 schreef Tony Espy <email address hidden>:

> I enabled -proposed on jammy, and updated pcscd to 1.9.5-3ubuntu1. I
> verified that the socket is now enabled:
>
> $ systemctl status pcscd.socket
> ● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
> Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor
> preset: enabled)
> Active: active (listening) since Fri 2023-07-21 12:57:49 EDT; 6s ago
> Triggers: ● pcscd.service
> Listen: /run/pcscd/pcscd.comm (Stream)
> CGroup: /system.slice/pcscd.socket
> Jul 21 12:57:49 brain systemd[1]: Listening on PC/SC Smart Card Activation
> Socket.
>
> I also verified that when I plug in my Nitrokey HSM2, that it's now
> recognized by the system:
>
> $ sc-hsm-tool
> Using reader with a card: Nitrokey Nitrokey HSM (...)
>
>
>
> ** Tags removed: verification-needed-jammy
> ** Tags added: verification-done-jammy
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971984
>
> Title:
> pcscd.socket is disabled after installation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
>
>

[Andreas Hasenack (ahasenack)]

Kinetic is EOL.

[Andreas Hasenack (ahasenack)]

This is missing a lunar verification before jammy (already verified) can be released.

[Brian Murray (brian-murray)]

I tested this update in Lunar (both a fresh install from -proposed and an upgrade to -proposed) and confirm that the socket is enabled:

Do you want to continue? [Y/n] Y
Get:1 http://192.168.10.7/ubuntu lunar-proposed/universe amd64 pcscd amd64 1.9.9-1ubuntu0.23.04.1 [58.6 kB]
Get:2 http://192.168.10.7/ubuntu lunar-proposed/main amd64 libpcsclite1 amd64 1.9.9-1ubuntu0.23.04.1 [20.5 kB]
Fetched 79.1 kB in 0s (679 kB/s)
(Reading database ... 241412 files and directories currently installed.)
Preparing to unpack .../pcscd_1.9.9-1ubuntu0.23.04.1_amd64.deb ...
Unpacking pcscd (1.9.9-1ubuntu0.23.04.1) over (1.9.9-1) ...
Preparing to unpack .../libpcsclite1_1.9.9-1ubuntu0.23.04.1_amd64.deb ...
Unpacking libpcsclite1:amd64 (1.9.9-1ubuntu0.23.04.1) over (1.9.9-1) ...
Setting up libpcsclite1:amd64 (1.9.9-1ubuntu0.23.04.1) ...
Setting up pcscd (1.9.9-1ubuntu0.23.04.1) ...
Created symlink /etc/systemd/system/sockets.target.wants/pcscd.socket \u2192 /lib/systemd/system/pcscd.socket.
pcscd.service is a disabled or a static unit not running, not starting it.
Processing triggers for libc-bin (2.37-0ubuntu2) ...
Processing triggers for man-db (2.11.2-1) ...
bdmurray@clean-lunar-amd64:~$ systemctl status pcscd.socket
\u25cf pcscd.socket - PC/SC Smart Card Daemon Activation Socket
     Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; preset: enabled)
     Active: active (listening) since Thu 2023-07-27 12:31:53 PDT; 20s ago
      Until: Thu 2023-07-27 12:31:53 PDT; 20s ago
   Triggers: \u25cf pcscd.service
     Listen: /run/pcscd/pcscd.comm (Stream)
     CGroup: /system.slice/pcscd.socket

Jul 27 12:31:53 clean-lunar-amd64 systemd[1]: Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pcsc-lite - 1.9.9-1ubuntu0.23.04.1

---------------
pcsc-lite (1.9.9-1ubuntu0.23.04.1) lunar; urgency=medium

  * Fix dh_installsystemd doesn't handle files in /usr/lib/systemd/system.
    Closes: #103429 and LP: #1971984

 -- Brian Murray <email address hidden> Tue, 27 Jun 2023 16:29:54 -0700

[Andreas Hasenack (ahasenack)]

The verification of the Stable Release Update for pcsc-lite has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pcsc-lite - 1.9.5-3ubuntu1

---------------
pcsc-lite (1.9.5-3ubuntu1) jammy; urgency=medium

  * Fix dh_installsystemd doesn't handle files in /usr/lib/systemd/system.
    Closes: #103429 and LP: #1971984

 -- Brian Murray <email address hidden> Tue, 27 Jun 2023 16:46:08 -0700

[Ubucolors (ubucolors)]

Thank you Andreas, the Ubuntu bug Team did a great job.

Op do 27 jul 2023 om 22:31 schreef Andreas Hasenack <
<email address hidden>>:

> The verification of the Stable Release Update for pcsc-lite has
> completed successfully and the package is now being released to
> -updates. Subsequently, the Ubuntu Stable Release Updates Team is being
> unsubscribed and will not receive messages about this bug report. In
> the event that you encounter a regression using the package from
> -updates please report a new bug using ubuntu-bug and tag the bug report
> regression-update so we can easily find any regressions.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971984
>
> Title:
> pcscd.socket is disabled after installation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
>
>