potkulautapaprika

I need to know what happens next, I’m hooked.

https://wiki.archlinux.org/title/general_recommendations

Take your pick.

“Note: In the installation image, systemd-networkd, systemd-resolved, iwd and ModemManager are preconfigured and enabled by default. That will not be the case for the installed system.”

https://wiki.archlinux.org/title/Installation_guide#Connect_to_the_internet

So you probably didn’t set anything up. Arch-chroot in to fix, or use a cable or phone tether to fix it from the new install.

Idk how to set up it with systemd suite, but for network manager it’s pretty much

# pacman -S networkmanager
# systemctl enable --now NetworkManager.service 

For 1, grub is fine, but systemd-boot is simpler, so I’d say that as ‘use grub if you actually need it’

For 2, has this actually ever happened to anyone in uefi times? Mbr overwrite was the good old times, now we have something at least better

If we define stable as unchanging for release cycle, yes. Just really hard to come up with equivalence with these two otherwise.

Sir, either you troll, or have the wrong idea why the distros mentioned are different things with different goals.

In case it was intended seriously, I’ll probably descend into madness because of the ubu lts = centos stream assessment.

Ahahaha, still great. My favourite flavor of init wars after seeing ppl digging up that horse’s dead corpse for a beating to re-enact the same old discussion over and over. Keep em coming op!

Quick, someone make a yt video that explains even less with more confusion and a word from our sponsors!

Occasionally I get this on wake from suspend, doesn’t matter if amd or nvidia system.

I just think of it as an annoying kde bug. It’s harmless though.

You either reboot or just switch to another tty and unlock the session.

But the others are right, you increase chances of this happening if you updated the kde stack and didn’t reboot/relog.