Bug#1035061: gnome-keyring: prevents chrome/chromium from running on a new account's first run

[Harold Grove]

Package: gnome-keyring
Version: 42.1-1+b2
Severity: normal
X-Debbugs-Cc: rgrove at rsu20.org

Dear Maintainer,

On a new account, gnome-keyring seems to prevent the first run of both Google
Chrome and Chromium. Restarting gnome-keyring-daemon.service works but requires
another unlock of the keyring. After this, Chrome/Chromium launches as
expected.
Thanks


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/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.14.6-1
ii  dbus-x11 [dbus-session-bus]                   1.14.6-1
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-4
ii  gcr                                           3.41.1-1+b1
ii  init-system-helpers                           1.65.2
ii  libc6                                         2.36-9
ii  libgck-1-0                                    3.41.1-1+b1
ii  libgcr-base-3-1                               3.41.1-1+b1
ii  libgcrypt20                                   1.10.1-3
ii  libglib2.0-0                                  2.74.6-2
ii  libsystemd0                                   252.6-1
ii  p11-kit                                       0.24.1-2
ii  pinentry-gnome3                               1.2.1-1

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  42.1-1+b2
ii  libpam-gnome-keyring  42.1-1+b2

gnome-keyring suggests no packages.

-- no debconf information