Sorry for unclear text, yes, I meant KWallet API, you're right. Here's
those method itself:
bool MicroBlog::enterWalletFolder(const QString &folder)
{
//TODO: seems a bit silly to have a function just for this here
//why doesn't kwallet have this itself?
m_wallet->createFolder(folder);
if (! m_wallet->setFolder(folder)) {
//kDebug() << "failed to open folder" << folder; // <-- on
startup it fallbacks here
return false;
}
//kDebug() << "wallet now on folder" << folder;
return true;
}
And yes, it looks like a racing condition very much, perhaps, with
kwalletd daemon. But is there any way to ensure that it's already
started? And should it be checked in client or I can ask some KDE part
about it?
2011/8/23 Thiago Macieira <thi...@kde.org>:
> On Tuesday, 23 de August de 2011 11:32:20 4ernov wrote:
>> When the plasmoid starts on KDE startup, KWallet reports that it
>> failed to open the certain directory in the wallet
>> (setFolder(QString::fromLatin1("Plasma-MicroBlog")). In all other
>> cases it opens directory successfully.
>>
>> Is there any related issues in KWallet or maybe some hints how to use
>> KWallet in plasmoids? I tried to find example code in other plasmoids
>> but suddenly found that most of them save user data in config files.
>> Perhaps, one should even avoid using KWallet in plasmoids?
>
> When you say "KWallet reports", what exactly is KWallet in that question?
>
> Is that the KWallet API? Or the kwalletd daemon?
>
> There's a world of difference. The API might fail because the daemon isn't
> running yet. I suggest you investigate if this is the case.
>
> If the daemon reports that the folder cannot be opened, then it looks like a
> serious bug in the daemon.
>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
> Software Architect - Intel Open Source Technology Center
> PGP/GPG: 0x6EF45358; fingerprint:
> E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
