On 08/29/2011 09:07 AM, 4ernov wrote: > I've worked some more on this bug with KWallet. > > It turned out finally that the cause of the bug is that somehow D-Bus > service of KWallet API library call is unregistered during this call > and kwalletd considers it as the application died while user is > entering the master password for wallet (there's special processing in > kwalletd for this case). What's more, it turns out that this call's > service is somehow exactly this: "org.kde.Akonadi.Firstrun.lock". > > To be more exact, the method KWalletD::slotServiceOwnerChanged is > called in kwalletd even before the password is entered (here's my > debug message): > kwalletd(30399) KWalletD::slotServiceOwnerChanged: name, oldOwner, > newOwner: "org.kde.Akonadi.Firstrun.lock" ":1.21" "" > > I looked at the code some more and found that the 'service' of the > (async) call (i.e. ":1.21") is taken from QDBusMessage.service(); in > KWalletD::openAsync method. > > Does someone know how such an aliasing could ever take place and what > could lead to such a situation? I think it's quite significant problem > as I guess it works like this for _every_ d-bus call from plasmoids. Thanks for the details analisys. Can you please give me more details about your running configuration? What KDE version, have you compiled from source, etc.
-- Valentin Rusu (IRC valir, KDE vrusu) KSecretsService (former KSecretService, KWallet replacement) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
