Problems with kdepim4

[Fernando Rodriguez]

On Monday, May 25, 2015 06:32:47 PM you wrote:
> On Mon, May 25, 2015 at 6:13 PM, Fernando Rodriguez <
> 
> frodriguez.developer at outlook.com> wrote:
> > If you don't want to type a password every time the workaround is to set a
> > kwallet with a blank password. I tried to do the same with the native
> > keychain
> > and it won't let me. So unless somebody knows how it can be done I have to
> > go
> > back to kwalletd :(
> 
> You probably want to go into the keychain settings then, because you have
> set things to a non-default state. The OS X keychain is normally unlocked
> whenever you authenticate (login or screensaver) and stays unlocked unless
> you lock it (including activating screen lock --- but again, it is unlocked
> by unlocking that).
> 
> You may get a prompt the very first time asking if the app is allowed to
> use the password. Click "Always allow" and it won't ask again.


Are your KDE apps using the "login" keychain or "kdewallet"? Mine is using the 
"kdewallet" keychain but that keychain is not showing on either Keychain 
Access or kwalletmanager. I thought it may be because my settings where messed 
up from the other kdelibs4 variant but I deleted the following directories:

~/.config
~/.local
~/Library/Preferences/KDE

Then I started kmail and recreated my account and it still wants to use the 
"kdewallet" keychain. I can tell the keychain exists because it only accepts 
the password that I set when I created it but it's not listed anywhere. Am I 
missing any config directories?

BTW. Switching to this variant fixed the original problem with google's 
certificate. So thanks @Rene.


-----------------------------------------