On Tuesday, 12 April 2016 21:10:58 CEST, Erik Quaeghebeur wrote:
No, any change just triggers a new login, so in a request for the password.
So there's no error message next/underneath a password field in the setting dialog, right? That means that QtKeychain reports itself as working.
Ok, I was at 0.5.0. I've now updated to 0.6.2. After this update and a rebuild of git Trojita, I once got a request to access a wallet (I guess this is the plasma 5 one, as in the meantime I managed to get my kde 4 wallet ‘active’ again, but the Trojita passwords there don't seem to be picked up by Trojita, which is not surprising, as my qtkeychain is qt5-only.)
Whether your qtkeychain is qt4-only or qt5-only doesn't matter; it is only important in determining what applications can *use* this library for talking to a password backend.
The password backend to use is determined at runtime based on several criteria, including the currently running desktop environment. A Qt5-only qtkeychain can talk to kwalletd and kwalletd5 just fine.
After installing 0.6.2, I did get a symbol issue and segfault, but this was already with latest git.
Do you have a backtrace? This should have been fixed as of Thursday 7th, commit da070e70ca28761d58c1534e7bc88c9cd74cbd17.
Does the qtkeychain plugin log anything?
Nope; errors are shown to the user through the settings dialog. This should improve it: https://gerrit.vesnicky.cesnet.cz/r/698
-- Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
