You're viewing a single thread.
Basically, most of the points there fall into some of 3 categories:
- Your hardware is crap:
- WiFi not working;
- Nvidia failed;
- You ability to read/follow simple instructions is crap:
- WiFi not working;
- Messed up installation;
- Nvidia failed;
- No answer in the wiki;
- Lies/outdated:
- Updater broke system;
- Troubleshoot everything;
- No answer in the wiki;
This guy Arches
I use Arch and I lol'd.
Could that user possibly be an arch user?
I Arched for like 4 years or so, and now I NixOS. Got somewhat tired of modifying configs in 100500 places and eventually forgetting what exactly I've changed 😅
Nevertheless, I still think arch is great, and, as a side note, it does provide a good understanding of Linux on the upper-low level (not like LFS or even gentoo, but still very much viable).
About 3, idk what's going on with my system, but sometimes after a big yay update, the kde login fails (something about the plasma environment failing to boot or idk I have not debugged it correctly yet), then after a reboot systemd-boot fails to load it and the efi entry dissapears. I'm forced to arch-chroot and reinstall the bootctl. After doing so, sometimes I have to do it again and other times it logs correctly.
Again, not debugged it correctly but it's not like I did any kind of weird change to any config, just installed some flatpaks, some steam games, and lutris for League, which in the end is basically wine, and a yay update provoking this behaviour is pretty bad.
I've had this happen. I never did figure it out, personally. I distro hopped a bit and eventually ended up back on Arch and it didn't happen again, so I guess it was a bugged install?
Journalctl might be a great friend here.
Yeah, I've taken the routine of logging into tty3 before kde to pipe the journal tal output into a file to debug only the error if it happens. Yeah I know I can fine tune then output to get only the last execution and so on and I have done it, but it was not that clear and this happened after a work day and I wanted to fuck off and chill so the next time it happens I'll be more through.
Just Linux stuff xD
Yeah, I feel that man. Hopefully it doesn't happen again though.
I've personally encountered mentioned behavior with kde on both arch and kde neon, so I'm inclined to think it's their f-up. As for sd-boot, I'm not sure: I've used it on arch for a short while only, and then just ditched bootloaders altogether for efistub
Yeah, it's not that big of a deal for me, but damn if this would not be a deal breaker for a regular user, and I ensure you that a regular user would install league and steam or something of the sort xD
Like, I'm a software engineer and arch-chrooting once in a while to launch some commands is nbd, but a regular office worker that hardly runs some commands once in a while in terminals, copied from (safe) random places? Yeah good luck I bet they would just either distro hop or format and reinstall windows.
If I have to edit a config file, this means the OS is a failed piece of garbage
I could say inability to edit a config file is worth reevaluating of what is a failed piece of garbage here... But it won't be fair. If you don't want to deal with configs, go ahead and use chromeos or something :P
Jokes aside, pop-os is great ootb.
I've kind of come and gone full circle on this one. It fits in the same space as the terminal, way more useful when you know what you want.
Some config files are a lot easier to get the behavior I want, but editing a poorly formatted (or in some some cases pointlessly complicated) config is a quick nope out.
Too many options to learn a new language.