macos 26.4 and custom keychain - doesn't unlock

[arekm]

Are your custom keychains unlocking fine after update to 26.4 (from 26.3.x) ?

Here it behaves just like wrong password entered. Even if I use old copies of keychain db files.

Edit: from gui it failed every time but worked from cmdline via "security unlock-keychain" command.

 

[IcePic]

I got this for Chrome, it can't unlock its keychain anymore after 26.3 -> 26.4, claims the pw is bad, but its the same as my login pw and the sudo pw which both work nicely. Super annoying.

 

[ibash]

I had this issue too. The keychain access prompt continually rejected my password (even though I confirmed it was correct with sudo). This is what finally fixed it for me:

In a terminal:

mv ~/Library/Keychains ~/Library/Keychains.old
sudo reboot

 

[IcePic]

I had this issue too. The keychain access prompt continually rejected my password (even though I confirmed it was correct with sudo). This is what finally fixed it for me:

In a terminal:

mv ~/Library/Keychains ~/Library/Keychains.old
sudo reboot

That solves the problem of not being able to get macos to accept what you type, but it seems "forgetting all secrets" is the last choice to fix this, not the first one.
I managed to unlock the chrome keyring from CLI with "security -v unlock-keychain <keychain_path>" and entering the expected password. From that point on, I could have chrome read its keychain again, but there is still a bug where the graphical pw reader is not reading pws correctly.

 

[IcePic]

And now 26.4.1 came out and it unlocks again.