Damn, they giving out electromagnetic interference for free, how nice!

You could install linux-lts, I sometimes use that as a sanity check in case there is some kernel fuckery

Did you also update systemd at the same time? It might be worth reverting that update to see whether it’s that causing the issues.

To me, this sounds more like an fstab/systemd-automount issue rather than a bootloader/initrd issue

ArchWiki is your friend

broken features like FSR4 (it needs a DLL from the AMD drivers to work that this thing doesn’t provide)

I assume the LLM assume you are using either Proton-GE, Proton-EM or Proton-cachy, where this flag actually works 🤔

Why have a consistent Wayland experience when each application can run it’s own Electron version with varying degrees of enforced Wayland flags, and/or such an outdated Chromium version Wayland is just jank.

Edit:

Was trying to say that most of these CEF/Electron applications all need their own separate Wayland specific (Chromium) flags to have better Wayland support/integration. And the older Electron applications typically use an older Chromium as base, having even worse Wayland support… Was not trying to make this a “Wayland bad!” kind of post.

TL;DR: Electron applications have wildly varying level of Wayland support/integration, don’t have any Wayland issues other than specific CEF/Electron apps!