[Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[ipkpjersi]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1689825

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions