Summary: | Regression: kwalletd5 breaks wallet access for applications like Chromium | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kwallet | Reporter: | Gunter Ohrner <kdebugs> |
Component: | general | Assignee: | Valentin Rusu <valir> |
Status: | RESOLVED UPSTREAM | ||
Severity: | grave | CC: | arojas, evangelos, kdelibs-bugs, rdieter |
Priority: | NOR | ||
Version: | 5.61.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=400462 | ||
Latest Commit: | Version Fixed In: |
Description
Gunter Ohrner
2019-08-16 21:55:03 UTC
Are there already any plans if - and if yes, when - this might be resolved? If it's not planned to be resolved, what are the recommended workaround? chromium works fine with kwallet 5.61. Are you perhaps calling it with "--password-store=kwallet" (In reply to Antonio Rojas from comment #2) > chromium works fine with kwallet 5.61. Are you perhaps calling it with > "--password-store=kwallet" Yes. How else can I make it work together with KDE Wallet from KF 5? Do you have any background documentation for me to get better insight into the big picture? I thought that without any argument, Chromium will default to it's unencrypted built-in passwort store. And besides this, a big warning before removing this functionality / changing it in an incompatible way would have been important, as you immediately lose access to all stored passwords once you upgrade... (In reply to Gunter Ohrner from comment #3) > (In reply to Antonio Rojas from comment #2) > > chromium works fine with kwallet 5.61. Are you perhaps calling it with > > "--password-store=kwallet" > > Yes. How else can I make it work together with KDE Wallet from KF 5? That's the problem then, you are explicitely asking it to use the deprecated kde4 interface. Use kwallet5 for the KF5 one. This is indeed quite poorly documented. https://chromium.googlesource.com/chromium/src/+/8917b83c677a8c632d5df666f72046f80c74472d (In reply to Antonio Rojas from comment #4) > That's the problem then, you are explicitely asking it to use the deprecated > kde4 interface. Use kwallet5 for the KF5 one. This is indeed quite poorly > documented. Thanks, this actually seems to work (even though I'm currently still on the old kwalletd, so I'll have to properly check this after upgrading again.) "Poorly documented" is some kind of understandment here, though - Chromium does not even list kwallet5 as a possible value for this option in it's command line help: --password-store=<basic|gnome|kwallet> Set the password store to use. The default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. (Note that KWallet may not work reliably outside KDE.) I reported this issue in the Chromium bug tracker: * https://bugs.chromium.org/p/chromium/issues/detail?id=1004785 The behaviour is even more annoying, as there does not seem to be a way to permanently select the default password store. As the Chromium command line help I quoted says, "The default is to automatically detect based on the desktop environment." And apparently, in KDE, also in KDE 5, and also with KF 5.61 and later, always "kwallet" seems to be chosen as the password store, never "kwallet5". This means, I cannot easily start Chromium via the desktop any more, but have to resort to the command line. (I could probably add a one-line shell script or adjust the *.desktop file for Chromium to start it with the right command line arguments, but that's not something I'd normally expect a user to have to do...) |