From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I'm not sure what fixed it because I tried multiple things yesterday, but it shutdown normally last night.
I'd reinstall libpcre, looks like it's gotten broken?
The kernel panic should be a direct result of shutdown (which I guess at this point is init/pid1) not finding its dependency and killing itself.
How would I reinstall it? I tried to look it up but I couldn't find anything.
sudo apt-get install --reinstall
https://duckduckgo.com/?q=apt+reinstall+package&t=fpas&ia=qa&iax=qa
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.
Sometimes we think a little bit too complicated
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.
Ok but is there anything notable from this error message, like anything specific that I should be checking out for?
First line of your picture is a hint for a software issue. I would just google that.
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?
Did it help though? Same error or is the system shutting down fine now?
I wont know until tonight.
What prevents you from shutting it down right now?!
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.
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.
I might be totally wrong, but libpcre sounds like the regex library used by perl. Maybe his perl packages are broken?
Almost. It's a C library that mimics Perl's regular expression facilities. Fairly common dependency for any number of packages.
Apt says it's installed. Someone said something about reinstalling it but I couldn't find anything online about reinstalling.
Your libpcre seems broken. Reinstall the package that contains this file.
I did that yesterday and it might have fixed it because I didn't have the issue but I did try multiple things yesterday, so I'm not sure.
Could also be an SEU
That's pretty specific, but I guess it's possible.
Iirc it's 1 bit per 500mb per week for your every day ram.
There's this famous case where a speedrunner playing Mario had such a bit flip and affected his play time.
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.
You seem to have removed libpcre2 library. Try to reinstall it using your package manager.
Synaptic Package Manager states that there are several versions of libpcre2 installed, which one should I try to reinstall?
In addition to the other things mentioned, check the health of your drive. This could be a symptom of corruption.
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.
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.
I see kernel panics at shutdown most often on Arch-based distros after updating system packages.
When I tried Arch, upgrading kernel would delete the kernel modules of the running kernel
somewhat unimpressive upgrade process.