On my system this bug appears to have been resolved since Chromium
updated to Version 53.0.2785.143. I note that when I boot up the
system, at the log-in screen that I get a dialogue box requesting the
wireless network password which has not occurred in the past so not sure
if something has also
I found that stopping the gnome-keyring process resulted in the PC
running normally again until the screen lock came on. This resulted in
been unable to unlock the screen again requiring dropping to a command
line via Ctrl + Alt + F1 to allow a reboot.
Therefore does Petar Bojovic's ugly fix
I have noticed the same behaviour - after boot and starting chrome the
gnome-keyring-daemon process takes about 50% of CPU for about 5mins.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
Have the same issue but have just converted my wav to an ogg and it
works OK (although I think that I have tried an ogg earlier.
Unfortunately after reading through the posts I also installed the
gstreamer plug in for canberra so not sure if that was also involved in
the fix.
For new users of
