Add a dummy entry with libsecret when initializing OSCrypt.

components/os_crypt/key_storage_libsecret.cc

Index: components/os_crypt/key_storage_libsecret.cc
diff --git a/components/os_crypt/key_storage_libsecret.cc b/components/os_crypt/key_storage_libsecret.cc
index 32c6d0905e17f1354b1c9e26ad2648ee9dd5b2ed..166a5b2360d4e74e10cef98a59c1020b623eff42 100644
--- a/components/os_crypt/key_storage_libsecret.cc
+++ b/components/os_crypt/key_storage_libsecret.cc
@@ -73,6 +73,8 @@ std::string KeyStorageLibsecret::AddRandomPasswordInLibsecret() {
 }
 
 std::string KeyStorageLibsecret::GetKey() {
+  LibsecretLoader::EnsureKeyringUnlocked();

[vasilii, 2016/10/28 09:36:24]

How often is this method called? Is it enough to unlock it once?

[cfroussios, 2016/10/28 11:21:22]

GetKey() is called once and its result will be cached.

We should only need to unlock the keyring once, and not expect that someone
would re-lock it. I've moved it to Init(). That doesn't have a practical effect,
but should remove the confusion.

+
   GError* error = nullptr;
   LibsecretAttributesBuilder attrs;
   attrs.Append("application", kApplicationName);