Daniel,
after further extensive testing and trialling. I can confirm that the high CPU
problem does not occur when I disable all GNOME extensions.
When no gnome-extensions were enabled the problem did not occur.
However, I was able to make the high CPU problem appear by running the
dock
*** This bug is a duplicate of bug 1849142 ***
https://bugs.launchpad.net/bugs/1849142
Daniel,
I disabeld the extensions and confirmed that the directory mentioned above is
not present.
I am still experiencing the following.
After being away from my machine, I come back to find the screen
*** This bug is a duplicate of bug 1849142 ***
https://bugs.launchpad.net/bugs/1849142
Daniel - I had the issue happen a couple of times tonight. While the UI
was unresponsive, I was able to use another machine to SSH to the PC and
run the journalctl command you recommended.
The attached
*** This bug is a duplicate of bug 1849142 ***
https://bugs.launchpad.net/bugs/1849142
Daniel - I tried the work around recommended for bug 1849142 however
that didn't fix the problem and the issue still persists.
I therefore believe that the issue is a separate one.
Are you able to provide
Public bug reported:
I have configured my PC to lock the screen automatically after a period
of inactivity. Often when I come back to my PC I'm unable to login due
to gnome shell running at 100% CPU (according to htop).
The only way I can log in is to SSH to the machine from another PC and
kill
5 matches
Mail list logo
