ReillyBrogan So, I guess I need your expertise.
I have a question, two more reports on freezes I have encountered, and maybe an idea what caused them, at least the one I encountered today.
Spoiler: Might be related to keepass / mono.
The question:
it is my understanding that the command you mentioned earlier sudo journalctl -b0
gives you as output the logs from the last boot to now. Is that right? If so, how does this help to understand what caused the last freeze, which obviously happened before the last boot. What am I missing here?
The reports:
a) 5 days ago I had a freeze. I know for sure that I was playing music via Lollypop and had a youtube video playing via chrome browser on my TV as a second screen. I noticed the freeze when the video wasn't moving any more. music from lollypop continued playing. I could still move the mouse cursor, but nothing was responding any more. When switching to tty via alt+ctrl 1 or 2 or 3 or whatever, computer would switch back the frozen gnome session. This is the sudo journalctl -b0 output
b) today my system froze again while I was running keepass. The moment I was saving the database and then pressed alt+tab to switch to another window, the screen froze. Again, I could still move the mouse cursor, but nothing else was responding. I tried to switch to tty, but again I was returned back to the graphical session, to the lock screen. I don't know. Maybe because I was impatient and pressed all sort of ctrl+alt+number combination, one of which might have brought me back to the graphical session. I entered my password and was back in my frozen GNOME session. Again hitting all sort of ctrl+alt+number combination, and when I was back at the lockscreen, instead of entering my password, I chose to reboot.
While booting, I again experienced a delay of maybe a minute with a blinking underscore in top left corner of an elsewise blank screen like described here , but this time without the dracut-initqueue timeout. After the delay, the boot continued.
This is the sudo journalctl -b0 output
I then did run keepass again to do some stuff there, and closed it. By accident, I then noticed a very high cpu load. A processed called mono ate up to 47% of cpu, chrome was also running, my cpu load was by 100 %
A quick google search gave me this command ps ax | grep "mono"
with the following output:
7910 ? Sl 11:22 mono /usr/share/keepass/KeePass.exe
42319 pts/1 S+ 0:00 grep mono
After killing the process 7910, mono stopped consuming the 47% of cpu. Note that I had closed the keepass window earlier, while mono/keepass apparently continued running in background.
So I somehow think that this keepass/mono issue might have caused the last system freeze.
Some weeks ago I installed a german language package for keepass. Don't know if that's related or if there is a general keepass/mono issue. For now I have deleted the german language package and switched back to english.