Linux

48665 readers

519 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Fedora 41/KDE broke itself (lemmy.world)

submitted 2 days ago by some_random_nick@lemmy.world to c/linux@lemmy.ml

6 comments fedilink hide all child comments

While I was adding Golang to the PATH my terminal (Konsole) suddenly stopped recognizing basic commands like nano and ls. I restared my PC and after logging back in (X11) KDE started throwing errors because it wasn't able to find any program I tried to launch. Konsole is gone. I can't open any program whatsoever (Firefox, Discover etc.). Trying to log in into Wayland just throws a black screen. After a few more reatarts I decided to use the terminal from the login screen, but it is broken as well. ls not found, nano and vim don't exist. So far I can use pwd and cd.

What the hell is wrong here? Is it hardware failure (bad SSD)? Is there anything I can attempt to recover the system?

you are viewing a single comment's thread
view the rest of the comments

[–] yardy_sardley@lemmy.ca 4 points 2 days ago

It definitely could be a hardware failure, but if the system still boots fine, it's probably not that. Based on the symptoms, I think you might have clobbered your PATH variable. This can happen when you do something like PATH=/new/path/ because the variable gets overwritten. You have to remember to preserve the existing value with PATH=$PATH:/new/path/. Don't worry, this is reversible.

The best thing to do would be to fix or temporarily remove the commands you used to set PATH in whatever profile or .rc file it's in. You can run whatever text editor you have installed by specifying the path to the executable. I don't know exactly where vim is on Fedora, but it's probably something similar to /sbin/vim or /usr/bin/vim. Keep trying locations until you find the right one. Then log out and back in and it should be fixed.

You might also be able to login as root and use the shell normally to fix the problem, depending on which file contains the faulty command. Hopefully this helps.