https://bugs.kde.org/show_bug.cgi?id=504014
--- Comment #21 from bastimeyer...@gmail.com --- > It's the other way around: the browser is asking KWallet if it's available. > But after the update, it seems KWallet fails to respond when it's disabled. Exactly this. I have posted the relevant Chromium code parts in my previous comment, where it checks `isEnabled` on the dbus first (after detecting KDE Plasma as my DE). https://bugs.kde.org/show_bug.cgi?id=504014#c8 I have since rolled back my entire system to earlier BTRFS snapshots (both / and /home), because I don't want to deal with this major breakage that affects multiple applications. However, on KWallet 6.13.0, when it's disabled (right now on my system), there's nothing on my dbus session bus. The Chromium logs also show this. Chromium attempts to check on the session bus whether KWallet is enabled, as it has detected Plasma as my DE and thus does this by default, but it can't find the dbus interface and then switches to the "basic" password store, which is what I want (without having to force the `--password-store=basic` launch option). Here's the respective log ``` [124261:124261:0514/113826.513583:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: KDE6 [124261:124261:0514/113826.513592:VERBOSE1:components/os_crypt/sync/key_storage_linux.cc:116] Selected backend for OSCrypt: KWALLET6 [124323:124323:0514/113826.569782:WARNING:sandbox/policy/linux/sandbox_linux.cc:415] InitializeSandbox() called with multiple threads in process gpu-process. [124323:124323:0514/113826.570302:VERBOSE1:components/viz/service/main/viz_main_impl.cc:85] VizNullHypothesis is disabled (not a warning) [124261:124261:0514/113826.628698:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected [124261:124261:0514/113826.628715:ERROR:components/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled) [124261:124261:0514/113826.628803:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable [124261:124261:0514/113826.628809:ERROR:components/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6 [124261:124261:0514/113826.628812:WARNING:components/os_crypt/sync/key_storage_linux.cc:189] OSCrypt tried KWallet but couldn't initialise. [124261:124261:0514/113826.744174:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected [124261:124261:0514/113826.744199:ERROR:components/os_crypt/sync/kwallet_dbus.cc:412] Error contacting kwalletd6 (close) ``` > reading various comments, i don't have exactly clear whether this happens > when kwallet is actually enabled or disabled. To repeat what happened after updating to 6.14.0 without enabling KWallet: Chromium simply hang. It didn't show its window and didn't respond to SIGTERM. This indicates that the dbus calls for checking KWallet hung. After enabling KWallet 6.14.0 and rebooting, Chromium worked, but re-visiting the KWallet KCM before the reboot made it crash (together with the system settings application). Enabling also caused corruption in Chromium, as the previous profile data was based on the "basic" password-store (affecting all kinds of stored sensitive data). Disabling 6.14.0 again made Chromium once again hang. And the KCM also crashed before rebooting. Enabling and disabling always required a system reboot to take effect. ---- Current kwalletrc on 6.13.0: ``` $ cat ~/.config/kwalletrc [Wallet] Close When Idle=false Close on Screensaver=false Default Wallet=kdewallet Enabled=false Idle Timeout=10 Launch Manager=false Leave Manager Open=false Leave Open=true Prompt on Open=false Use One Wallet=true ``` -- You are receiving this mail because: You are watching all bug changes.
