66
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jan 2026
66 points (100.0% liked)
Linux
57274 readers
835 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 6 years ago
MODERATORS
Clear up some space first and then try something like this:
I've had issues like that before and oftentimes it's recoverable. A bit unfortunately if the wrong packages got damaged. Can be quite an effort to get it going again and it depends on the exact situation.
The first command worked, the second one is still showing up
http have died unexpectedly error 127Method http died unexpectedly 127means APT’s HTTP helper (usually curl/wget) was in a bad state when the disk filled. Chroot alone won’t fix it, run dpkg --configure -a first, and if http still fails, reinstall curl/apt-transport-https (manually via dpkg if needed), then apt --fix-broken install.You'll have to download them manually as other people have mentioned, and resolve any missing dependencies during install the same way. Also check your network still works.
That's the trick, local installation via
dpkgof the missing package itself (that you got another way) required to let apt get work.Hmm, sorry. I'd guess your internet connection doesn't work any more. So apt can't fetch the packages. That's kind of hard to debug, though. You'd somehow need to fix networking before you can proceed. But we don't really know what broke. And if that's really the only issue at play.
Maybe a Live-USB stick and a rescue mode can help here?! Other than that I'm out of options.
are you able to ping a website? try this command "ping google.com" without quotes