[Bug 1971984] Re: pcscd.socket is disabled after installation

[Tony Espy]

** Description changed:

- Ubuntu Mate 22.04 with the latest updates.
- Problem is present with internal smart-card reader and also external usb smart-card reader.
+ [ Impact ]
  
- eid-viewer sees no card reader,but When i do:
+ The pscc-lite package provides an open source implementation of PC/SC,
+ the de-facto standard to interface Personal Computers with Smart
+ Cards/Readers.
  
- sudo pcscd -f
+ 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).
  
- it is working, also following the tips of Ludovic:
- https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html
+ This is especially painful for users that require Smart Authentication
+ for login.
  
- sudo systemctl stop pcscd.socket
- sudo systemctl start pcscd.socket
+ [ Test Plan ]
  
- It is working until next restart.
+ Steps to reproduce:
  
- libacsccid1  version: 1.1.8-1
- libccid version: 1.5.0-2
- pcscd version: 1.9.5-3
- eid-archive version: 2022.3
- eid-mw version: 5.0.28v5.0.28-0u2204-1
- eid-viewer version: 5.0.28v5.0.28-0u2204-1
+ 1. If installed, remove and do a fresh install of the package pcscd
+ (the sole version released for jammy is 1.9.5-3).
  
- In Firefox, my eid card is then also recognized, but only in the ESR
- version, but this is a know Mozilla bug.
+ 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.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1971984

Title:
  pcscd.socket is disabled after installation

Status in pcsc-lite package in Ubuntu:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions