After upgrade from 5.28.0 to 5.29.0 i can't open my wallets anymore. if i start kwalletd and kwalletmanager on commandline i get this output: ~ $ kwalletd(13467) passwordXXXXX_SHA512: Can't get secure memory: 16777217 kwalletd(13467) KWallet::Backend::openInternal: Wallet new enough, using new hash kwalletd(13467) KWallet::Backend::swapToNewHash: Runtime error on the new hash Oops, secure memory pool already initialized kwalletd(13467) passwordXXXXX_SHA512: Can't get secure memory: 16777217 kwalletd(13467) KWallet::Backend::openInternal: Wallet new enough, using new hash kwalletd(13467) KWallet::Backend::swapToNewHash: Runtime error on the new hash If i start kwalletd5 on commadline i get this when trying to open a wallet: kwalletd5: Checking for pam module Lacking a socket, pipe: 0, env:0 kwalletd5 started Migration agent starting... old wallets were already migrated Migration agent stop. Can't get secure memory: 16777217 Wallet new enough, using new hash Runtime error on the new hash fsize: 3453645513 encrypted.size(): 3064 blksz: 8 Oops, secure memory pool already initialized Can't get secure memory: 16777217 Wallet new enough, using new hash Runtime error on the new hash fsize: 2198704151 encrypted.size(): 3064 blksz: 8 Any suggestions what to do here?
After some investigation, including all stuff that may include encryption, i found that this lib dev-libs/libgcrypt-1.7.4 was upgraded to. I downgraded to =dev-libs/libgcrypt-1.7.3 (just a shot in the dark). Now i can open the wallets again. Is this a bug or is this some breaking change in libgcrypt?
Maybe it's related to this one: https://lists.gnupg.org/pipermail/gcrypt-devel/2016-December/004047.html
Update to libcrypt-1.7.5 solved the problem.