https://bugs.kde.org/show_bug.cgi?id=504014
--- Comment #48 from bastimeyer...@gmail.com --- (In reply to Patrick Silva from comment #47) > I installed kwallet 6.14.1-1 on Arch Linux a few hours ago. If I disable > kwallet in its KCM, Chromium opens without any delay, but it does not load > any url until reboot. And after reboot with kwallet disabled, Vivaldi > browser does not open as expected with my current profile; I get the window > seen in the attached screenshot instead. This is unlikely an issue with kwallet. You can't switch back-and-forth between different password stores in Chromium-based applications, meaning you can't disable and enable kwallet without "breaking" the data of your browser's user-data-dir. Once kwallet has been enabled, Chromium will use it and encrypt sensitive user data (not just passwords), and it will also translate old data from the unencrypted "basic" password store that was used when kwallet was disabled. However, when disabling kwallet again after it had been enabled, Chromium won't be able to read sensitive user data anymore, as it has been encrypted, resulting in a broken profile. Either keep kwallet enabled or create a new user-data-dir. - https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux/password_storage.md - https://wiki.archlinux.org/title/Chromium#Force_a_password_store - https://wiki.archlinux.org/title/Chromium#Launch_a_new_browser_instance This back-and-forth was the reason why I reverted to older BTRFS system+home snapshots until this issue got resolved, because it had messed with my Chromium browser/application profiles while I was figuring out the cause of the issue. -- You are receiving this mail because: You are watching all bug changes.
