There is Plasma Bigscreen that’s a modification for HTPCs. For touch screen based devices, a tiling WM is available for both Gnome and Plasma, though not baked in. IMHO bigger issue for both is a poorly working touch screen keyboard. This is something that SteamOS solves quite well.
There are basicly two ways to go with regressions: bisecting or research.
With bisecting you restore a working backup, and try to isolate the breaking change. In your case you could try updating one package at time and testing. Since these are often GPU related, start with kernel and mesa. When you find the breaking update, you can either report it on your distros issue tracker, or git bisect it further to the breaking change in the source code to increase the change of it getting fixed quick.
With research, you look into relevant bug reporting databases. These include your distros issue tracker, Valve’s issue trackers both for Steam and Proton, DXVK issue tracker, freedesktop.org and kernel issue trackers.
These are a lot of work, so most people just try random stuff. That’s why you often get suggestions to do so.
Sorry I don’t have an easy fix for you.
Regardsless what distro you end up with, do your research before bying new hardware. Any hardware, such as keyboard, usb bluetooth adapter or gaming audio headset might be unsupported or supported poorly, and require out-of-kernel drivers, firmware or propietary vendor software, that work only with some kernel versions or certain distros. There often are options that have great linux support and work with any distro, but you’ll need to find them.
Pick your prefered update interval between LTS, 6 month point release or rolling based on how much time you have for administration. If you need you PC also for work, a rolling distro might break just when you need it the most. After choosing the update interval, pick the distro with chosen update interval you like the most. Say you know and like Debian but need a rolling distro, then Debian unstable might be a good choice for you. You can also run multiple distros and dual-boot.
Special purpose distros such as gaming distros can be a good choice, but they often have less developer resources and tend to die then the few developers lose their interest.
Regardless of your choice of distro, spend some time to configure regular backups.
Two most common reason for Proton not working are:
Running games from NTFS or other incompatible file system.
Issues with GPU drivers.
Anyway, we are just guessing here without logs.
Set PROTON_LOG environment variable, eg. “PROTON_LOG=1 %command%” in launch options of Steam for the game. Log will show in your home dir. See Runtime config options part of the Proton README for more info.
https://github.com/ValveSoftware/Proton/blob/proton_10.0/README.md#runtime-config-options
Here’s my suggestion.
First, check your RAM with Memtest86+ or similiar tool. This is the first test because failing memory can and will corrupt your whole system, and it’s easy to test.
Second, if RAM is fine, check the logs. This is more effective then just guessing. Just copy-pasting possible errors to your favorite search engine usually points to the right direction. Archwiki has a nice tutorials about logs.
Third option is to test components one-by-one. Remove all unnecessary components, such as extra SSDs/HDDs, wifi cards, USB devices and PCIe cards. If it doesn’t help, test your CPU and GPU by running dedicated CPU and GPU benchmark tools. If you still get hangs, try with another PSU. If your components test fine, it’s likely a driver issue. See Arch wiki article on Nvidia troubleshooting for some tips about that.
Your last option is pure guessing. It’s the most time and money consuming way to debug with the smallest chance of success, but still many people prefer it. Most often issues like these are GPU issues, so it’s a good guess. However it’s still a guess.
I hope this helps.
Maybe try bleeding edge. See,
Acording to SteamDB, there has been no updates. I didn’t manually check all of the 355 depots though. I’d guess it’s either shader cache, corrupted game files, or a bug in Steam.
There is also Kaldi, but it’s not on F-Droid though.
Have you tried the fixes in the comments of this page?
https://aur.archlinux.org/packages/gzdoom
I find the comments in the AUR package page the best source of information to debug AUR issues.
Anyway, if you don’t want to use exactly that AUR package, there are multiple ways to install gzdoom witch some may be easier to install. You many different packages come up when you search gzdoom.
And what comes to other options, for Steam users there is luxtorpeda that integrates with Steam. Lutris users have their gzdoom runner. For the rest there is flatpak version available.
Another option is using libpurple compatible chat app, and using steam plugin for it. These haven’t had much developement effort lately, but worked last time I tried them.