On Sunday 15 May 2016 17:45:01 J. Roeleveld wrote: > On May 15, 2016 11:56:45 AM GMT+02:00, Mick <[email protected]> wrote: > >I ran kwalletd5 on the recently migrated desktop and it will not accept > >the > >KDE-4 user's kwallet passwd. This is what it gives: > > > >$ kwalletd5 > >kwalletd5 started > >Migration agent starting ... > >Setting useNewHash to true > >Wallet new enough, using new hash > >fsize 4154251805 encrypted.size(): 40 blksz: 8 > >Application ' "KDE Wallet Migration Agent" ' using kwallet without > >parent > >window! > > > >any idea what I should do for the migration script to accept the > >passwd? > > In the upgrade guide there was mention of a specific USE flag to ensure > kwallet5 can read kwallet4 files.
(I think) I fixed the kwalletd5 problem. I gave up on running the *idiotic* migration, which should be semi-automatic if not completely transparent to the user, or at least accept the user's passwd if it can't read it from kwallet-4 and hacked chromium to use --password-detect=kwallet. This brought it back to the behaviour it had under KDE4. Kmail appears to be running the old kwalletd-4 daemon, but kwalletd5 runs at start up. I hope it won't give me any more problems. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
