gnome-keyring mysteriously asks for keyring password on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-keyring (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: gnome-keyring
I recently (yesterday) upgraded from Karmic to Lucid. Now whenever I start up, gnome-keyring asks me for my keyring password. Note that I use a password to log in, and I also have a keyring password. So I am not using auto-login. What confuses me is that I cannot tell what application is trying to access the keyring. And when I am asked for my password, I am unable to switch to other applications, e.g. terminal, to perform any debugging.
This behavior did not occur before the upgrade.
As far as I know, I should not have to enter my keyring password until something actually has to use the keyring. And it should only unlock that portion of the keyring that it uses. But the dialog I get provides me with no information other than "an application wants to access the keyring".
From apt-cache policy gnome-keyring:
gnome-keyring:
Installed: 2.92.92.
Candidate: 2.92.92.
Version table:
*** 2.92.92.
500 http://
100 /var/lib/
From lsb_release -rd:
Description: Ubuntu 10.04 LTS
Release: 10.04
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-keyring 2.92.92.
ProcVersionSign
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed May 5 12:10:00 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: gnome-keyring
Changed in gnome-keyring (Ubuntu): | |
importance: | Undecided → Low |
Changed in gnome-keyring (Ubuntu): | |
status: | New → Confirmed |
I also just upgraded from Karmic to Lucid. I am using automatic login and before the upgrade I didn't need to enter my keyring password. Now it does ask me for it but I can't tell what application needs access. I have no problem minimizing the window and using my network connection without unlocking the keyring.