Package: libpam-gnome-keyring
Followup-For: Bug #531695
X-Debbugs-Cc: [email protected]

Dear Maintainer,

The problem still exists here in all its glory just as it was described in 2009 
now,
after sixteen years, after upgrading to Trixie, and in Seahorse (which hides 
its name)
version 47.0.1-2. The only difference is that this time it applies to the 
fingerprint
login. (I followed the advice here to right-click on my login keyring in Gnome's
“Passwords and Keys” window and changed my login password there, then finally it
synchronised.) It seems that fingerprints are not part of the login keyring. I 
deleted and
re-entered my fingerprints but the situation remained the same.

   * What led up to the situation?

I log in using a fingerprint in the Greeter. A dialogue window forces me to 
enter my login
password even though I just logged in without an error.  But even then, when I 
call
Evolution, I cannot access my calendars because Evolution cannot access the 
passwords I
entered when I created each calendar's entry in Evolution. I have to not just 
quit
Evolution but

evolution --force-shutdown
pkill --echo keyring

and start Evolution again, which causes a dialogue window to appear that asks 
me for my
login password again. Then I can finally access my calendars.


-- System Information:
Debian Release: 13.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.57+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-gnome-keyring depends on:
ii  libc6           2.41-12
ii  libpam-runtime  1.7.0-5
ii  libpam0g        1.7.0-5
ii  libselinux1     3.8.1-1

Versions of packages libpam-gnome-keyring recommends:
ii  gnome-keyring  48.0-1

libpam-gnome-keyring suggests no packages.

-- debconf-show failed

Reply via email to