Yesterday, I spent half an hour trying to figure out why SDDM wasn't seeing /usr/share/wayland-sessions/sway.desktop before I realised that the reason it wasn't showing up in the menu was because I hadn't installed any fonts; so it was there, but it was invisible.
Once I spent several minutes trying to troubleshoot a network problem, turned out my ethernet cable wasn't properly plugged. The even dumber part is, I had checked the connection on the PC end, but had somehow neglected to do so on the router end.
I can totally relate to you. Everytime we touch the software and even the slightest bit changes, the pitchforks are ready. I even read the entire forum post and man it is awesome.
Thanks! It's really funny. Especially since KDE updated to version 6 and caused a lot of issues for other users - so it had to be the a software issue of course!
I'm still not entirely convinced, that it wasn't a software issue that caused the device to misbehave.
This actually happened to me not too long ago. Things would randomly just crash. Turns out it was because my RAM had bad sectors in it.
On linux I'd just restart whatever crashed and it usually went along fine for another 30 minutes. Worst that happened was btrfs would make my drive readonly until a reboot because it knew some shit was up.
On windows it bluescreened several times before corrupting the hard drive (was thankfully able to recover it lol)