O Chrome e o Chromium demoram muito tempo a carregar

Question

Estou no Ubuntu 16.04.2 e hoje o Google Chrome e o Chromium começaram a demorar muito tempo para carregar. Depois de abertas, elas congelam com frequência.

Carreguei o Chrome a partir da linha de comando e recebi esta mensagem:

$ google-chrome
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[8032:8100:0504/165233.258127:ERROR:connection.cc(1954)] Cookie sqlite error 5, errno 0: database is locked, sql: DELETE FROM cookies WHERE persistent != 1
[8032:8070:0504/165235.449471:ERROR:leveldb_database.cc(311)] Failed to open LevelDB database from /home/fd/.config/google-chrome/Default/IndexedDB/https_www.google.pt_0.indexeddb.leveldb,IO error: /home/fd/.config/google-chrome/Default/IndexedDB/https_www.google.pt_0.indexeddb.leveldb/LOCK: No further details. (ChromeMethodBFE: 15::LockFile::1)
[8032:8070:0504/165235.450323:ERROR:indexed_db_backing_store.cc(1403)] Unable to open backing store, not trying to recover - IO error: /home/fd/.config/google-chrome/Default/IndexedDB/https_www.google.pt_0.indexeddb.leveldb/LOCK: No further details. (ChromeMethodBFE: 15::LockFile::1)
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[8032:8074:0504/165337.922687:ERROR:connection.cc(1954)] Cookie sqlite error 5, errno 0: database is locked, sql: COMMIT

O carregamento do cromo na linha de comando retorna isso:

$ chromium-browser
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Killed

Eu já removi completamente o chrome / chromium, excluí suas respectivas pastas em .config e .cache

Como posso corrigir isso?

    

Answer 1

Resolvido isso criando este arquivo ~/.config/autostart/gnome-keyring-daemon.desktop com o seguinte conteúdo:

[Desktop Entry]
Type=Application
Exec=/usr/bin/gnome-keyring-daemon
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_US]=Gnome Keyring Daemon
Name=Gnome Keyring Daemon
Comment[en_US]=Load gnome keyring daemon
Comment=Load gnome keyring daemon

Depois, reiniciei e o Chrome / Chromium voltou ao normal ( fonte ).

Após a reinicialização, continuei recebendo esta mensagem "o chaveiro não foi desbloqueado durante a conexão" e tive que digitar minha senha. Eu me livrei dele seguindo Como posso deixar de ser solicitado a desbloquear o chaveiro "padrão" na inicialização?