Unable to reproduce the issue on ubuntu 17.10 using chrome reported version #70.0.3538.67. Observed that kwalletd got started by Chromium as expected. The issue seems to be specific to Plasma 5. Hence, adding label TE-Hardware-Dependency.

Thanks...!!

krajshree@, could you please check the DBus service name of klauncher? Is it "org.kde.klauncher5" or "org.kde.klauncher"?

I can reproduce this problem exactly in a Kubuntu 18.04.1 LiveCD:

0. killall kwalletd and kwalletd5
1. Remove kde-runtime (provides kwalletd 4, which is not what we want)
2. Start chromium-browser --password-store=kwallet --enable-logging=stderr
3. Notice these lines in output:

[5450:5526:1025/114555.734177:ERROR:object_proxy.cc(615)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.kde.kwalletd: No such file or directory
[5450:5526:1025/114555.734218:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd (isEnabled)
[5450:5526:1025/114555.742707:ERROR:object_proxy.cc(615)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files
[5450:5526:1025/114555.742805:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd

I just dug through the source code and found that I should use "--password-store=kwallet5" to correctly invoke KWallet5 or something upper the call chain will try to set desktop_env to KDE4 to enforce KWallet4 in KWalletDBus (which I think is a strange idea, because it makes DE detection look broken for me while debugging KWalletDBus ctor).

And it seems KWallet5 can be dbus-activated(?) by calling the service name. Not sure about the KLauncher part then; It's obviously wrong in Plasma 5 because of the incorrect service name, but it's also not needed?

*** UI Mass Triage ***