Re: [Evolution] Keyring Password issues again!!

[Adam Tauno Williams <awilliam whitemice org>]

On Sat, 2013-08-10 at 18:05 +0100, David wrote:
> On Tue, 2013-08-06 at 17:29 +1200, Chris and Tracey wrote:
> > Has anyone else faced this? 
> >
> > Kernel : Linux 3.2.0-4-486 (i686)
> > Compiled : #1 Debian 3.2.32-1
> > Distribution : LMDE Xfce Edition - Running Mate
> >
> > Starting Evolution (3.4.4) - and what started out as a minor
> > irritation is now a major. I used to be able to just minimize it and
> > see email and send receive ok. 
> >
> > Now It will not give me that option as a work around. I actually found
> > the password that worked last week and then the last few days that
> > stopped!
> >
> > I tried an earlier terminal fix for the same problem I had last year. 
> > sudo sed -i 's/gnome_keyring/mate_keyring/g' /etc/pam.d/*
> > Logged out - restart and problem still persists
> > That didn't work either. I also tried the "set password in default to
> > blank/empty" that didn't work as well!
> > Anyone got a clue how to remove keyrings without knowing the
> > passwords?

You can manage your keyrings via Seahorse; including deleting, locking,
unlocking, changing the password, etc...    

The unlocking and password changes happen automatically if PAM is
correctly installed and configured.

> I'm running Evolution 3.6.2 on a Mint 14 XFCE 4 system.
> Mine keeps forgetting to open the keyring, luckily I know the password,
> it's the same as my login password.

That is configured in PAM.

Something like:

session optional        pam_gnome_keyring.so    auto_start
only_if=gdm,gdm-password,lxdm,lightdm

So your login password unlocks the keyring when you login; as only the
PAM stack actually has the password you entered.  If it doesn't work it
is mostly likely that your distribution or packagers screwed this up.  

I recall having this issue awhile ago, so maybe there was some issue
with packages around the 3.4.x vintage.  But I don't recall it [on
openSUSE at least] on 3.6.x, and my 3.8.x installs do not have this
problem.

This is really not an Evolution problem, it just uses the keyring in the
state that it finds it [available/unavailable, locked/unlocked].


-- 
Adam Tauno Williams <mailto:awilliam whitemice org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA