🔍 See Original Answer on Ask Ubuntu ⧉ 🔗
Random freezes on 19.04, unsure which logs to check
November 23, 2019
September 20, 2023
Copy to clipboard: false
/assets/js/search.js will update text..
Enable systemd multi-boot message logs
The best solution is to enable multi-boot message logging and then displaying the last messages of the previous boot:
$ journalctl -xe -b-1 Nov 11 23:12:07 alien systemd: Reached target Shutdown. -- Subject: Unit shutdown.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit shutdown.target has finished starting up. -- -- The start-up result is done. Nov 11 23:12:07 alien systemd: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition Nov 11 23:13:37 alien systemd: dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d8 Nov 11 23:13:37 alien systemd: Deactivated swap /dev/disk/by-uuid/b4512bc6-0ec8-4b17-9ed -- Subject: Unit dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d88db0f031332.swap -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d88db0f031332.swap has finis Nov 11 23:13:37 alien systemd: dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d8
In your case the messages won’t show a normal shutdown but rather the last recorded messages just before the system crashed.
Analyzing the messages you found so far
The first error message is addressed here:
- New alert keeps showing up: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001
The solution is to use:
It seems that my system had the old config in the place, resulting in
a conflict between two services:
/etc/resolv.conf pointed to
Changing it to point to
managed by systemd, fixed it for me.
The second error message is generated by nvidia:
The answers posted are only helpful for the software developer, not the end user. For end users running chrome other solutions exist: