I cannot wait to get home and try it out!
Please consider reporting back after you’ve tried it; I’d love to read your experiences.
I cannot wait to get home and try it out!
Please consider reporting back after you’ve tried it; I’d love to read your experiences.
Wouldn’t it be fun to have “a ready-to-game Arch Linux based OCI designed for use exclusively in distrobox”?
There are like a gazillion questions one might ask to better derive what keyboard would suit you best. As so far you haven’t given us much to work with, I’ll just post my personal favorites:
Obviously, I’m a sucker for splittable keyboards that adhere to traditional layouts. With both of these being the current endgame-models within that space; tilt, wrist support, excellent software, good add-ons, name it and it’s probably found between the two.
The simple virtue of being able to genuinely express these words; “I don’t know”, “Sorry” and “Thank you” (or any derivative of these*).
Thank you for reporting back! Much appreciated!
Interesting. Unfortunately, I don’t own an Nvidia device. Therefore, I can’t tackle it myself. Distrobox should allow the use of Nvidia, but I’m unaware if this applies to the bazzite-arch container as well. The picture you shared and the link to its FAQ-page (found below) do suggest otherwise, unfortunately…
FWIW, I’ve always experienced better performance inside the bazzite-arch distrobox container, at least compared to Flatpak*.
Because the
distroimage it’s used in conjunction with, Bazzite, is Fedora-based, while Steam OS is based on Arch. Bazzite is Fedora-based in the first place, because Arch doesn’t officially have any plans for ‘immutable’ distros yet. As for the remaining distros, only Fedora and NixOS (see Jovian-NixOS) have a sufficiently mature and suitable platform at this point in time.This happens way more often than you might expect. Even the so-called ‘toolbox’ containers from Distrobox miss a lot of packages required to support software graphically. Consider running it inside a terminal and pay attention to error codes etc; those might/should help you resolve the issue. Sometimes it helps to explicitly use the
-v
or--verbose
option to ensure that the program actually communicates what’s happening.