I can confirm that the problem occur when two instances of gnome-
screensaver are launched by the system. For my part, the fact that 2
gnome-screensaver instances are launch at startup is unknown and appears
randomly.
using a console :
$ pstree -p | grep gnome-screen
|-gnome-screensav(XXXX)───{gnome-screensav}(YYYY)
|-gnome-screensav(ZZZZ)
$ kill -9 ZZZZ
then do ALT+F7 to come back to your X session.
As my system have only been upgraded Ubuntu release to another (for
several years), may be there are corrupted config files that launched
two instances of gnome-screensaver, that is at the origin of the
conflict and cpu outage ...
I think #181065 and #458501 are duplicated bugs of this one.
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for GNOME Keyring.
_______________________________________________
Mailing list: https://launchpad.net/~registry
Post to : [email protected]
Unsubscribe : https://launchpad.net/~registry
More help : https://help.launchpad.net/ListHelp
