Hi,
When some applications tries to access login information from my keychain, it asks for the password. This should unlock the keychain, right?
What happens on my macbook pro is that keychain status in the menu bar does not unlock in such a case. However, the system will act as if the keychain is unlocked (all applications will have access to their stored login information). This is probably because If I open keychain access, I find it unlocked, as it should be.
Briefly, the keychain status and the keychain access become unsynchronized. Then, locking/unlocking one of them will not affect the other and vice versa. To fix this problem, I have to hide the keychain status and show again.
I described above the case when this behavior occurs, but if I do not lock the keychain and just keep it unlocked by system login, they will be synchronized.
Has anybody faces such a problem or have a suggestion. First aid verification gives finishes completely with no problem.
I read a similar problem in a different forum but could not find it again. Could this be sue to some system update or so?!
Thanks,
When some applications tries to access login information from my keychain, it asks for the password. This should unlock the keychain, right?
What happens on my macbook pro is that keychain status in the menu bar does not unlock in such a case. However, the system will act as if the keychain is unlocked (all applications will have access to their stored login information). This is probably because If I open keychain access, I find it unlocked, as it should be.
Briefly, the keychain status and the keychain access become unsynchronized. Then, locking/unlocking one of them will not affect the other and vice versa. To fix this problem, I have to hide the keychain status and show again.
I described above the case when this behavior occurs, but if I do not lock the keychain and just keep it unlocked by system login, they will be synchronized.
Has anybody faces such a problem or have a suggestion. First aid verification gives finishes completely with no problem.
I read a similar problem in a different forum but could not find it again. Could this be sue to some system update or so?!
Thanks,