I had that symptom, and I found that my laptop was using S2 idle (suspend to idle). I fixed it by switching to S3 sleep (suspend to RAM). I suggest following the instructions in section 3 in this page: https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate
Like many Arch Wiki guides, most of the information on that page is applicable to most Linux distros, not just Arch.
Question, changing the OS on the deck, do you still get all the updates to steam and everything?
Yes, I think so. I haven't used SteamOS, but it seems like it gives you Steam, and exactly the right drivers for the Steam Deck? Steam is packaged for basically every distro, and you get the same experience everywhere, including "big picture mode" if you opt into that. Bazzite is designed with the Steam Deck in mind so it should have the right drivers.
Distrobox uses either podman or docker to manage containers - you can find details on where data is stored by looking into those directly.
The distrobox docs have info on how to move containers from one system to another. It's not the same as sharing between two installs, but it might help. https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#container-save-and-restore
I really liked the options to cycle through previous prompts in history, and to view output of the last command with at option to search in that output. But then I realized that lots of terminal emulators can do that, and I just needed to learn the hotkeys.
I'm wondering if Wayland support in Wine will encourage Valve to support Wayland in the Steam app too.
On my desktop I run a Wayland window manager that doesn't implement XWayland so I can't run Steam directly. So I've been running it in Gamescope in big picture mode - which is actually exactly what the Steam Deck does.
Impressive! I struggle to get as far as a phylum or even kingdom identification in the moment something smacks my safety glasses. But looking at a picture of a palo verde beetle I can see how that would be unambiguous.
Weirdly synthehol is much harder on the liver compared to alcohol.
I assume because the writers thought it was hilarious
I was reading this thread thinking, "this isn't the time to recommend NixOS that's not what OP asked about." But if you're using Ansible this way NixOS might be a good fit for you. It's got the advantages of the other immutable distros with the added feature of managing everything through a declarative configuration.
Not necessarily - real gene therapies that are in use now are carefully designed so that modifications are not inherited. For example, Casgevy which targets blood stem cells to treat sickle cell anemia. Because the treatment is limited to specific types of cells modifications don't get into the germ line.
This is a good thread to have today. This is some encouraging news!
Docker Compose runs services, manages dependencies between services, isolates each service in a container, manages a private network. Out-of-the-box flakes don't do any of that - except arguably running one service at a time. What flakes do is build software, which is the thing that Docker Compose doesn't really do. (Or doesn't do well.)
I'd compare flakes to Makefiles with waaay more expressiveness and reproducibility. Or maybe a comparison could be to a Dockerfile, minus containerization, with waaay more expressiveness and reproducibility.
There are tools you can add on to get Nix to do what Docker Compose does:
Arion is a Nix frontend for Docker Compose. You're still using Docker Compose, but it layers on the extra expressiveness and reproducibility of Nix flakes, or other kinds of Nix expressions.
process compose flake is similar, but instead of Docker Compose it is a frontend for Process Compose. You get a similar result, but without containerization. That can potentially avoid the need to run in a VM on non-Linux systems that don't natively support containers.