Linux – Disable KWallet password request in Arch Plasma 5

I found this

One annoyance of the free desktop at present is the use of incompatible systems for storing sensitive user data such as passwords. Every web browser may have its own password store and anyone using both KDE and Gnome applications will likely have to open both KWallet and Gnome Keyring in every desktop session.

Michael Leupold presented a collaboration between KDE and Gnome to develop a unified standard for storing secrets. The aim is that KDE and Gnome applications will both be able to share a common secrets architecture but still have separate graphical interfaces.

A KDE user will be presented with a KDE interface if they need to unlock an account in Empathy (the Gnome instant messaging application) while a Gnome user will see a Gnome interface for password management even if they prefer to chat using KDE's Kopete. It is also hoped that the standard will attract the support of other vendors, such as Mozilla.

this seems older, but might be a link to the actual project?

After having hinted at it now and then, I can finally gladly announced that we (GNOME Keyring + KDE Wallet) managed to kick off a joint freedesktop.org project with the goal of creating a common infrastructure (or more technically: protocol) for managing passwords and other secret values.

There is an option to "import" the old wallet in KWalletManager under File > Import Wallet. I found that my old wallet password was not accepted. Examination of the old folder revealed a salt file. I suspect (and further experimentation supports) that the kwalletd process has one salt file loaded and this one was not being read.

I was able to replace the new wallet file with the old one by replacing my new kwallet directory with my old one:

1. Turn off kwallet in System Settings > Account Details > KDE Wallet > Wallet Preferences > [Uncheck] "Enable the KDE wallet subsystem"
2. Remove $HOME/.kde/share/apps/kwallet and place your old wallet folder there
3. Enable the wallet subsystem (reverse of 1.)

If you need to "merge" two wallets and the import option is not working there are also "Export as XML" and "Import XML" options. You may export from one, switch wallets as above, then import. Be very careful about passwords being written unencrypted to disk! Once you have completed the import run the following command to securely overwrite and delete the XML file:

shred -u /path/to/exported/file

Note: overwriting files is not considered secure deletion on solid state storage media (flash drives, SSDs, etc) as wear leveling prevents exact blocks being written to. Instead, taking care to e.g. turn off swap and mount a RAM disk to write the XML file to are preferable, but that is out of the scope of this answer.