Hmmm...
It seems the pcscd unit is running, but it is also spamming some kind of error 
into the system logs. Very interesting. I'll have to dig at the error message a 
bit more, but that looks like a solid potential lead.

$ systemctl status pcscd
● pcscd.service - PC/SC Smart Card Daemon
     Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; preset: 
enabled)
     Active: active (running) since Tue 2025-09-16 23:38:30 MDT; 22h ago
 Invocation: 33a96b1ea7c84ffaa73e794aee06f808
TriggeredBy: ● pcscd.socket
       Docs: man:pcscd(8)
   Main PID: 5028 (pcscd)
      Tasks: 10 (limit: 74802)
     Memory: 3.8M (peak: 5.2M)
        CPU: 938ms
     CGroup: /system.slice/pcscd.service
             └─5028 /usr/sbin/pcscd --foreground --auto-exit

Sep 17 22:12:59 <hostname> pcscd[5028]: 00000002 
../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Sep 17 22:13:05 <hostname> pcscd[5028]: 06651108 
../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Sep 17 22:13:05 <hostname> pcscd[5028]: 00000008 
../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Sep 17 22:13:05 <hostname> pcscd[5028]: 00000002 
../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Sep 17 22:15:53 <hostname> pcscd[5028]: 99999999 
../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Sep 17 22:15:53 <hostname> pcscd[5028]: 00000008 
../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Sep 17 22:15:53 <hostname> pcscd[5028]: 00000002 
../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5
Sep 17 22:16:00 <hostname> pcscd[5028]: 07766588 
../src/winscard_svc.c:404:ContextThread() Communication protocol mismatch!
Sep 17 22:16:00 <hostname> pcscd[5028]: 00000009 
../src/winscard_svc.c:406:ContextThread() Client protocol is 4:4
Sep 17 22:16:00 <hostname> pcscd[5028]: 00000003 
../src/winscard_svc.c:408:ContextThread() Server protocol is 4:5

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2089141

Title:
  Opensc smart cards do not work in the snapped browsers

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Opensc supported smartcards can now be loaded in Firefox so:

  First connect the PCSCD interface:

    snap connect firefox:pcscd

  To load the module, write this path in Settings > Security devices >
  Load:

    /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so

  The file picker messes with the path, do NOT use it!

  Context
  -------

  This bug was created for reference. It was split from LP:1967632,
  which reference smart cards in general, and although many (most?) are
  supported by Opensc, many are not, so that bug cannot be closed yet,
  while this can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2089141/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to