login keyring does not get unlocked at login

[Cris]

Binary package hint: gnome-keyring

Hi,

on a new Karmic installation, suddenly my 'login' keyring does not get automatically unlocked when logging in.
Thus I get an annoying popup window asking me to insert the password the first time an application tries to access the keyring.

1. I've not changed my passwords
2. my login password is the same as the default keyring one
3. I've already tried to delete my ./gnome2/keyrings/login.keyring and recreate
    a new one without any luck

It just seems like the magic with pam_gnome_keyring isn't working anymore ...

Any help would be appreciated.

[Sebastien Bacher (seb128)]

Thank you for your bug report, seems rather a local issue than a bug

[Cris (cristiano.p)]

Thank you for your reply.

I've updated a bit the description and the title:
the right keyring is the 'login.keyring', which is supposed to be unlocked at login by the pam_gnome_keyring module.

Well, this used to work until yesterday morning; then suddenly, without any user configuration, stopped to work.

Interesting is that it does not seem to work anymore even for a newly created users.

[Cris (cristiano.p)]

The problem seems to be related to downgrading gdm to gdm-2.20.

Steps to reproduce:

1. downgrade to gdm-2.20 (e.g.: apt-get install gdm-2.20)
2. remove residual gdm's configuration files (e.g.: dpkg --purge gdm)
3. reinstall gdm-2.20 (e.g.: apt-get --reinstall install gdm-2.20)

Restart and login: the login.keyring does not get anymore unlocked automatically.

The following steps seem to solve the problem:
1. reinstall gdm (e.g.: apt-get install gdm)
2. downgrade to gdm-2.20 (e.g.: apt-get install gdm-2.20)
3. do not purge the gdm configuration!

[Asif Youssuff (yoasif)]

I am having this issue on Lucid, with

$ apt-cache policy gdm
gdm:
  Installed: 2.29.1-0ubuntu9
  Candidate: 2.29.1-0ubuntu9
  Version table:
 *** 2.29.1-0ubuntu9 0
        500 http://mirror.anl.gov lucid/main Packages
        100 /var/lib/dpkg/status

Should this bug be linked to gdm as well?

[Jim Rorie (jfrorie)]

Being seeing this since Lucid A1 on a fresh install. Definitely related to the wireless key.

[Sebastien Bacher (seb128)]

the issue seems rather a gdm-2.20 one then, reassigning the bug

[Gurubie (gurubie)]

sudo apt-get install gdm-2.20
E: Couldn't find package gdm-2.20

Didn't work; on current Ubuntu Lucid. FYI. May 1st.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.