Why do we need to run two kwalletd?

Thiago Macieira thiago at kde.org
Sat May 28 15:53:56 BST 2016

Em sábado, 28 de maio de 2016, às 16:14:23 BRT, Albert Astals Cid escreveu:
> El dissabte, 28 de maig de 2016, a les 10:19:59 CEST, Thiago Macieira va
> escriure:
> > Commit https://quickgit.kde.org/?
> > p=kwallet.git&a=commit&h=f7c1586264e029be50f3d9ca15ccad268a8c5601 renamed
> > the binary and the D-Bus name for kwalletd in the name of
> > coinstallability.
> > 
> > Coinstallation is fine, but as a consequence, people with mixed KDE 4 and
> > KF5- based systems now have two kwalletd running and often two
> > kwalletmanager running, with two icons in their systrays and little
> > information which is which.
> > 
> > Moreover, there are two sets of wallets, with subtle differences because
> > one was migrated off the other at some point in time, but then they
> > diverged.
> > 
> > Was that the correct/wise decision? Why not have *one* wallet for all
> > programs?
> I think it was not a wise decision, it was probably done for people thinking
> with a "KDE 5" mindset in which everything would move to KF5 & friends at
> the same time.
> I don't think it's an easily fixable solution at this point unfortunately,
> I'd like to be proven wrong :)

It's simple to make kwalletd5 acquire both D-Bus names, which would prevent 
kwalletd from doing so. I don't know how to prevent it from being launched in 
the first place, though, so we just need to make sure that kwalletd5 starts 

There also needs to be a way to migrate the contents of the old wallet into 
the new.

Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

More information about the kde-core-devel mailing list