https://bugs.kde.org/show_bug.cgi?id=504014
bastimeyer...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bastimeyer...@gmail.com
--- Comment #8 from bastimeyer...@gmail.com ---
Please have a look at this thread on the Arch Linux forums:
https://bbs.archlinux.org/viewtopic.php?id=305540
Same issue on Arch Linux after a full system update today. Chromium didn't
start after updating kwallet to 6.14.0, despite kwallet being disabled in the
KCM.
Launching Chromium with the `--password-store=basic` launch option however
worked.
Enabling kwallet and rebooting also worked, though restarting Plasma alone
without a reboot didn't (which I guess was probably related to kwallet DBus
changes and not restarting the `dbus.service` too, but I'm not sure).
Disabling kwallet again after the reboot also worked, meaning Chromium launched
just fine, but it had messed with the profile data, because Chromium had
switched to kwallet after enabling it. For some reason, the
`--password-store=basic` launch argument resolved that, despite kwallet being
disabled again. A bit annoying, but I can live with that...
> Why should these browsers need kwallet to work?
As shown in the linked thread, Chromium always queries the kwallet DBus
interfaces in order to check whether kwallet is enabled. If it's not, or if the
user has set `--password-store=basic`, then it uses the "basic" password store
implementation ("password store" affects all sensitive user data, like cookies,
etc.).
-
https://github.com/chromium/chromium/blob/136.0.7103.92/components/os_crypt/sync/key_storage_kwallet.cc#L58-L71
-
https://github.com/chromium/chromium/blob/136.0.7103.92/components/os_crypt/sync/kwallet_dbus.cc#L109
So my guess is that updating kwallet to 6.14.0 requires a reboot (or
`dbus.service` restart), otherwise its initial query gets stuck and times out
after the default timeout value it uses (which may be quite long).
Btw, my kwallet KCM froze and crashed the system settings before rebooting. I
couldn't generate a log from this, unfortunately.
--
You are receiving this mail because:
You are watching all bug changes.
