The Cookie Machine - Click here to drag window

DUMMY TEXT - Real text set in assets/js/theCookieMachine.js

Views: 1,820β€…    Votes:  2β€…
Tags: google-chrome   19.04   freeze  
Link: πŸ” See Original Answer on Ask Ubuntu πŸ”—

URL: https://askubuntu.com/q/1191155
Title: Random freezes on 19.04, unsure which logs to check
ID: /2019/11/23/Random-freezes-on-19.04_-unsure-which-logs-to-check
Created: November 23, 2019
Upload: November 24, 2022    Layout:  post
TOC: false    Navigation:  false    Copy to clipboard:  false


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[1]: 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[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition
Nov 11 23:13:37 alien systemd[1]: dev-disk-by\x2duuid-b4512bc6\x2d0ec8\x2d4b17\x2d9edd\x2d8
Nov 11 23:13:37 alien systemd[1]: 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[1]: 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:

The solution is to use:

It seems that my system had the old config in the place, resulting in
a conflict between two services: resolvconf and systemd-resolved.

The symlink /etc/resolv.conf pointed to
../run/resolvconf/resolv.conf

Changing it to point to /run/systemd/resolve/resolv.conf which is
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:

⇧ Since 19.10 update, mouse movement wakes computer from sleep Does rsync requires changing UUID after copying a partition?  β‡©