If it’s just the dirty flag (it was uncleanly unmounted) you can try

ntfsfix -d /dev/sdc1

Still probably better to boot into Windows and let it deal with it (ntfs tools are still reverse engineered stuff after all), and check journalctl before doing it, but it works in a pinch.

I had a quick go at it yesterday (the latest 535 broke DDC CI for one of my monitors, making plasma-powerdevil unable to start) and for whatever reason KWin ran at something like 3 seconds per frame. No that’s not a typo, I mean it. I hope it’s fixed before it gets to Arch’s repo.

EDIT: It works! I had to switch to the DKMS driver (the main one isn’t in the repos yet) but other than that my Wayland session didn’t die a horrible death. Well smooth. I still didn’t test much, but at least night light works.

Yeah, as usual the opinionated crew are making something that one may even like feel like it’s forced down everyone’s throat (see: systemd, snap…) and making everything worse. I don’t see how any Linux desktop distro worth its salt can get by ignoring 90% of the PC GPU market share and essentially forcing them into an inferior desktop experience for pure ideology’s sake, and I LIKE Wayland. I even put up with all its quirks in a particularly quirky implementation (KWin). But this ain’t it if you want users to use your OS.

It’s because it’s bleeding edge, extremely well documented and extremely popular. Bleeding edge is exciting and you’re gonna end up on the arch wiki anyway regardless of distro, so you may as well go to the source.

Do mind though it doesn’t mean it’s easy, like at all, and I fundamentally agree, there’s a million better choices for first timers.