summaryrefslogtreecommitdiffstats
path: root/tools/bisect-builds.py
diff options
context:
space:
mode:
authormdm@chromium.org <mdm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-05-02 20:24:09 +0000
committermdm@chromium.org <mdm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-05-02 20:24:09 +0000
commitac31b2d53a52ddea32261ab021426ebdb7c2907e (patch)
treec4fa0149bd2c998061f0718a1dfa3032f2261f5e /tools/bisect-builds.py
parent50b72f450f73c9ce70cc60663b91cdf939915783 (diff)
downloadchromium_src-ac31b2d53a52ddea32261ab021426ebdb7c2907e.zip
chromium_src-ac31b2d53a52ddea32261ab021426ebdb7c2907e.tar.gz
chromium_src-ac31b2d53a52ddea32261ab021426ebdb7c2907e.tar.bz2
Linux: attempt to write a dummy value to the native password store to get it to
unlock when there are no passwords to migrate into it on startup. This avoids sometimes choosing the unencrypted store on startup if the native store was locked, and may be related to bugs 80727, 78675, and 80738. BUG=80727,78675,80738 TEST=starting linux chrome with locked keyring should always prompt to unlock the first time the password store is used, e.g. by sync or chrome://settings/passwords Review URL: http://codereview.chromium.org/6902187 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83773 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/bisect-builds.py')
0 files changed, 0 insertions, 0 deletions