I'm running into inconvenience because the global password manager (gnome keyring?) that should fill in auth dialogs in Chromium doesn't trigger. For example, I'm accessing some webpage that asks for basic HTTP auth, or simply a login form I've already accessed and for which Chromium has already stored my credentials.
The expected flow would be
- the global pw manager popping up once per session, the first time I load the page (or periodically in a session, like sudo works, for example),
- demanding my password,
- then filling in the browser auth dialog.
Instead, nothing happens, unless I sidestep this by doing some other action that finally triggers the password manager, e.g. installing-uninstalling some program in Ubuntu's software center. After triggering the password dialog in this manner, and refreshing the relevant pages in Chromium, passwords and credentials are filled in as expected, but this is far from ideal. I cannot find links to other people experiencing this problem. Does anybody know how to solve this?
It seems I'm running into a similar issue as the one detailed in this SU question. In my case, both "Enable Autofill..." and "Offer to save passwords..." are checked. When I first login (autologin is enabled), e.g. when turning on the computer, the Saved Passwords list is empty. After doing something that requests the global password manager's attention, such as the aforementioned installing something through the Software Center, the list is full of stored credentials.
I checked, and it doesn't seem to be a difference between starting a session with automatic login (where I don't have to input my password) or starting my session by entering a password (I tried closing the session, the system then asked me for my password, but autofill was still unavailable.)
I checked Seahorse, and I see two different password keyrings: the "Session Start" one, which only contains one item: "Unlock password for Default (Google Chrome password)" and the "Predeterminado" keyring, which indeed holds all my Google Chrome passwords, and probably more. Problem is, the "Default" keyring is not unlocked by logging in.
I also tried replacing the "login" keyring with the "Predeterminado" (Spanish for "Default") one, as mentioned in this answer, but that didn't work either, and in fact that made the chromium password autofill stop working entirely.