Page MenuHome GnuPG
Create Task
Maniphest T5767

scdaemon gets stuck on smartcard access
Closed, ResolvedPublic
Actions

Description

When I upgraded from 3.1.15 to 4.0.0 I noticed that operations involving smartcard access get stuck, i. e. the "call" to scdaemon is never finished and the scdaemon process causes ~15% CPU load.

The only way to "fix" this situation is by killing the scdaemon process.

Cases where this behavior occurs include:

  • gpg --card-status
  • gpg-connect-agent -> SCD SERIALNO
  • Accessing scdaemon via libassuan

By trial and error, I noticed that this is somehow caused by my scdaemon.conf's line:

reader-port "Yubico Yubikey NEO OTP+U2F+CCID"

As soon as remove the line (which makes the conf empty) and restart the scdaemon process, everything works fine. Maybe this is connected to change https://dev.gnupg.org/T5644.

Is "reader-port" not supported anymore or is this a bug with the new heuristic?

System specs:

  • WIndows 10 21H1 (19043.1415)

Details

Version
4.0.0

Related Objects

Event Timeline

JanMosigItemis created this task.Jan 10 2022, 2:28 PM
JanMosigItemis updated the task description. (Show Details)
ikloecker added a subscriber: ikloecker.EditedJan 10 2022, 5:01 PM

See T5758: scd: loop forever with reader_port, when open_pcsc_reader failed. Yes, the workaround is not to set reader-port.

• werner closed this task as Resolved.Jan 10 2022, 6:00 PM
• werner claimed this task.
• werner added a subscriber: • werner.

That is annoying enough that we should do a new release. I close this bug, though.