The ownCloud client is integrated with KDE's password manager (KWallet).
When it starts, it checks if the kwallet is unlocked and looks for the password.
Yeah, that's how it should be and that is a very software design. Unfortunately it has never worked and the ownCloud client asks for the password every single time!
In the latest version the problem is actually explained in the dialog ("No keychain available"):
In my case, which seems to be the default, the problem is that kwalletd is not running when the ownCloud client starts. It's a timing issue.
My solution :
1. Open KDE's "Autostart" control module (a quick search from the start menu will get you there)
2. Change the ownCloud entry to point to a script of your own.
3. Click OK.
4. Write the following shell script:
5. Make it executable.
6. Reboot (or kill kwalletd and try your script. Note that logging out doesn't kill the daemon.)
Of course if your KWallet is protected by a password, then you will be asked to provide it.
Vielen Dank. Hat jetzt endlich geklappt.
ReplyDeleteVielen Dank für Deine Mühe.
ein dankbarer User
5 stars, is perfect !
ReplyDeletethank so much.
kwalletd
ReplyDeleteQDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kwalletd(11960): Communication problem with "kwalletd" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message recipient disconnected from message bus without replying" "