*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
To get all of it:
journalctl -b0 > journal.txt
Or to just watch for the latest messages:
journalctl -f
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
Daniel, how does one produce the shell journal log? I'm afraid the
problem resurfaced even after I removed all the extensions.
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
Agreed, on both :)
I'll submit a suggestion there.
Thank you Daniel
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
I guess you could make that argument for all programs -- why don't they
monitor themselves for bugs, or at least for high CPU. The argument is
stronger for something like gnome-shell that allows 3rd party
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
This seems to have been the case. So far so good. If it changes I'll
act accordingly.
How about gnome-shell issuing an alert to the user that something nasty
is happening in the background without them
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
Thanks for the bug report.
The attachment 'ShellJournal.txt' seems to show this is a duplicate of
bug 1880405. But also, we find most high CPU issues are caused by
unsupported gnome-shell extensions and
