On 27/03/2025 03:26, George at Clug wrote:
I tried "$ journalctl | grep -i error"
First of all, likely it should be "#", not "$" (run it as root: either
sudo or su). Next
journalctl --priority=err
or
journalctl --priority=warning
instead of grep.
However in the case of obscure issues I would recommend against any
filtering besides time. After system freeze and reboot skim through all
last messages from previous boot. There is a chance that the action
caused hang left some traces
journalctl -b -1
Time window of the following command may be too narrow, but in some
cases it is more convenient
journalctl -b -1 -e
You can adjust boot ID to get access to earlier failures.
And for xorg /var/log/Xorg.0.log ?
/var/log/Xorg.0.log.old
but avoid graphical login before you copy it. Likely /var/log/Xorg.0.log
is created by current LightDM session.