I am experiencing the same issue with a YubiKey 4. I have disabled pkcs11 and ssh support in gnome-keyring via the autostart method to no avail. I would be very interested in a workaround and/or fix for this behavior, which denies access to my smart card in a seemingly unpredictable way (probably depending on whether the gnome-keyring-daemon or the gpg-agent starts first).
On Thu, 09 Aug 2018 16:52:41 +0200 Wouter Verhelst <wou...@debian.org> wrote: > Package: gnome-keyring > Version: 3.28.2-1 > Severity: important > > Hi, > > When I log in to my session or start seahorse while gpg-agent isn't > running, I get a desktop notification: > > *Smart card is ready to use* > CryptoStick v1.2 (OpenPGP v2.0) > > At this point, I can no longer use gnupg or gpg-agent to access the > card, because gnome-keyring-daemon has locked it. > > Wtf? > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, m68k, arm64 > > Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages gnome-keyring depends on: > ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 > ii dbus-x11 [dbus-session-bus] 1.12.10-1 > ii dconf-gsettings-backend [gsettings-backend] 0.28.0-2 > ii gcr 3.28.0-1 > ii libc6 2.27-5 > ii libcap-ng0 0.7.9-1 > ii libcap2-bin 1:2.25-1.2 > ii libgck-1-0 3.28.0-1 > ii libgcr-base-3-1 3.28.0-1 > ii libgcrypt20 1.8.3-1 > ii libglib2.0-0 2.56.1-2 > ii p11-kit 0.23.12-2 > ii pinentry-gnome3 1.1.0-1+b1 > > Versions of packages gnome-keyring recommends: > ii gnome-keyring-pkcs11 3.28.2-1 > ii libpam-gnome-keyring 3.28.2-1 > > gnome-keyring suggests no packages. > > -- no debconf information > >
