The former is done by not setting google_default_client_id and google_default_client_secret during build. Reading the thread: it seems we need to:Įither build without the OAuth 2.0 client id and secret or to disable the Google signin integration. This is unwelcome, but not unexpected given that Google had already announced that this feature was going away for third-party API keys. If I click it, choose the option to sign in again, and complete the username / password / 2FA flow, then… nothing changes. The icon on the toolbar is stuck at “Sync paused”. This worked for me until a few weeks ago, and now it does not. AccountReconcilor::RegisterWithIdentityManager AccountReconcilor::RegisterWithContentSettings Loaded tokens: result = 2 number of tokens loaded = 0 Failed to decrypt token for service AccountId. InitializeSandbox() called with multiple threads in process gpu-process. InitializeVaDriver_Locked(): vaInitialize failed: unknown libva error Libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Password storage detected desktop environment: GNOME The only thing from os_crypt_ are those Decryption failed. Password decryption failed, encryption_result is 2 NetworkDelegate::NotifyBeforeURLRequest: Activated seccomp-bpf sandbox for process type: utility. ChromePasswordManagerClient: this: 0x351c7b1fa800
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |