https://bugs.kde.org/show_bug.cgi?id=511425
--- Comment #5 from Szőts Ákos <[email protected]> --- Frank, this is the solution that worked for me: https://forum.vivaldi.net/topic/109314/solved-can-not-pass-profile-launcher-after-update . Basically, within KWalletManager: 1. Use File > Export Encrypted to back up the current key storage. 2. Close, then Delete the entire key storage (same menu) named kdewallet. 3. Import the previously backed up key storage using File > Import Encrypted. 4. Another bug here, too: quit KWalletManager, and killall ksecretd and kwalletd6 (otherwise you wouldn't see the newly imported wallet and it wanted to recreate a new one with an "_1" appended to it..). Then restart all of them. 5. Start your misbehaving applications It fixed Vivaldi for me. I analysed the difference of the D-bus communication of both the bad and the good wallets. The only difference was in this call: ```diff ‣ Type=method_call Endian=l Flags=2 Version=1 Cookie=X Timestamp="X" Sender=:D Destination=:F Path=/org/freedesktop/secrets Interface=org.freedesktop.Secret.Service Member=GetSecrets UniqueName=:D MESSAGE "aoo" { ARRAY "o" { - OBJECT_PATH "/org/freedesktop/secrets/collection/kdewallet/1"; OBJECT_PATH "/org/freedesktop/secrets/collection/kdewallet/0"; }; - OBJECT_PATH "/org/freedesktop/secrets/session/33"; + OBJECT_PATH "/org/freedesktop/secrets/session/1"; }; ``` It seems in the bad case (marked with minus), there was another kdewallet collection (/1) and Vivaldi could not handle this case. Deleting and re-importing the very same wallet fix it somehow. There was another diff but I don't know if it's expected because of different timestamp or wallet: ```diff ‣ Type=signal Endian=l Flags=1 Version=1 Cookie=X Timestamp="X" Sender=:F Path=/ksecretd Interface=org.kde.KWallet Member=walletAsyncOpened UniqueName=:F MESSAGE "ii" { - INT32 22; - INT32 1433144397; + INT32 3; + INT32 1920261253; }; ``` -- You are receiving this mail because: You are watching all bug changes.
