Bug 361860

I tried to setup automatic unlock on login, but the unlock always failed.

As soon as I renamed my wallet to “kdewallet”, the unlock worked.

Reproducible: Always

Steps to Reproduce:
1. Set up automatic unlock e.g. after this guide: https://wiki.archlinux.org/index.php/KDE_Wallet#Unlock_KDE_Wallet_automatically_on_login
2. create a new wallet with blowfish backend, using e.g. “kwallet” as the name.
3. delete the default “kdewallet”
4. or explicitly choose the new wallet as default wallet in the settings menu

Actual Results:  
The unlock fails:

kwalletd5: Wallet failed to get opened by PAM, error code is -9
kwalletd5: fsize:  2765156783  encrypted.size():  53520  blksz:  8
kwalletd5: Wallet new enough, using new hash
kwalletd5: kwalletd5 started

Expected Results:  
The unlock succeeds.

I looked around in the kwallet code to find out what the error code -9 actually means, it seems to come from here:
https://github.com/KDE/kwallet/blob/master/src/runtime/kwalletd/backend/backendpersisthandler.cpp#L414

I'm reporting this because the code seemed like it would actually support encrypting whatever wallet is currently set as default wallet, in contrary to this statement found in the arch wiki:

Note: Currently, pam_kwallet-git / kwallet-pam has at least two limitations: first, it's not compatible with GnuPG keys, so KDE Wallet must use the standard blowfish encryption. Also, the wallet name must be "kdewallet" (that's the default name). If, for some reason, you create a new wallet, you need to use this name (so you will probably need to rename the old wallet too).