UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36

Steps to reproduce the problem:
Reproduce my obscure environment:
1. Install Ubuntu 14.04 with full-disk encryption with luks.
2. Enable Auto-login to lightdm.
3. Change the user password (not the full-disc encryption password).
Now, Ubuntu does not unlock the gnome keyring after the auto-login.
(This is probably an Ubuntu bug)

Reproduce the Chrome bug (or rather: inconvenient behavior)
1. Open Chrome.
2. Go to a website, login, let Chrome store username/password.
3. Get prompted to unlock the keyring.
4. Reboot (gnome keyring is still locked after auto-login)
5. Go to the same website where the username/password has been saved by the Chrome password manager
6. Chrome will not unlock the gnome keyring, so it does not know that there are stored credentials for that website.

What is the expected behavior?
Chrome will make sure that the gnome keyring is unlocked such that it knows for which website there are saved credentials to fill in username/password.

What went wrong?
If I let chrome store my password, Chrome should make sure the gnome keyring is unlocked on Chrome startup.

Did this work before? N/A 

Chrome version: 50.0.2661.75  Channel: stable
OS Version: Ubuntu 14.04.4 LTS
Flash Version: