New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 870228 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
vamshi.kommuri@chromium.org
maxwalker@chromium.org
cfroussios@chromium.org
█ tsabolcec@google.com
vasi...@chromium.org
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Saved passwords no longer loaded from sqlite database after last Chrome upgrade

Reported by tsuna...@gmail.com, Aug 2 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.23 Safari/537.36

Steps to reproduce the problem:
1. Upgrade to Chrome Version 69.0.3497.23 (Official Build) dev (64-bit)
2. Go to chrome://settings/passwords

What is the expected behavior?
Saved passwords should be loaded from sqlite database.  I can see them if I stop Chrom and open the DB manually (sqlite3 ~/Library/Application\ Support/Google/Chrome/Default/Login\ Data)

What went wrong?
No saved passwords show up.

Did this work before? Yes 

Chrome version: 69.0.3497.23  Channel: dev
OS Version: OS X 10.13.6
Flash Version: 

I also got logged out of my Google accounts after restarting Chrome with that last upgrade on the dev channel.

Comment 1 by tsuna...@gmail.com, Aug 2 

My bad, the problem wasn't with Chrome.  The safe storage key that Chrome stores in the OS X keychain was unavailable due to a hiccup with Keychain.  I realized this once I went to recover the passwords manually from the sqlite database.  When I tried to retrieve the safe storage key it prompted me for my password and kept returning a permission error even though I was entering the right password.  So instead I locked and unlocked the keychain and that somehow fixed it.  Restarting Chrome after this allowed it to recover both my passwords.

What's annoying is that there wasn't any indication anywhere that Chrome had failed to access the safe storage key.  I started Chrome with verbose logging enabled and didn't see any complaints.

Please close this issue unless you wanna take an action item to somehow alert the user when there is an error accessing Keychain (whether with a popup at startup or a verbose log message).

Comment 2 by swarnasree.mukkala@chromium.org, Aug 2

Labels: Needs-Triage-M69 Needs-Bisect

Comment 3 by vamshi.kommuri@chromium.org, Aug 3

Cc: vamshi.kommuri@chromium.org
Components: -UI UI>Browser>Passwords
Labels: -Needs-Bisect Triaged-ET
Thanks for filing the issue!

As per comment#1 it is clearly understood that the issue isn't with chrome rather it's with a missing safe storage key due to a hiccup with Keychain. Hence removing Needs-Bisect label.

Tentatively adding component "UI>Browser>Passwords" and requesting someone from respective team to have a look into this as reporter expects an alert from chrome when there is an error accessing Keychain(...as per comment#1).

Comment 4 by phanindra.mandapaka@chromium.org, Aug 14

Cc: phanindra.mandapaka@chromium.org
A Gentle ping...

@ UI>Browser>Passwords Requesting you to please respond to comment #3.

Thanks..!

Comment 5 by battre@chromium.org, Aug 14

Cc: vasi...@chromium.org cfroussios@chromium.org

Comment 6 by vasi...@chromium.org, Aug 14

Cc: tsabolcec@google.com maxwalker@chromium.org
Status: Available (was: Unconfirmed)
I guess we should add an indication of problems with the Keychain. Tonko is working on detecting the state.
►

Sign in to add a comment