Personally I’d be worried there’s a transient disk issue. I’d ensure my backups are good and files aren’t being silently corrupted. I assume you’re on an NVME, they tend to fail instantly, but sometimes you’ll get transient file errors beforehand (like not being able to open a system library). Look at something like debsums to start with maybe.
I’m not having the issue anymore, I’m not sure what fixed it though as I tried multiple things yesterday.
Also, I’m not using an NVME, I’m actually just using an old laptop hard drive with one of those hard drive cases that basically converts it into an external hard drive.
That type of error is usually indicative of hdd issue. I only mentioned NVMEs because they tend to fail all at once, without recovery options. Spining disks usually fail slower (but not always). Take a peek at smart info, maybe run a scan. My guess is the cord got jostled though tbh
You could look at the package that's mentioned in the first line in Synaptic. The error message says it can't find a file. Fürst thing is do is check if that fike is actually there.
As others said, check if it is a single case or if it repeats at the next shutdowns. Anyway, the main question this brings to mind is: do you have a good backup of your system / data ?
I don’t have a backup of the system because if something happens, I’m switching distros. But I do have both an external hard drive and Pcloud for cloud storage for some other things like game save files.
Not sure how you searched but I assume you didn’t use or know apt? How do you install packages in the first place? Through GUI or Terminal?
EDIT: I assume you use the Linux Mint GUI package manager. I can’t find how to do this too, would need to search more detailed but I don’t have enough time for this now, need sleep, don’t have enough sleep.
I know about and have used apt, I install pretty much everything through the terminal. What I searched for was “how to reinstall libpcre” because I thought that it required a specific method or something due to the fact that it’s a system library.
Anyways, it reinstalled it but I wont know if it fixed the issue until tonight.
I have no idea what those are, unless Linux Mint (at least the XFCE edition) has one of those installed by default, I’m pretty sure I don’t have any of those installed.
Attempting to kill init means that something tried to kill PID 1. That’s… abnormal outside of a shutdown. But it can be normal during shutdown. So uhh… yeah: if it continues to be a problem then it needs to be reported and fixed by your distribution. What distribution are you using?
I see kernel panics at shutdown most often on Arch-based distros after updating system packages.
It sucks when it happens during shutdown but it’s typically not going to cause other problems… except perhaps not automatically booting if you wanted to reboot instead of shutdown.
A kernel update, if it’s done right, shouldn’t cause a panic. But not every distro does updates right.
If you know the old version and the new version then it might be useful to reach out to the Mint community and see if they’re aware of issues like that.
Yes this is a kernel panic which occurs when something goes terribly wrong inside the system. This could be anything from broken software to defective hardware. You should observe if this happens regurlarly.
I tried seaching it online but the only I could find (that I understood how to use it) was to run “sudo ldconfig” which didn’t seem to day anything. I have no idea if that actually fixed the problem or not but if it didn’t, do you have any other solutions?
It’s probably just paranoia but every laptop I’ve ever owned has had a problem pertaining to repeatedly turning them off and on again. This laptop is my mom’s and I’m just using it because my old one stopped working and I really don’t want to break this one too.
You’ll break things if you do more and more stuff suggested inside this thread without testing it. Maybe executing ldconfig was enough, but if you try more and more stuff you don’t know what you did. Linux is very hard to break, especially when you didn’t mess around with things like packages and libraries by yourself, there’s mostly a way back. But if you’re scared use the time and make a backup and a live USB stick with a Linux distro of your choice to rescue the system if something’s terribly messed up.
I’m not concerned about Linux breaking, I’m concerned about the laptop itself. My last laptop stopped being able to boot into any OS or even enter the bios after I was repeatedly restarting it one day and my laptop before that has a problem where for some reason the screen gets dark spots if it’s turned on more than once a day. I also have another laptop that has a failing GPU and another that for some reason can’t read internal hard drives anymore. In the off chance that Linux does have problems, I am already prepared for that but as I said, I’m more concerned about the laptop. We’ve had it for over 5 years and we really can’t afford a new one.
ldconfig sets up links and caches for loading library code. That might be an issue if your install is broken between updates. You can use ldd to check if code can be looked up. ldd /usr/lib/x86-64-linux-gnu/libpcre2-8.so.0 should show no errors. Likewise for ldd /usr/sbin/init.
Ok, so Synaptic Package Manager states that it’s installed in the exact location you say that it’s supposed to be in but ldd states “No such file or directory”. What’s going on here?
Add comment