nyan

And I think all programs should follow user theming, regardless of desktop environment, widget set, or anything else. ('Scuse me while I give GTK4 the stinkeye again.) You can never tell whether someone's colour selection is a matter of accessibility rather than just personal preference, so you absolutely should not ignore it. Defaults matter very little as long as you can change them.

It's really more nvidia's fault than Mint's—the nvidia proprietary drivers periodically drop support for a generation or three of cards, and nouveau doesn't work properly with some cards because nvidia has a history of not giving out needed information.

Why would it be awkward? Most non-technical people are so thrown by my white-text-on-black desktop theme that they can't even tell what software I'm using, and the few technical people around know that I have Opinions about software and aren't interested in talking about it. Keeping everything adequately compatible with the company-issued software is my problem.

How would I blacklist the nouveau driver?

Create a file in /etc/modprobe.d/ containing the text blacklist nouveau (worked for me on Gentoo and for a friend on Ubuntu) or add a kernel parameter module_blacklist=nouveau to your bootloader. However, if you don't have the correct proprietary driver, that won't help.

After 20 years of Gentoo, I don't see myself switching in the next five. Comfortable, capable, flexible.

I switched from KDE 3.5 (whenever that was current).

Terrifyingly, I think someone is still maintaining KDE 3.5 proper for OpenSUSE. Then there's TDE, which is widely available. (But you probably mean 15-20 years ago.)

Not the same distro, but on my system, the relevant file is located at /etc/default/grub. Find the line that says GRUB_CMDLINE_LINUX, uncomment it if necessary, and add your kernel parameter to it (mine has GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax", for historical reasons). Then run grub-mkconfig with appropriate arguments to regenerate your grub configuration.

Per the contents of my /usr/portage/distfiles, the original undivided package is ~500MB, making it the largest single package I've got on my system. Splitting it seems like a very good idea . . . but Gentoo generally prefers not to alter upstream tarballs, so I'm likely stuck.

If you're getting a grub command line, then it's finding the grub efi payload itself now, but can't locate the kernel (or possibly the initram or something that's supposed to be in it). Check your grub.cfg and try to confirm that it's looking for the correct partition on the correct drive.

One possibility is that it has a degenerate UEFI implementation that will only recognize the efi "payload" if it's in the fallback location—I had this problem with an older HP laptop. You can force grub-install to place the needed file in this location by passing the --removable switch (you may also need to pass --efi-directory=[dir]), or you can manually copy the file to EFI/BOOT/BOOTX64.efi on your EFI partition if it was already installed elsewhere.

If you dare, you can try temporarily killing the system's swap (using the swapoff command) and see what happens. With no swap, the standard OOM reaper should trigger within a couple of minutes at most if it's needed, and it should write an entry to the system log indicating which process it killed.

Note that the process killed is not necessarily the one causing the problem. I haven't had the OOM trigger on me in many years (I normally run without swap), but the last time it did, it killed my main browser instance (which was holding a large but not increasing amount of memory at the time) rather than the gcc instance that was causing the memory pressure.

Hmmm. Random guess: does your machine have another audio output, possibly via HDMI, that you're not using? This could be ALSA selecting the wrong device as a default, which would then propagate up through the stack.