Chrome和Chromium需要很长时间才能加载


20

我使用的是Ubuntu 16.04.2,今天,Google Chrome和Chromium开始加载需要很长时间。打开后,它们经常冻结。

我从命令行加载了Chrome,并收到了以下消息:

$ 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

从命令行加载铬会返回以下内容:

$ 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

我已经完全删除了chrome / chromium,删除了.config和.cache中各自的文件夹

我怎样才能解决这个问题?


2
我为此问题发布了以下错误。请添加任何相关信息和/或将其标记为也会影响您:bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825
Mike Rushton

Answers:


10

通过创建~/.config/autostart/gnome-keyring-daemon.desktop具有以下内容的文件来解决此问题:

[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

然后,我重新启动,Chrome / Chromium恢复到正常()。

重新启动后,我不断收到此消息“登录时未解锁密钥”,必须输入密码。我遵循以下说明摆脱了它:如何停止提示我在引导时解锁“默认”钥匙圈?


这是否给您一些“登录时未解锁密钥”消息,并提示输入用户密码?
MrMesees'5

1
是。:我被以下说明摆脱它askubuntu.com/questions/867/...
菲利普·迪亚斯

1
清除密钥环密码既不是可接受的解决方案,也不是解决方法
Laurent

2
其实这个答案有助于解决这个问题干净利落
安瓦尔

启动gnome-keyring-daemon来解决我在Debian Jessie的TigerVNC上更糟糕的症状:1:Chrome根本无法启动,即使据称在libsecret和“ GNOME keyring”超时后又恢复为“基本(未加密)存储进行密码存储” ”,每个--enable-logging = stderr。
Martin Dorey
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.