Re: [Kde-pim] kmail2 v5.1.1. and kwallet

ianseeks <[email protected]>
Newsgroups gmane.comp.kde.users.pim,gmane.comp.kde.devel.pim
Message-ID <2861922.0qsrQ7Ufur@lianli>
On Monday, 8 February 2016 23:10:41 GMT Martin Steigerwald wrote:
> Am Montag, 8. Februar 2016, 18:50:41 CET schrieb Andreas Gungl:
> > Am Sonntag, 7. Februar 2016, 23:58:55 CET schrieb ianseeks:
> > > On Sunday, 7 February 2016 11:13:12 GMT Mike Mikowski wrote:
> > > > The solution I found running running Neon on Ubuntu 15.10 with the
> > > > backports ppa enabled:
> > > > 
> > > > $ # remove all kwallet config files
> > > > $ sudo pkill kwallet
> > > > $ cd /user/bin
> > > > $ sudo mv kwalletd kwalletd.O
> > > > $ sudo ln -s kwalletd5 kwalletd
> > > > $ kwalletmanager5
> > > > 
> > > > That worked wonders for me!  I hope it helps you!
> > > 
> > > thanks, i'll give that a go.  I'm sure kwallet is supposed to easier
> > > than
> > > it seems.
> > 
> > Hello, I'm on OpenSUSE Tumbleweed, and I experienced similar problems.
> > I've
> > found that Akonadi uses a wallet below ~/.local while walletmanager uses a
> > wallet below ~/.kde4
> > I didn't bother using a symlink or whatever,  just kept both wallets even
> > if it's a duplication. Of course, such things actually should not
> > happen...> 
> > :-)
> 
> Well, this in intentional. KDE SC + Plasma 4 uses ~/.kde, Plasma 5 + KDE
> Frameworks 5 use ~/.config.
Is there a way to find out which programs like kmail2 v5.1.1 use? 

> On first run of kwallet 5 stuff a migration wizard should pop up. It did for
> me. And yes, I´d keep both until you have nothing anymore that accesses
> kwallet 4.
> 
> Please also note that this is development mailing list. There is
> kdepim-users for user questions.
that was my fault, i picked the wrong one when asking the original question.
 
> Thanks,


_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.