After quiet some more upgrade- and downgrade dance, things seem to work
mostly correctly now. What I did:
After another upgrade, that ended up with a broken system again, I tried
removing my existing kwallet (mv .local/share/kwalletd/ kwallet_orig). I
then created a new gpg-protected wallet.
This helped partially (I could add a password for my Wireless network or
for Nextcloud again) but not fully. KMail was still unusable failing to
even open the settings for my IMAP account.
So I removed the new wallet, moved the old back into place and
downgraded again to 6.13.0-1.
After rebooting into the old system KDE asked me to create a new default
wallet again. Again I selected a gpg-protected wallet. Now I had to
reregister all passwords but this worked. And even KMail now managed to
save passwords into the new wallet. In KWalletManager I found both the
old and the new wallet and could open both of them.
Now I just upgraded kwallet again and after another reboot, everything
seems to be happy using the new wallet. In KWalletManager I still see
both my wallets.
HOWEVER: Trying to open the old wallet in KWalletManger crashes the
WalletManager and seems to block KMail again. Logging out and back in
does not help, only rebooting does.
Given this observations, it seems that there are still quiet some rough
edges here.
1. There should be a path to migrate an existing wallet automatically.
2. The upgrade should make sure a new wallet exists before it removes
the ability to open old wallets.
3. Once the old wallets can not be opened anymore, no tool should try to
do so (or at least error out without crashing the whole wallet-system)
Hope this information helps smoothing out the upgrade process for future
users (and the forky release)
