Saya di Ubuntu 16.04.2 dan hari ini Google Chrome dan Chromium mulai membutuhkan waktu lama untuk memuat. Setelah dibuka, mereka sering membeku.
Saya memuat Chrome dari baris perintah dan mendapat pesan ini:
$ 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
Memuat kromium dari baris perintah mengembalikan ini:
$ 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
Saya sudah benar-benar menghapus chrome / chromium, menghapus folder masing-masing di .config dan .cache
Bagaimana saya bisa memperbaikinya?
16.04
google-chrome
chromium
Filipe Dias
sumber
sumber
Jawaban:
Selesaikan ini dengan membuat file ini
~/.config/autostart/gnome-keyring-daemon.desktop
dengan konten berikut:Lalu saya reboot dan Chrome / Chromium kembali normal ( sumber ).
Setelah mem-boot ulang, saya terus menerima pesan ini "keyring tidak dibuka saat masuk" dan harus mengetikkan kata sandi saya. Saya menyingkirkannya dengan mengikuti Bagaimana saya bisa berhenti diminta untuk membuka kunci 'default' saat boot?
sumber