Thank you Andreas, the Ubuntu bug Team did a great job.
Op do 27 jul 2023 om 22:31 schreef Andreas Hasenack <
1971...@bugs.launchpad.net>:
> 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
>
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
pcscd.socket is disabled after installation
Status in pcsc-lite package in Ubuntu:
Fix Released
Status in pcsc-lite source package in Jammy:
Fix Released
Status in pcsc-lite source package in Kinetic:
Won't Fix
Status in pcsc-lite source package in Lunar:
Fix Released
Status in pcsc-lite package in Debian:
Fix Released
Bug description:
[ 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
