Comment 20 for bug 1689825

Revision history for this message
ThomasRosenkranz (tom-rosary-q) wrote : Re: gnome-keyring not unlocked on boot

same for me here
by starting with the terminal

$google-chrome
[6136:6136:0528/125519.901742:ERROR:browser_main_loop.cc(279)] Gtk: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden,
[6136:6136:0528/125519.902002:ERROR:browser_main_loop.cc(279)] Gtk: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden,
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.
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.
[6136:6136:0528/125701.104195:ERROR:CONSOLE(0)] "Error in event handler for (unknown): TypeError: Cannot read property 'id' of undefined
    at inject_code (chrome-extension://mhcmfkkjmkcfgelgdpndepmimbmkbpfp/js/cs_inject.js:17:13)", source: https://www.google.de/_/chrome/newtab?espv=2&ie=UTF-8 (0)

after
$sudo apt install gnome-themes-standard

I got less error messages but still a long delay
$ 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.
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.

from post #17 I tried this
$ google-chrome --password-store=basic

And the browser started immediately :-D