You were just lucky. For some of us ut was just about having the wrong hardware at the wrong time.
Not complaining, I knew the risks going in and still love my distro, but arch updates totally can brick a PC with no PEBCAK involved. It does happen. :3
Fwiw, about the zéro expérience thing, I hope you know that plenty of women would enjoy helping their partner explore how to share pleasure and day to day intimacy with them. Being inexperienced and realistic about it also means you won't have that overconfidence that leads some men to disregard their partner's personal likes, needs and body quirks, and that can be a very reassuring premise.
Until you're one of the unlucky ones whose PC gets bricked by an update. Happened to me twice. I agree, it's wayyyy more chill than people give it credit for, but let's not pretend using it as a daily driver doesn't come with its risks ^^
There will be lots that will make you feel lost, because of the design language differences and the widely different philosophy, but you got this. Just take it at your own pace, one web search at a time and you'll be grand!
It is, yeah. Especially if it's to change it after 2 short years of use because if you keep it longer than that you look like a bum or whatever. I will never understand that tbh.
Depends. That's about what I paid for my previous phone second hand and it lasted me 7 years and I loved it to bits. But I was pretty broke and only could afford that. New phone, I decided to buy a brand new fairphone, because i think that the moment I get enough disposable income, I have a moral responsibility to use it in ways that encourage more ethical practices, for all the people who can't. Doing that is bloody expensive, but if it somehow helps make this dystopian hellscape a little more bearable, I'll invest.
You might not want to trust chatgpt with anything where accuracy and specificity are both essential to not brick a machine or lose data though. Especially since you can't check the sources it used. It did a decent job at getting the general workflow right, but even that's not a given. :/
Foxit still provides a free version that's linux compatible. Its been a lifesaver at work to do document signing without messing everything up. It may take a little tweaking to run, but it's worth a try for forms.
You could switch all your repos to the core Arch ones. I did that by accident once, and it was fine (although, I did switch them back eventually). Maybe it’d add release stability? I’m not really clear how the EOS repos vary off the baseline, except by adding some custom packages.
They don't afaik. EOS uses Arch's repos directly, unlike Manjaro. Just adds its own on top for all the fancy EOS stuff. Which is why EOS was immediately affected by the grub meltdown and not Manjaro. (which kinda digs a few holes in the stability hypothesis, though Manjaro is another kettle of fish tbf)
Snapper sounds really interesting, and I didn't expect "super easy" to be the feedback there. Sounds a bit overkill for my use case at home but I might look into it for work. Thanks for the info!
Oh god a borked BIOS is my nightmare... I don't even know how you'd go about fixing that on a modern PC mobo... Let's not jinx it shall we?
Ah no no, maybe I was unclear, but the issue occurs during the initramfs stage, long before any of my KDE/Plasma nonsense had any chance to run! KMS has nothing to do with KDE. ^^
Mostly using eos-update by clicking on the notification, unless I'm on a terminal where I still have the yay reflex from arch. I should remember to use eos-update though, I do appreciate the extra housekeeping.
Nop, I avoid nvidia as much as I can as well, I already can't avoid it at work, too much driver drama. Ryzen and radeon it is, with (almost) no fuss.
Also mostly using wayland, it works well even on KDE, but got Xorg around just in case, and I've had the occasional issue on both. That being said, it's plymouth that blows up, long before the graphical session is opened, so that shouldn't have an influence either.
Maybe I'm just a black cat, and/or maybe it just comes with the territory when you stay long enough on a bleeding-edge-use-at-your-own-risk kinda distro and update almost every day. Something's bound to go wrong eventually. Which, has also "been Arch with an easier install" for me, tbf.
Gonna investigate a bit more today, couldn't be asked yesterday. But if you're curious I can keep you updated when I find a fix. :)
Edit: Found the solution by essentially doing the same thing the folks on reddit did with nvidia by enabling early KMS start, and learning quite a bit along the way. Apparently it's now required by Plymouth and my system didn't get the memo? Or something? Eh it works.
That's anecdotal evidence but good for you!