Comment 114 for bug 1689825

> This bug is not resolved. Seeing it under 16.04LTS without
> dbus-user-session or flatpak installed.

I can reliably reproduce the issue of the keyring not being automatically unlocked at startup in an up-to-date 16.04 VM without dbus-user-session installed. Not seeing any application slowdown though, chromium doesn't block at startup, but it does pop up a dialog prompting to unlock the keyring.

That VM was configured to automatically log in the only user account though, and I had removed the user's password. After setting back a password for the user and disabling the automatic login, I verified that the keyring was correctly unlocked after logging in.

To everyone affected:
 - can you comment on whether you're seeing application slowdown/blocking when the login keyring is not unlocked?
 - can you share whether automatic login is enabled, and whether you have unset your user's password (this is not recommended)