ipacialsection

I personally don't use Arch, but I think the reason so many people find it stable in practice is because they know their system well. When something breaks or needs to be changed, they know which configuration file to edit, which package to {un,re,}install, what to look for in the AUR, etc., and they can usually avoid those things in the first place, because they went through a fairly hands-on install process, not to mention having the best Linux wiki in existence at their disposal.

On top of that, I think a lot of derivatives of Debian, including Ubuntu and all its derivatives, severely undermine their stability by providing custom configurations for or changes to software that are rarely documented and completely transparent to the user... until they break and leave no indication of how to fix them. Which is one reason why I ended up using base Debian.

For me, the outdated packages in stable have actually gotten better over time, as DEs get closer to a place where I don't need any major updates to enjoy using them, Flatpaks become more readily available, and on a subjective level, I get less and less invested in current Linux news. Before Debian became my "forever distro", I'd hopped to it a few times, and often found myself wishing for a newer piece of software that wasn't in backports or flathub, or simply being bored with how stable it is, but that's been happening less and less. And I feel like Debian 12 in particular left me with software that I wouldn't mind being stuck with for two years.

I've gotten warnings to upgrade my browser with Debian's Firefox ESR, but they never affected a website's usability in a way that a newer version would fix, and they do provide security updates and new ESR series when they come out; even if you must have the newest Firefox, you can use the Flatpak.

Additionally, I'm currently on testing in order to get better support for my GPU, and each time I've tried to use it, it's worked for me for a longer time than the last as I get better at resolving or avoiding broken packages. If you do experience issues like the one you described, and can replicate them, and no one else has already reported them, you should report them to Debian's bug tracker. The whole point of Testing is to find and squash all the critical bugs before the next stable releases.

I'm pretty sure it's supposed to be a mix between Starfleet and Vau N'Akat dress.

how do I install programs from outside the "discover store"? I can get the Plex app through the built in app store, but the Plex media server app isn't on there so I have to download it from the website, which gives me a .rpm file.

Installing from Discover (or to be more precise, your distribution's software repositories, for which Discover is a frontend) is usually best practice. Programs you find online are less likely to work on your distro (especially something as technologically unusual as Bazzite). That said, from what I could find online the command to install an RPM file on that distro is sudo rpm-ostree install <path/to/package.rpm>. I have never used boxbuddy or any kind of distro container, but I imagine it would as simple as opening the terminal for one of your distros and entering the appropriate command for that distro to install your package.

Also, outside of the built in discover store, what's the best way to install programs?

Generally, Flatpak packages are safe to install, and any Flatpak repos you enable will show up in Discover. Flathub contains the majority of Flatpak packages in existence, though it might be enabled by default on Bazzite.

What are some cool programs in general to check out? My main use case is gaming, I don't program or do any work on my PC but I'd like to explore just for the sake of exploring!

Just look around in Discover and you'll find lots of gems. As a retro gamer, I've found RetroArch indispensable, as a frontend for all my emulators and then some. Lutris is nice if you want all of your games to be centralized under one launcher. There are lots of fun time-wasting open-source games too.

Also, what's a good way to familiarize myself with using the terminal? I've used the terminal on Windows quite a bit in the past, but only for basic things like unlocking a bootloader on Android and sending a ROM to it, back when I cared enough to root my phones. How would I, for example, pull a program off of github and compile it myself if needed? There's a program on github called gHub GUI by ysph that I'd like to check out, would be nice to be able to configure my mouse since piper doesn't seem to recognize my mouse.

You can just ease into it, or read any number of Linux courses online. Following tutorials on Linux will be as easy as following tutorials on Windows. You can learn about programs with either man <command>, info <command>, or <command> --help.

Most projects include README files instructing you on how to compile and/or install them; the exact process depends on the program. But generally, if you see files named "configure" and "Makefile", the process is to install dependencies, then cd into the source code folder and run ./configure; make; sudo make install.

What are some general best practices that differ from Windows? I don't really know how to narrow this question down, apologies for it being so vague.

Discover should be the first place you go to install programs. Don't install programs from random websites unless you absolutely have to. They probably won't work.

A lot of the programs you are used to from Windows will not be available for Linux. They might be compatible with Wine or Proton, but try to find alternatives to them before you try that. There is a KDE app and a GNOME app for most of the basic uses, and https://alternativeto.net/ is a decent resource for finding Linux-friendly alternatives to just about anything.

You probably don't need an antivirus - there are viruses for Linux, but they are extremely rare, and the anti-malware programs that are available for Linux will only detect and remove Windows viruses.

Don't have any comments on your other issues, because I don't have experience with the software you're using (I rarely if ever buy "gaming" hardware).

Damn Small Linux is a recently resurrected distro made specifically to run on old 32-bit PCs. You probably won't be doing much web browsing or gaming on this device, but you should at least be able to get it to function

Debian! It's stable, elegant, and doesn't impede customization. I distro-hopped a lot over the years - some that I ended up disliking included KaOS (severely limited software repository), Clear Linux (only way to get ffmpeg was to compile it from source) and Fedora (very slow); most I liked, and just decided to move on at some point. But I kept coming back to Debian, and eventually got to a point where instead of trying a different distro when Debian broke, I would just reinstall Debian.

I'd be interested to try VanillaOS or another "immutable" distro at some point in the future. See if they've matured enough for my day-to-day use.

First, go to [three dots] -> Preferences -> Runners -> Proton, click the button next to the newest available version of Proton GE (currently ge-proton-9-7), and wait for it to download.

Then, go to your bottle -> Settings -> Runner, set the runner to ge-proton-[version], and wait for Bottles to configure the new runner.

Have you tried using different runners? According to ProtonDB Ape Out is completely supported by Proton, so maybe try a Proton runner instead of Wine.

Now I'm (tentatively) excited to see how they'll outdo a season with a novel gimmick in each and every episode, including a musical and a crossover with a parody show, in terms of gimmicky weirdness.

Could you describe the issue in more detail, then? What happens when you try to play a video? If you get any error messages, please copy them.

It might not be Wayland-related at all.

I just tried installing Parole on my own KDE Plasma+Wayland system and it just works, aside from opening an external playback window, which feels a bit weird, but I'm assuming it's normal. The only display drivers available are X, but the "Automatic" pick works.

If it doesn't work for you, make sure xwayland is installed.

My second distro was Debian 8, initially with LXDE (which has barely changed at all since then, so it's still nostalgic) then later switching to KDE Plasma 4. I probably hold the most nostalgia for it, even more than I do for my first distro (Linux Mint 17). For a while I was into Plasma Netbook, which I find to be an especially weird, nostalgic product of its time, and the Oxygen theme in general is probably my favorite default look for any DE.