Try assigning it an IPv4 address manually to get ethernet working. Eg ifconfig eth0 addr 192.168.1.64/24 as root. Replace eth0 with whatever the link is called. And use an address nothing else you have is using.

That would only be a temporary fix, but would enable you to download fixes onto it.

Or post output from /sbin/ifconfig here to give us a bit more to go by.

What make and model of system is it? CPU, motherboard, manufacturer, etc? Are you booting from a USB drive or a DVD? In either case what model?
Do any messages come out during the boot process?
If you have more than one system does it respond to pings from another system? If so can you log on to it over the network?
Exactly what message came out about the "live-boot" package when booting the minimal install? Can you take a photo of the screen and post it somewhere?

Chris

The problem here is that microsoft is an effective monopoly. Capitalism works well if you have a choice of product to buy, eg cars. But most people have to buy the OS with most software written for it, and most software is written for the OS with most users. So just because microsoft got there first they won control of the desktop. Ditto Intel nearly control the hardware market, though AMD do provide some competition.

WSL is intended to help them keep control by allowing people who need software only available on Linux to stay on windoze.

Nothing but US government intervention could break microsoft's monopoly (eg by requiring that the source code for any OS be made publicly available). And don't hold your breath waiting for that to happen.

It's a similar story with facebook (most people use it because most of their friends use it). And google etc.

Chris

Also check if the filesystem it is in is mounted read-only, Eg mount | grep /mnt/sd8

If all else fails copy everything you want to keep from that filesystem to somewhere safe, then re-format it.

Chris

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