![](https://seccdn.libravatar.org/avatar/f555ff5be093ee02ffb38d3ad7e10dca.jpg?s=120&d=mm&r=g)
On Monday, January 25, 2016 10:20:22 PM CST Chan Ju Ping wrote:
On Monday 25 Jan 2016 15:30:56 Neil Rickert wrote:
On 01/25/2016 11:20 AM, Chan Ju Ping wrote:
I always do an initial setup of Kwallet with GPG encryption, though in the latest upgrade, this has been automatically replaced with the simple passphrase method.
You have "kwallet4" and "kwallet5". The update of kmail left you using "kwallet5".
For me, "kwallet5" uses gpg encryption. But you probably set it up before gpg support was available for "kwallet5".
Good call. That was the missing package.
Here's what I would do in your situation: 1: Install kwalletmanager5 (if not already installed). This might
remove kwalletmanager (the "4" version). Maybe run that one last time to be sure you have the settings that you want.
2: Using "kwalletmanager5", save the content of kwallet5 to a file.
If you have an encrypted partition, that might be a good place to save it.
3: Delete "kwallet" related files from ".config" and
".local/share/". It might be best to do that while logged into Icewm or at a command line session, so that you are not logged into KDE.
4: Log back into KDE and reinitialized "kwallet". There should be
an option to use "gpg".
5: Using "kwalletmanager5", read your saved kwallet content back in
from where you saved it.
6: After checking that all is good, you can shred the saved copy of
kwallet content ("shred" command).
I find that I have had to ressurect this thread because today's update completely reset Kwallet5 setups on both my computers running TW. In fact, there does not seem to be a way to re-engage the KWallet5 subsystem to create a new wallet protected using gpg keys. Has something else changed today to cause this? And is there a manual way to tell KWallet to use GPG keys? I have tried renaming the kwallet related files (e.g. kwalletmanager5rc > kwalletmanager5rc.bac) in .config/ and .local/share to something else, to no avail.