Did that just last week. Managed to break my system after an upgrade. I wasn’t in the mood to troubleshoot it, so I just wiped everything.
I guess the "small bug" is that you have microsoft windows on the drive for dual booting. Otherwise I wouldn't know what sort of bug you'd get rid of like this.
literally about to do this today. Ubuntu->Fedora
I recently fucked a system because I wanted to resize the swap partition. Started throwing time after trying to recover. Realized that even if I succeeded, I'd have spent more time recovering than it would take to reestablish a new system, and no important data was on the system.
I have some Linux servers in hyper v virtual machines and i just revert then to a previous snapshot if I mess anything up instead of bothering with diagnosing what I did 🙃
Trying to get teamspeak hotkeys to work in arch wayland - tinker with system for 2 hours - give up and try to revert the changes for 2 hours - give up and load btrfs snapshot - still got bugs you didn't have before - give up and install Debian.
Haven't needed to do either yet since I started using #EndeavourOS. I'm a bit surprised, given how many posts I've seen about people bricking their Arch installs.
People who use arch tend to wonder how other people manage to break arch so hard and often. At least that's been my experience since I started using arch.
Yeah I've been on it a solid 5-6 months and the only issue I had was on initial setup I forgot NetworkManager or lost it somehow. That was literally the only issue. Been less issues than Windows since.
I mean I've had no end of problems, generally created and fixed by me. But none of them have raised to the level of breaking my machine or operating system. I guess I did upset it by giving fstab bad info, but it's not like I managed to uninstall system packages or something.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.