73
I'm not sure what fixed it because I tried multiple things yesterday, but it shutdown normally last night.
this post was submitted on 15 Aug 2023
73 points (96.2% liked)
Linux
47993 readers
1194 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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?
ldconfigsets up links and caches for loading library code. That might be an issue if your install is broken between updates. You can uselddto check if code can be looked up.ldd /usr/lib/x86-64-linux-gnu/libpcre2-8.so.0should show no errors. Likewise forldd /usr/sbin/init.(Your paths may vary)
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?
You have a typo: It should be
x86_64, notx86-64Did 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.