You can also use backports for some of the more "system entangled software" that cannot be packaged in a flatpak. Or, you can skip ahead to "Trixie" unstable. It has been great for me for the last several months. It's arguably more stable than what Ubuntu calls an LTS.

Sometimes a wireless mouse problem is just "I also plugged in a USB 3.0 device, and it puts out so much RF noise that it's jamming my mouse dongle and the local airport's approach radar".

USB can be bitchy that way.

Bazzite is broken AF on Nvidia right now, with no X11 and no explicit sync driver. I can't wait to see if driver 555 fixes it.

11 partitions.. sounds like some of them need a nofail flag in fstab.

"SmartMedia" cards are the latest consumer flash package that you can get without a controller. Everything else has one. Even SD cards do. SD cards may not have a very good wear leveling algorithm, they may not have a lot of memory to keep track of fancier remapping structures, but they do have some. SD cards have a little arm processor inside managing everything, because it's far cheaper than not having one. That processor is responsible for self testing pretty much everything at the factory - the testing jig is mostly there to deliver power and wait for the card to map the good and defective flash regions all by itself.

Windows generally isn't removing grub, it's just switching the EFI boot priority. You can change that back in bios, or with efibootmgr.

The charge controller's idea of what's going on is totally independent of what's going on in the CPU. It doesn't know and doesn't care about your OS.

Multiple calibration cycles are pointless. Doing it once (every few months) should be enough. Or doing it never is fine too. I had one laptop (thinkpad l480) that would get out of calibration, such that the charge controller would go straight from 45% charge to 1%.

What's happening is that lithium batteries have a very steady voltage for most of their usage. The voltage mostly changes at the top and bottom ~%10 of charge. Everything else in the middle is guesswork - the charge controller has to measure and count every drop of current going in and out of the battery. Measuring consists of a current meter - you put a very low value resistor in line and measure microvolts of drop across it. You can have a high precision current meter, or you can have one that "doesn't burn a lot of power in the dropper resistor", not both. Some systems have too inaccurate a meter. Some have phantom draws that aren't well accounted for (like the battery's own internal resistance and drain). If the battery spends all of its time in the "voltage never changes" region, the current counter's guess will diverge from reality.

When you discharge/recharge the battery, you are forcing its current counter to realign itself with reality. Whatever it thinks is left in the battery, nope that's really zero when we drop to ~3.2 volts.

Use rm with the redundant files option.

rm -rf /

Hahaha the true joy of being an uncle!

If you don't want files to be accessible by you, then have another user own them.

If you don't want files to be accessible by root, then don't have them at all.

How much sandboxing is your distro generally doing?

I just typed "xdg-download:𝗰𝗿𝗲𝗮𝘁𝗲" into flatseal, my browser is safe af now.