https://bugs.kde.org/show_bug.cgi?id=511425
--- Comment #4 from Szőts Ákos <[email protected]> --- This is the debug log from the browser (nothing too interesting, it tells that it found the right provider): >VERBOSE1:chromium/components/os_crypt/sync/key_storage_util_linux.cc:49] >Password storage detected desktop environment: KDE6 >VERBOSE1:chromium/components/os_crypt/sync/key_storage_linux.cc:139] Selected >backend for OSCrypt: KWALLET6 >VERBOSE1:chromium/components/os_crypt/sync/key_storage_linux.cc:209] OSCrypt >using KWallet as backend. >VERBOSE1:chromium/components/os_crypt/sync/os_crypt_linux.cc:218] Decryption >failed >WARNING:extraparts/vivaldi_keystore_checker.cc:79] KeystoreChecker: Decryption >of the canary failed. Keystore may have changed! >ERROR:extraparts/vivaldi_keystore_checker.cc:163] KeystoreChecker: Profile >Default: Encryted keystore changed or is now unavailable. This may result in >lost cookies and other problems. >WARNING:extraparts/vivaldi_keystore_checker.cc:28] KeystoreChecker: >AskShouldAllowInsecureAccess: UI Is not available yet. Returning NO to >insecure access >ERROR:extraparts/vivaldi_keystore_checker.cc:168] KeystoreChecker: Keystore >unlock failed and user requested profile switch! Is there a way to inspect the communication between KWallet and the browser? -- You are receiving this mail because: You are watching all bug changes.
