Please consider applying patch c9a9252d34a6 (KDE bug 504014)

Description:

Please consider applying
https://invent.kde.org/frameworks/kwallet/-/commit/c9a9252d34a63bb02a3756bf5e58441a42ad5928
to kwallet 6.14.0, which fixes
https://bugs.kde.org/show_bug.cgi?id=504014

This bug affects lots of people who use Plasma and have kwallet disabled and are using Chromium-based software, including Chromium itself. The browser/program doesn't launch for up to a minute because of a bug in kwallet 6.14.0 that results in a DBus query hanging and timing out eventually. When launching any kind of Chromium-based software, an initial check is made which password-store needs to be used. On Plasma, Chromium queries the respective DBus interface of kwallet and checks whether it's enabled and then chooses it as its password store. Otherwise, it's using its "basic" password store, which can also be forced via --password-store=basic. This CLI argument workaround however requires users to override/edit their .desktop launchers or launch scripts of all kinds of Chromium-based programs, which is annoying.

The bug was tagged as high-priority by the KDE team, but it was also tagged as fixed-in-6.15, so it was never cherry-picked onto kwallet's Frameworks/6.14 branch. Considering the release cycle/schedule of KDE frameworks and the severity of the bug, the patch should be backported here. https://invent.kde.org/frameworks/kwallet/-/commits/Frameworks%2F6.14

Additional info:

Steps to reproduce:

See upstream bug report

I have already applied the patch to my own kwallet build based on the current version of the PKGBUILD and it has successfully resolved the issue. All users should receive this bugfix as soon as possible IMO.

Thanks for your consideration.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information