If you want to check that a machine you’re buying is compatible with Linux, a good place to start is to google how to install drivers for the computer’s components on Linux. Check the common problem areas (WiFi, graphics, sound, etc.) and see if you find lots of other people complaining about those components. If you find evidence that a driver is available, or you can’t seem to find any info either way, it’s probably fine.
I can’t really answer the question you had regarding this site you found, but that is my general strategy for checking Linux hardware compatibility.
Also make sure that the retailer you’re buying from has a reasonable returns policy, just in case you get it, install Linux (or run it from a live USB, to avoid wiping the disk before you know you’re good), and discover something doesn’t work.
sounds like something is going seriously wrong, you should never really be having to deal with this stuff (ive been using arch and the AUR for several years and never have). Im not sure it its a steam deck thing or what. Only thing I can say is make sure to always run sudo pacman -Syu before you install a new package.
Yeah for real, this is my experience every time installing any package. Idk what the problem, but dealing with anything out of the discover store is a nightmare
I’ve created a tool for similar of use-cases: https://codeberg.org/contr/contr
You could run your workload inside, say, an alpine container:
<pre style="background-color:#ffffff;">
<span style="color:#323232;">cd path/to/evil/dir
</span><span style="color:#323232;">contr alpine
</span><span style="color:#323232;">❯ # inside container, run dangerous program
</span><span style="color:#323232;">❯ ./dangerous_program
</span>
If the program needs extra dependencies, you’ll have to write a Containerfile and build an image with the dependencies installed – there’s an example in the repository. Just installing the dependencies at runtime inside the container is also an option, but all changes inside the container are lost on exit.
gnome-initial-setup will default to displaying the toggle as enabled, even though the underlying setting will initially be disabled. (The underlying setting will not actually be enabled until the user finishes the privacy page, to ensure users have the opportunity to disable the setting before any data is uploaded.)
I see what they’re saying here and how they’re trying to give users options for users to opt-out before “accidentally” sharing data.
We are not interested in opt-in metrics. To make this a little more confusing, metrics collection is actually separate from uploading. Collection is always initially enabled, while uploading is always initially disabled. The graphical toggle enables or disables both at the same time.
Given all this I have even lower confidence that the opt-out will be bug free, especially over time. If the settings are separate then why just one toggle? If it were separate, I might want to collect then inspect the data and maybe even choose to share (or use the data myself some other way).
Few users would opt in…
Well yes, if it’s all my way or the highway. I understand that this is a tough problem to solve and a tougher one to message correctly. Hopefully someone will figure it out one day.
For me efficiency and less eye strain is important. I want my eyes to be at the center of the screen for the majority of my session. Gnome is my goto for that reason but any tiling windows manager would do as welll.
KDE and the windows start bar lookalikes constantly have your eyes going to the corner or sides to open and find apps.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.