I'd try apt-get --simulate autoremove first and see what it said it would remove (or apt --simulate autoremove). Then double-check it wasn't saying it would remove anything current.

Chris

https://gist.github.com/npcardoso/47d8f … wakeups-sh has backticks round grep '\*disabled' /proc/acpi/wakeup | cut -d ' ' -f1 and grep '\*enabled' /proc/acpi/wakeup | cut -d ' ' -f1. Those tell bash to run the command inside the backticks and assign the output from it to TOGGLE.

You could use $(...) instead, it's easier to read if you don't get muddled about what sort of brackets to use.

Chris

There are a number of text consoles, accessed by ctrl-alt-F1, ctrl-alt-F2, etc. ctrl-alt-F7 should take you back to the GUI if that's working (it might be some other combination such as ctrl-alt-F6 so it's worth testing before you need it in anger).

And did the logs show anything from the last time it happened? Although I've had systems lock up or suddenly reboot with nothing interesting in the logs before the messages from the system coming back up.

Chris

Try memtest86 (first single threaded, then multi). If that fails it's not the OS causing it.

Could you put the old CPU back in and see if that still works OK?

Try running watch sensors in another window and see if the system gets too hot under load. If you have another system log on to the faulty one (eg by ssh) and run it. That way you could still see the last screenful of output.

Try other stress tests. If it's stable under CPU load but not graphically intensive ones that might point to the error.

But it's odd the OS needs to be re-installed after a few crashes. What are the symptoms in that state?

Chris

Please post the segfault log entries here (and a few each side of the segfaults).

Chris

The command you were given contains an odd number of quotes. Try

pgrep -a expressvpn && echo 'It is running' || echo 'Not running'

Chris

To save typing I'll assume the user account is called fred. Replace it below if that's not true.

The first thing to try is ctrl-alt-F1 to get to a text console, then try logging on as fred. If it fails you may get interesting messages.

If that fails use ctrl-alt-F7 (or ctrl-alt-F6) to get back to the normal GUI, log on as root, open a console and enter su fred. If that works the account should be OK, but the password may not be what you think it should be.

To fix the password enter passwd fred. This should ask you for a new password for fred. Then try logging on as fred.

If that fails post output from grep fred /etc/passwd here.

If all else fails set up another user account from scratch.

Chris

Does a directory called /var/db exist? If not try sudo mkdir /var/db

NB: I'm only guessing since I don't use DHCP. But the "can't create /var/db/dhclient.leases: No such file or directory" message looks suspicious.

Chris

The release notes should be the first place to look if you do have problems. Or want to know the distro in depth.

And please allow for the fact that it's impossible to test a distro with *every* combination of hardware etc that any user could have.

Also remember that the people who built it are doing it in their own free time. Ask yourself how you would feel if you were the one being asked about something you built in your own time. Politeness will be more likely to get you helped. As will providing details of what you are doing and think is wrong.

Chris

It sounds like it would be a good idea to disconnect from the Internet before starting Firefox for the first time. So you could configure it to disable telemetry etc without giving it a chance to phone home first.

But it's a bad sign if you need to do that. Ideally it should be shipped with telemetry etc disabled by default.

Chris

Try ls -l /dev/nvidia* (the file names just start /dev/nvidia so the * is important). And ls -l to see what permissions they have is useful.

I get:

chris@rigel:~/bin$ ls -l /dev/nvidia*
crw-rw-rw-+ 1 root root 195,   0 Aug 25  2019 /dev/nvidia0
crw-rw-rw-+ 1 root root 195, 255 Aug 25  2019 /dev/nvidiactl
crw-rw-rw-+ 1 root root 195, 254 Aug 25  2019 /dev/nvidia-modeset
crw-rw-rw-+ 1 root root 248,   0 Aug 27  2019 /dev/nvidia-uvm
crw-rw-rw-+ 1 root root 248,   1 Aug 27  2019 /dev/nvidia-uvm-tools

Chris

My approach is to put entries in /etc/hosts for local hardware. See the man page for hosts for details of how to format entries. This is quite manageable if you only have a few systems which all have fixed IP addresses (eg 1 router and  1 printer). And then use DNS for everything on the internet.

Chris