qtkeychain
qtkeychain copied to clipboard
KDE: Starting owncloud-client when other applications wait for opening wallet, crashes kwallet
I'm using KDE and I've configured it that it restores my session after login. So there are a few applications started which uses kwallet at the same time. But I'm only asked once for the wallet password. Since the owncloud-client uses qtkeychain I can't autostart it anymore. When it starts and there is already an open request for opening a wallet, this leads to some strange behavior of the wallet. Entering the master password will not succeed, the password dialog will appear again and again, but with an hidden password already in the text box. So I have to kill kwalletd and restart all affected applications. I'm not sure how to give any further information, but it would be nice, if this annoying bug could be fixed. I think the idea of this library is very good and I am surprised that there are not more applications already using it. Unfortunately the KDE support seems to be a bit broken. I think that there shouldn't be so many qt dependencies is the reason for implementing things very different to this example?! http://techbase.kde.org/Development/Tutorials/KWallet With this example the default wallet issue would also be solved.
This is the version I have with which the issue still happens: libqtkeychain0-0.20130221-7.1.x86_64 KDE: kdelibs4-4.10.5-1.101.1.x86_64 openSUSE 12.3
Also tried with the latest source code (6747027ce71ecaa6690d579533506da5cb3ba62a) but the issue still happens.
Might be worth a try using KWallet directly instead of dbus. The crash could also be a bug in KWallet and dbus.
Very likely to be KWallet + dbus, there's an old ticket here where someone had an autostart script that triggers the issue: https://bugs.kde.org/show_bug.cgi?id=266228
@maystar can you try again with KDE 4.10.5 ?
I think I mixed up two issues:
- the crashing of kwallet where no wallet can be opened afterwards, which is what you reported
- the timeout that occurs in owncloud-client if no password has been entered after some time
I haven't been able to reproduce 1) so far. It's likely to have been fixed by https://bugs.kde.org/show_bug.cgi?id=254198
The second one can still be reproduced if you just wait long enough and don't input a password in kwallet, which is a separate issue.
Arghh, just go the kwallet crash again today after a fresh computer restart. I'll follow up in https://bugs.kde.org/show_bug.cgi?id=254198 as it's likely to be a kwallet bug.
Ok sorry, my mistake. It seems it has been fixed in KDE 4.11 according to that ticket. I'll update this ticket once I'll have tried with KDE 4.11
@PVince81 is this still hot?
Haven't seen this in a long while