Comment 110 for bug 1689825

Any update on this issue? I do not feel comfortable removing dbus-user-session as a workaround, and I have simply added --password-store=basic as an argument for Chromium/Chrome for now. However that is not completely suitable even though I only use Chromium/Chrome as a secondary browser, and I am wondering if this issue is still being looked into, and am inquiring for perhaps more details about it if anyone has any more details like if the maintainers/developers of dbus-user-session (whoever they may be?) are aware of this bug, etc. I am using Ubuntu 16.04 and Xfce 4.12 and the latest google-chrome-stable, chromium-browser, dbus-user-session, etc. I see someone has stated back in August that using Ubuntu 17.10 with Gnome shell and gdm still produces this issue, I wonder if this is still the case or if this issue has been fixed by now at least on Ubuntu 17.10?

Also, on a side-note, does anyone know the exact details of what the password-store argument does? For example, if I turn password saving in Chromium off and don't use Google/Chrome sync, am I "safe" to log into websites without my passwords being stored in plain-text on my hard drive (even if temporary)?

I may end up looking into Kwallet to see if this is a suitable alternative to GNOME keyring at least for Chromium.

Thanks.