<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Abdullah Musa</title>
    <description>The latest articles on DEV Community by Abdullah Musa (@retro-1o1).</description>
    <link>https://dev.to/retro-1o1</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3728987%2F7ef80779-e5b5-44a2-a26a-f94ee0677e57.jpeg</url>
      <title>DEV Community: Abdullah Musa</title>
      <link>https://dev.to/retro-1o1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/retro-1o1"/>
    <language>en</language>
    <item>
      <title>I ported ML4W's Hyprland dotfiles to NixOS. A missing log directory nearly stopped the whole thing.</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:05:58 +0000</pubDate>
      <link>https://dev.to/retro-1o1/i-ported-ml4ws-hyprland-dotfiles-to-nixos-a-missing-log-directory-nearly-stopped-the-whole-thing-5ef5</link>
      <guid>https://dev.to/retro-1o1/i-ported-ml4ws-hyprland-dotfiles-to-nixos-a-missing-log-directory-nearly-stopped-the-whole-thing-5ef5</guid>
      <description>&lt;p&gt;ML4W is a polished Hyprland setup with a GUI settings app, which makes it one of the gentler ways into Hyprland. It is also Arch-only. The installer assumes pacman, assumes systemd laid out the way Arch lays it out, and assumes it can write anywhere.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhvwh15em2neq04w0rcvv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhvwh15em2neq04w0rcvv.png" alt="ML4W Hyprland Dotfiles on NixOS" width="800" height="457"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I ported it to NixOS by hand. Translating the package list was the part I expected to be hard, and it took an afternoon of reading nixpkgs. The part that actually cost me was smaller and far more annoying.&lt;/p&gt;

&lt;p&gt;An installer does two things. It installs packages, which is visible and documented, and it creates preconditions, which is neither. On Arch nobody notices the second category because the installer handles it and the assumptions happen to hold. Port it somewhere else and those invisible preconditions are what break you.&lt;/p&gt;

&lt;p&gt;For ML4W there were three.&lt;/p&gt;

&lt;h2&gt;
  
  
  Precondition 1: a path that does not exist on NixOS
&lt;/h2&gt;

&lt;p&gt;ML4W's scripts hardcode &lt;code&gt;/bin/bash&lt;/code&gt;. NixOS does not have it, because everything lives in the store.&lt;/p&gt;

&lt;p&gt;Rather than patching shebangs across the whole dotfiles tree, create the path:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nix"&gt;&lt;code&gt;&lt;span class="n"&gt;systemd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;tmpfiles&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;rules&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="s2"&gt;"L+ /bin/bash - - - - ${pkgs.bash}/bin/bash"&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One thing that is easy to miss: after the rebuild you still need to make the rule take effect for the current boot.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo systemd-tmpfiles --create
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Precondition 2: executable bits
&lt;/h2&gt;

&lt;p&gt;The Arch installer marks ML4W's scripts executable as part of its run. Clone the repo and copy the configs yourself and you are responsible for that:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;find ~/.config/hypr -name &lt;span class="s2"&gt;"*.sh"&lt;/span&gt; -exec chmod +x &lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="o"&gt;}&lt;/span&gt; \&lt;span class="o"&gt;;&lt;/span&gt;
find ~/.config/waybar/ -name &lt;span class="s2"&gt;"*.sh"&lt;/span&gt; -exec chmod +x &lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="o"&gt;}&lt;/span&gt; \&lt;span class="o"&gt;;&lt;/span&gt;
find ~/.config/ml4w -type f -path &lt;span class="s2"&gt;"*/scripts/*"&lt;/span&gt; -exec chmod +x &lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="o"&gt;}&lt;/span&gt; \&lt;span class="o"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three separate trees, because ML4W keeps scripts in three places. Miss one and you get a desktop with a bar but no working buttons, which is a confusing state to debug because most of it looks fine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Precondition 3: the one that cost me an evening
&lt;/h2&gt;

&lt;p&gt;This is the good one.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir -p ~/.mydotfiles
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That directory holds nothing. Nothing is installed into it. It exists so a log file can be written into it.&lt;/p&gt;

&lt;p&gt;Here is the failure chain. &lt;code&gt;~/.config/hypr/conf/autostart.lua&lt;/code&gt; runs ML4W's autostart script and redirects its output to &lt;code&gt;~/.mydotfiles/ml4w-autostart.log&lt;/code&gt;. Shell redirection is set up &lt;strong&gt;before&lt;/strong&gt; the command runs. If the directory does not exist, the shell cannot create the log file, so the redirection fails, so &lt;code&gt;ml4w-autostart&lt;/code&gt; never executes at all.&lt;/p&gt;

&lt;p&gt;Which means you log into Hyprland and get a bare compositor. No bar, no wallpaper, no dock, no notifications. Nothing that was supposed to autostart started.&lt;/p&gt;

&lt;p&gt;And the detail that makes it genuinely nasty: the thing that failed was the log. There is no &lt;code&gt;ml4w-autostart.log&lt;/code&gt; to read, because being unable to create &lt;code&gt;ml4w-autostart.log&lt;/code&gt; is the entire problem. You go looking for the log that would explain the failure and its absence is the failure.&lt;/p&gt;

&lt;p&gt;One &lt;code&gt;mkdir&lt;/code&gt; fixes it. The Arch installer has always done it for you, silently, which is why it appears in no troubleshooting guide anywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  The package list, briefly
&lt;/h2&gt;

&lt;p&gt;Worth saying the translation was not trivial either, just predictable. Most of ML4W's dependencies map cleanly onto nixpkgs names. The Qt packages were where I lost time, because the Qt5 and Qt6 split is named inconsistently and you need pieces of both:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nix"&gt;&lt;code&gt;&lt;span class="n"&gt;qt5&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;qtwayland&lt;/span&gt; &lt;span class="n"&gt;qt6&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;qtwayland&lt;/span&gt; &lt;span class="n"&gt;qt6&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;qt5compat&lt;/span&gt;
&lt;span class="n"&gt;qt5Packages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;qt6ct&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read that last line twice. &lt;code&gt;qt6ct&lt;/code&gt;, the Qt 6 configuration tool, lives under &lt;code&gt;qt5Packages&lt;/code&gt;. That is not a typo in my config, it is where nixpkgs keeps it, and I spent a while convinced I had the wrong attribute name.&lt;/p&gt;

&lt;p&gt;Alongside that you need the Hyprland stack, the Wayland UI pieces (&lt;code&gt;waybar&lt;/code&gt;, &lt;code&gt;rofi&lt;/code&gt;, &lt;code&gt;swaynotificationcenter&lt;/code&gt;, &lt;code&gt;wlogout&lt;/code&gt;, &lt;code&gt;waypaper&lt;/code&gt;, &lt;code&gt;nwg-dock-hyprland&lt;/code&gt;), three Python modules ML4W's scripts import, and &lt;code&gt;quickshell&lt;/code&gt;, which compiles from source and is most of why the rebuild takes 5 to 15 minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  The whole sequence
&lt;/h2&gt;

&lt;p&gt;Services and the tmpfiles rule into &lt;code&gt;configuration.nix&lt;/code&gt;, packages into &lt;code&gt;environment.systemPackages&lt;/code&gt;, then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo nixos-rebuild switch
sudo systemd-tmpfiles --create
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Clone upstream and copy the configs across unmodified:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ~/Downloads
git clone https://github.com/mylinuxforwork/dotfiles.git
&lt;span class="nb"&gt;cd&lt;/span&gt; dotfiles/
cp -r dotfiles/.config/. ~/.config
cp dotfiles/.bashrc ~/.bashrc
cp dotfiles/.zshrc ~/.zshrc
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then the three &lt;code&gt;chmod&lt;/code&gt; passes, the &lt;code&gt;mkdir&lt;/code&gt;, and reboot. Pick Hyprland from your login manager's session menu.&lt;/p&gt;

&lt;p&gt;Check the directory layout in the clone before running those copies. ML4W reorganises between releases and these paths are the kind that move.&lt;/p&gt;

&lt;p&gt;Also worth knowing: NixOS lets you keep your existing desktop. I ran this on a Budgie install and Budgie was completely untouched, sitting in the session menu next to Hyprland. If the port had gone badly I would have logged back into a working desktop, which is a reasonable safety net for an unsupported install.&lt;/p&gt;

&lt;h2&gt;
  
  
  The transferable bit
&lt;/h2&gt;

&lt;p&gt;If you are porting installer-based software to a distro it does not support, read the installer for what it &lt;strong&gt;creates&lt;/strong&gt;, not just what it &lt;strong&gt;installs&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;grep&lt;/code&gt; it for &lt;code&gt;mkdir&lt;/code&gt;, for &lt;code&gt;chmod&lt;/code&gt;, for &lt;code&gt;ln -s&lt;/code&gt;, for anything touching paths outside its own tree. The package list is the part everyone translates because the package list is the visible part. The three lines that create a directory, flip some permission bits and make a symlink are the ones that will have you staring at a blank compositor at one in the morning.&lt;/p&gt;

&lt;p&gt;The full walkthrough, with the complete annotated package list, the DNS fix if your ISP blocks the Nix cache, screenshots of every step and a long FAQ, is on my site: &lt;a href="https://www.musabase.com/2026/09/install-ml4w-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;How to Install ML4W Hyprland Dotfiles on NixOS&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is one of a set. The same treatment for &lt;a href="https://www.musabase.com/2026/09/install-caelestia-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;Caelestia&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/10/install-end-4-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;End-4&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/09/install-jakoolit-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;JaKooLit&lt;/a&gt; and &lt;a href="https://www.musabase.com/2026/11/hyde-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;HyDE&lt;/a&gt; on NixOS, and a &lt;a href="https://www.musabase.com/p/best-hyprland-dotfiles-for-linux.html" rel="noopener noreferrer"&gt;comparison of all five&lt;/a&gt; if you have not picked one.&lt;/p&gt;

&lt;p&gt;If you have hit your own version of the &lt;code&gt;.mydotfiles&lt;/code&gt; bug, a precondition so invisible that its failure destroys the evidence of itself, I would like to read about it in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/09/install-ml4w-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>nixos</category>
      <category>linux</category>
      <category>hyprland</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>HyDE's README tells NixOS users to go use a different project. I made the real one run instead.</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Sun, 15 Nov 2026 08:03:38 +0000</pubDate>
      <link>https://dev.to/retro-1o1/hydes-readme-tells-nixos-users-to-go-use-a-different-project-i-made-the-real-one-run-instead-391p</link>
      <guid>https://dev.to/retro-1o1/hydes-readme-tells-nixos-users-to-go-use-a-different-project-i-made-the-real-one-run-instead-391p</guid>
      <description>&lt;p&gt;HyDE is the most theme-heavy Hyprland setup going: 70-plus built-in themes, a themed SDDM, its own lock screen, blur and glass effects configured out of the box. It is also Arch-native, and its installer assumes it can write wherever it likes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fof1551cffabkbcta8ayn.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fof1551cffabkbcta8ayn.webp" alt="HyDE Hyprland Dotfiles on NixOS" width="800" height="406"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;HyDE's own README handles this by pointing NixOS users at &lt;a href="https://github.com/richen604/hydenix" rel="noopener noreferrer"&gt;Hydenix&lt;/a&gt;, a home-manager rewrite of HyDE. That is a legitimate approach, and it is not the one I took.&lt;/p&gt;

&lt;p&gt;There are two strategies for getting software like this onto NixOS, and the choice between them is the actual content here.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rewrite the app, or rewrite the environment
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Strategy one: rewrite it as Nix.&lt;/strong&gt; Express every config, every service, every path as Nix modules. Idiomatic, declarative, pleasant to read. The cost is that you now own a fork. Every upstream change has to be ported by hand, and the rewrite drifts from the original until it is a different project that looks like HyDE.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Strategy two: leave upstream alone and fake the environment it expects.&lt;/strong&gt; Pin HyDE at a commit, run HyDE's own deployer, and build the FHS paths and runtimes its scripts assume into the system. Less pure. But upstream changes arrive by bumping one hash, and what you get is actual HyDE rather than a reimplementation of it.&lt;/p&gt;

&lt;p&gt;I went with the second. The whole thing is two files, &lt;code&gt;flake.nix&lt;/code&gt; and &lt;code&gt;hyde.nix&lt;/code&gt;, and the install is three commands:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; /etc/nixos
sudo curl -fLO https://raw.githubusercontent.com/musabase/hyde-hyprland-nixos/main/flake.nix
sudo curl -fLO https://raw.githubusercontent.com/musabase/hyde-hyprland-nixos/main/hyde.nix
sudo sed -i &lt;span class="s2"&gt;"s/CHANGEME/$(whoami)/"&lt;/span&gt; flake.nix
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo &lt;span class="nv"&gt;NIX_CONFIG&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"experimental-features = nix-command flakes"&lt;/span&gt; \
   nix-shell -p git --run &lt;span class="s2"&gt;"nixos-rebuild switch --flake /etc/nixos#nixos"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Reboot into a themed SDDM and you are in. About 20 minutes on my machine.&lt;/p&gt;

&lt;p&gt;Those files run as root during the rebuild, so read them before you run them. Both are printed in full in the guide, and pinning a commit instead of &lt;code&gt;main&lt;/code&gt; means they cannot change after you have reviewed them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four fixes, which are the actually interesting part
&lt;/h2&gt;

&lt;p&gt;Strategy two means the work is in the gaps between what HyDE assumes and what NixOS provides. Four stand out.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;HyDE hardcodes FHS paths.&lt;/strong&gt; &lt;code&gt;/bin/bash&lt;/code&gt;, &lt;code&gt;/usr/bin/python3&lt;/code&gt;, &lt;code&gt;/usr/share/oh-my-zsh&lt;/code&gt;, &lt;code&gt;/usr/bin/rofi&lt;/code&gt;. None of those exist on NixOS. Rather than patch every script, create them as symlinks:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nix"&gt;&lt;code&gt;&lt;span class="n"&gt;systemd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;tmpfiles&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;rules&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="s2"&gt;"L+ /bin/bash - - - - ${pkgs.bash}/bin/bash"&lt;/span&gt;
  &lt;span class="s2"&gt;"L+ /usr/bin/python3 - - - - ${hydePython}/bin/python3"&lt;/span&gt;
  &lt;span class="s2"&gt;"L+ /usr/share/oh-my-zsh - - - - ${hydeOmz}"&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;HyDE builds a uv venv and sources its activate script.&lt;/strong&gt; A real venv cannot live in the read-only Nix store, so the Python environment comes from nixpkgs and gets wrapped in something that provides a fake &lt;code&gt;activate&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nix"&gt;&lt;code&gt;&lt;span class="n"&gt;cat&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; $&lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;bin&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;activate&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&amp;lt;&lt;/span&gt;&lt;span class="s1"&gt;'EOF'&lt;/span&gt;
&lt;span class="no"&gt;VIRTUAL_ENV&lt;/span&gt;&lt;span class="o"&gt;=/&lt;/span&gt;&lt;span class="n"&gt;etc&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;hyde&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;python_env&lt;/span&gt;
&lt;span class="n"&gt;export&lt;/span&gt; &lt;span class="no"&gt;VIRTUAL_ENV&lt;/span&gt;
&lt;span class="k"&gt;case&lt;/span&gt; &lt;span class="s2"&gt;":$PATH:"&lt;/span&gt; &lt;span class="n"&gt;in&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="s2"&gt;":$VIRTUAL_ENV/bin:"&lt;/span&gt;&lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="no"&gt;PATH&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$VIRTUAL_ENV/bin:$PATH"&lt;/span&gt; &lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="n"&gt;esac&lt;/span&gt;
&lt;span class="n"&gt;export&lt;/span&gt; &lt;span class="no"&gt;PATH&lt;/span&gt;
&lt;span class="n"&gt;deactivate&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="no"&gt;EOF&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The environments are exposed at &lt;code&gt;/etc/hyde/&lt;/code&gt; specifically because &lt;code&gt;/etc&lt;/code&gt; survives garbage collection, so HyDE's scripts always find them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;killall&lt;/code&gt; does not match Nix wrapper names.&lt;/strong&gt; HyDE restarts Waybar and Dunst with plain &lt;code&gt;killall waybar&lt;/code&gt;. NixOS names the running process &lt;code&gt;.waybar-wrapped&lt;/code&gt;, so the call silently fails and your bar never comes back. Fix is a shim that retries with a regex:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;${pkgs.psmisc}&lt;/span&gt;/bin/killall &lt;span class="s2"&gt;"$@"&lt;/span&gt; 2&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/dev/null &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;exit&lt;/span&gt; 0
&lt;span class="nv"&gt;name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"${!#}"&lt;/span&gt;
&lt;span class="nb"&gt;set&lt;/span&gt; -- &lt;span class="s2"&gt;"${@:1:$#-1}"&lt;/span&gt;
&lt;span class="nb"&gt;exec&lt;/span&gt; &lt;span class="nv"&gt;${pkgs.psmisc}&lt;/span&gt;/bin/killall &lt;span class="s2"&gt;"$@"&lt;/span&gt; -r &lt;span class="s2"&gt;"^\.?${name}(-wrapped)?$"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Installed with &lt;code&gt;lib.hiPrio&lt;/code&gt; so it wins over the real one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My favourite: luarocks is installed to satisfy a check.&lt;/strong&gt; HyDE's activate script refuses to start unless &lt;code&gt;luarocks&lt;/code&gt; is on PATH. The Lua modules themselves come from nixpkgs and luarocks never installs anything. It is there purely so the presence test passes.&lt;/p&gt;

&lt;p&gt;There is one more worth mentioning because of how it fails. One line in HyDE's &lt;code&gt;theme.switch.sh&lt;/code&gt; looks for themes in the read-only system profile, and it gets rewritten with &lt;code&gt;substituteInPlace --replace-fail&lt;/code&gt;. The &lt;code&gt;--replace-fail&lt;/code&gt; matters: if upstream ever changes that line, the build breaks loudly instead of deploying something subtly wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this costs you
&lt;/h2&gt;

&lt;p&gt;Being straight about the trade-offs, because the flake makes two decisions on your behalf.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It follows &lt;code&gt;nixos-unstable&lt;/code&gt;.&lt;/strong&gt; Not just for HyDE, for your whole system. HyDE needs a recent Hyprland and Qt, so if you installed from the stable ISO this rebuild moves everything to unstable. Intentional, and rollback from the boot menu works, but you should know going in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The dotfiles land in &lt;code&gt;$HOME&lt;/code&gt;, and a rollback does not remove them.&lt;/strong&gt; &lt;code&gt;nixos-rebuild switch --rollback&lt;/code&gt; undoes every system change cleanly. It does not touch the files HyDE copied into your home folder, because those were copied by a user service rather than built into a generation. Uninstalling is genuinely two steps.&lt;/p&gt;

&lt;p&gt;Budget 30GB on root. The install itself is around 20GB.&lt;/p&gt;

&lt;p&gt;Also worth knowing: the first login looks half-styled for a few minutes while HyDE imports its theme pack from GitHub. Wait for the "Setup finished" notification before rebooting.&lt;/p&gt;

&lt;h2&gt;
  
  
  The broader point
&lt;/h2&gt;

&lt;p&gt;NixOS discussions default to the rewrite. Something is not packaged, so you express it in Nix and own the result.&lt;/p&gt;

&lt;p&gt;The alternative is cheaper than it looks. Most Arch-native software does not need porting, it needs a handful of paths, a runtime and an environment variable. Build that illusion and upstream runs unmodified, which means you track upstream by changing a commit hash instead of by reading diffs.&lt;/p&gt;

&lt;p&gt;The full walkthrough, with both &lt;code&gt;.nix&lt;/code&gt; files printed and annotated line by line, the NVIDIA additions, the uninstall steps and a long FAQ, is on my site: &lt;a href="https://www.musabase.com/2026/11/hyde-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;How to Install HyDE Hyprland Dotfiles on NixOS&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This completes the set. The same treatment for &lt;a href="https://www.musabase.com/2026/09/install-caelestia-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;Caelestia&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/10/install-end-4-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;End-4&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/09/install-jakoolit-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;JaKooLit&lt;/a&gt; and &lt;a href="https://www.musabase.com/2026/09/install-ml4w-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;ML4W&lt;/a&gt; on NixOS, and a &lt;a href="https://www.musabase.com/p/best-hyprland-dotfiles-for-linux.html" rel="noopener noreferrer"&gt;comparison of all five&lt;/a&gt; if you have not picked one yet.&lt;/p&gt;

&lt;p&gt;If you have taken the rewrite route instead, with Hydenix or your own modules, I want to hear how maintenance has gone over time. That is the part I cannot test from one side of the fence.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/11/hyde-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>nixos</category>
      <category>linux</category>
      <category>hyprland</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>GE-Proton installs with a single tar command. Here is why I still use the GUI.</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Sat, 14 Nov 2026 08:49:29 +0000</pubDate>
      <link>https://dev.to/retro-1o1/ge-proton-installs-with-a-single-tar-command-here-is-why-i-still-use-the-gui-158g</link>
      <guid>https://dev.to/retro-1o1/ge-proton-installs-with-a-single-tar-command-here-is-why-i-still-use-the-gui-158g</guid>
      <description>&lt;p&gt;GE-Proton is a tarball. Installing it means extracting that tarball into a directory where Steam will look for it. There is no build step, no installer, no package to register.&lt;/p&gt;

&lt;p&gt;Which makes ProtonUp-Qt an odd thing to recommend, because the job it does is &lt;code&gt;tar&lt;/code&gt;. I recommend it anyway, and the reason is worth more than the tutorial.&lt;/p&gt;

&lt;h2&gt;
  
  
  The manual version, so you can see the size of the problem
&lt;/h2&gt;

&lt;p&gt;Download a release from the GE-Proton repo, then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;tar -xf GE-Proton*.tar.gz -C ~/.steam/steam/compatibilitytools.d/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Create that directory first if it does not exist. Restart Steam. The version now appears in the compatibility tool dropdown.&lt;/p&gt;

&lt;p&gt;That is the entire installation. One command.&lt;/p&gt;

&lt;p&gt;Now the same thing for Flatpak Steam:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;tar -xf GE-Proton*.tar.gz -C ~/.var/app/com.valvesoftware.Steam/data/Steam/compatibilitytools.d/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Still one command. Different path.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem is combinatorial, not difficult
&lt;/h2&gt;

&lt;p&gt;Steam alone has two target directories depending on how it was installed. Bottles keeps its runners somewhere else entirely, and also splits by native versus Flatpak. Lutris has its own location. Heroic has another.&lt;/p&gt;

&lt;p&gt;None of those paths are hard. There are just a lot of them, they are all long, they are all invisible, and you will get one wrong at some point and spend twenty minutes wondering why the dropdown is empty.&lt;/p&gt;

&lt;p&gt;On top of that, you need to know which GE-Proton versions exist. The release tags are not sequential with Valve's Proton numbering, ProtonDB reports often name a specific build, and figuring out whether &lt;code&gt;GE-Proton10-27&lt;/code&gt; is current means opening a browser.&lt;/p&gt;

&lt;p&gt;ProtonUp-Qt is a dropdown of install targets, a dropdown of available versions, and a button. It is not solving a hard problem. It is removing a class of small stupid errors, which is a perfectly good reason for a tool to exist.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;yay -S protonup-qt
&lt;span class="c"&gt;# or&lt;/span&gt;
flatpak install flathub net.davidotek.pupgui2
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The AUR build integrates with your system packages. The Flatpak runs sandboxed and updates on its own schedule. If you install the Flatpak and run native Steam, that is the combination most likely to need a filesystem permission check, so keep Flatseal handy.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one gotcha that will actually bite you
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Close Steam completely before installing anything.&lt;/strong&gt; Not minimised to tray. Closed.&lt;/p&gt;

&lt;p&gt;Steam scans &lt;code&gt;compatibilitytools.d&lt;/code&gt; when it starts and writes its own config when it exits. Drop files in while it is running and you get one of two outcomes: Steam never notices the new tool, or it overwrites its config on quit and the registration vanishes. Either way the dropdown stays empty and nothing tells you why.&lt;/p&gt;

&lt;p&gt;This is the single most common failure with ProtonUp-Qt and it is not the tool's fault. It is a consequence of Steam treating that directory as a startup-time read.&lt;/p&gt;

&lt;p&gt;Bottles has no equivalent problem. It reads its runners directory when you open the components list.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow, compressed
&lt;/h2&gt;

&lt;p&gt;For Steam: open ProtonUp-Qt, Steam is usually preselected, click &lt;strong&gt;Add version&lt;/strong&gt;, pick &lt;strong&gt;GE-Proton&lt;/strong&gt; as the compatibility tool, pick a version, install.&lt;/p&gt;

&lt;p&gt;For Bottles: select &lt;strong&gt;Bottles&lt;/strong&gt; in the same dropdown, &lt;strong&gt;Add Version&lt;/strong&gt;, choose &lt;strong&gt;ProtonGE&lt;/strong&gt; from the Compatibility list, pick a version, install. Takes a few minutes.&lt;/p&gt;

&lt;p&gt;Then point a game at it. Steam: right-click the game, Properties, Compatibility, tick &lt;strong&gt;Force the use of a specific Steam Play compatibility tool&lt;/strong&gt;, choose your GE-Proton build. Bottles: open the bottle, Settings, Components, pick the runner from the dropdown and accept the Proton disclaimer.&lt;/p&gt;

&lt;p&gt;Note that ProtonUp-Qt manages each target separately. Installing GE-Proton for Steam does not make it available in Bottles. Two installs, one tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  What GE-Proton is not
&lt;/h2&gt;

&lt;p&gt;It is not a free frame rate boost, and it gets recommended as though it were.&lt;/p&gt;

&lt;p&gt;GE-Proton is Valve's Proton plus patches: fixes for specific games that are broken on stock Proton, media codecs so cutscenes play instead of showing a black screen, and upscaling work that lands ahead of upstream. The value is categorical, not incremental. A game either needs one of those patches or it does not.&lt;/p&gt;

&lt;p&gt;So the honest usage pattern is reactive. Run stock Proton first. When a game refuses to launch, crashes at a cutscene, or shows a known issue on ProtonDB with a specific GE build named in the reports, install that build and force it for that one game. Switching your whole library to GE-Proton by default buys you nothing and costs you Valve's own testing.&lt;/p&gt;

&lt;p&gt;In my case Red Dead Redemption 2 was the game that made this necessary. It would not run reliably on stock Proton and it did on GE-Proton. That is the shape of the problem this solves.&lt;/p&gt;

&lt;p&gt;The full walkthrough with screenshots of every ProtonUp-Qt dialog, both install methods and a longer FAQ is on my site: &lt;a href="https://www.musabase.com/2026/08/protonup-qt-and-ge-proton-on-arch-linux.html" rel="noopener noreferrer"&gt;ProtonUp-Qt and GE-Proton on Arch Linux&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is part of a wider Linux gaming series: &lt;a href="https://www.musabase.com/2026/01/run-windows-games-on-linux-using-steam-proton.html" rel="noopener noreferrer"&gt;Steam and Proton&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/02/run-non-steam-games-on-arch-linux-bottles.html" rel="noopener noreferrer"&gt;Bottles&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/03/windows-games-on-arch-linux-with-wine.html" rel="noopener noreferrer"&gt;Wine&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/04/msi-afterburner-alternative-on-linux.html" rel="noopener noreferrer"&gt;CoreCtrl and MangoHud&lt;/a&gt;, and &lt;a href="https://www.musabase.com/2026/04/gaming-on-linux-vs-windows.html" rel="noopener noreferrer"&gt;a year of gaming on both Linux and Windows&lt;/a&gt;. The &lt;a href="https://www.musabase.com/p/linux-gaming-roadmap-complete-musabase.html" rel="noopener noreferrer"&gt;Linux Gaming Roadmap&lt;/a&gt; indexes all of it.&lt;/p&gt;

&lt;p&gt;If you keep a specific GE-Proton build pinned for a particular game, I would like to know which game and which build in the comments. That pairing is the most useful thing to share here and it is scattered across ProtonDB reports.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/08/protonup-qt-and-ge-proton-on-arch-linux.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>archlinux</category>
      <category>steam</category>
    </item>
    <item>
      <title>CoreCtrl hides every AMD overclocking control until you pass one kernel parameter</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:13:16 +0000</pubDate>
      <link>https://dev.to/retro-1o1/corectrl-hides-every-amd-overclocking-control-until-you-pass-one-kernel-parameter-52o4</link>
      <guid>https://dev.to/retro-1o1/corectrl-hides-every-amd-overclocking-control-until-you-pass-one-kernel-parameter-52o4</guid>
      <description>&lt;p&gt;MSI Afterburner has no Linux port and does not work usefully under Wine, because it leans on Windows drivers. On AMD the replacement is two separate tools: &lt;strong&gt;CoreCtrl&lt;/strong&gt; for the hardware knobs, &lt;strong&gt;MangoHud&lt;/strong&gt; for the on-screen display.&lt;/p&gt;

&lt;p&gt;Installing both takes about a minute. The part that makes people give up is what happens next: you open CoreCtrl, switch Performance mode to Advanced expecting voltage and clock sliders, and find two controls. A power limit slider and a power profile dropdown. That is it.&lt;/p&gt;

&lt;p&gt;CoreCtrl is not missing those features. Your kernel is hiding them. There are two locked doors here, and neither is obvious from the UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  The split
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;yay -S corectrl        &lt;span class="c"&gt;# AUR, not in the official repos&lt;/span&gt;
sudo pacman -S mangohud
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;CoreCtrl talks directly to the &lt;code&gt;amdgpu&lt;/code&gt; driver: fan curves, power limits, clocks, voltage, and per-application profiles. It has no in-game overlay at all.&lt;/p&gt;

&lt;p&gt;MangoHud is that overlay, for Vulkan and OpenGL. FPS, frametime graph, GPU and CPU temps, clocks, usage. The Steam Deck ships it.&lt;/p&gt;

&lt;p&gt;Afterburner on Windows is really Afterburner plus RTSS. This is the same division of labour, just with the seams visible.&lt;/p&gt;

&lt;h2&gt;
  
  
  Door 1: the kernel is withholding the controls
&lt;/h2&gt;

&lt;p&gt;The &lt;code&gt;amdgpu&lt;/code&gt; driver hides overclocking and voltage control by default, for stability. You unlock it with a kernel parameter.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo nano /etc/default/grub
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Append to the existing &lt;code&gt;GRUB_CMDLINE_LINUX_DEFAULT&lt;/code&gt; line, do not replace it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;&lt;span class="na"&gt;amdgpu.ppfeaturemask&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mh"&gt;0xffffffff&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;So the line ends up looking something like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;&lt;span class="na"&gt;GRUB_CMDLINE_LINUX_DEFAULT&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"quiet splash amdgpu.ppfeaturemask=0xffffffff"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then regenerate and reboot:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo grub-mkconfig -o /boot/grub/grub.cfg
reboot
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On systemd-boot or Limine the parameter goes into that bootloader's kernel command line instead, same value.&lt;/p&gt;

&lt;p&gt;Confirm it actually took, because a typo here fails silently and you will spend twenty minutes blaming CoreCtrl:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cat /proc/cmdline &lt;span class="o"&gt;|&lt;/span&gt; grep amdgpu.ppfeaturemask
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Reopen CoreCtrl, Performance mode, Advanced. The full set of controls is there now.&lt;/p&gt;

&lt;p&gt;What that hex is doing: &lt;code&gt;ppfeaturemask&lt;/code&gt; is a bitmask of PowerPlay features the driver will expose. Setting it to all ones tells the driver to stop hiding things the hardware already supports. It is a disclosure switch, not an overclock. It works on RX 400 series and newer desktop cards, and can cause instability on some laptop GPUs, in which case you remove the parameter and reboot. Nothing is permanent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Door 2: Polkit, or the password prompt forever
&lt;/h2&gt;

&lt;p&gt;CoreCtrl needs root to touch GPU hardware, so it does not autostart cleanly. Adding the desktop entry is the easy half:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir -p ~/.config/autostart
cp /usr/share/applications/org.corectrl.CoreCtrl.desktop ~/.config/autostart/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That &lt;code&gt;mkdir&lt;/code&gt; is not optional padding. On a fresh install &lt;code&gt;~/.config/autostart&lt;/code&gt; often does not exist, and &lt;code&gt;cp&lt;/code&gt; fails with a "No such file or directory" that reads like a missing CoreCtrl file rather than a missing folder.&lt;/p&gt;

&lt;p&gt;Now it launches at login and immediately asks for your password. Every single boot. The fix depends on your Polkit version, so check first:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pkaction --version
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;106 or newer&lt;/strong&gt; gets a rules file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo nano /etc/polkit-1/rules.d/90-corectrl.rules
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="n"&gt;polkit&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;addRule&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;function&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s2"&gt;"org.corectrl.helper.init"&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt;
         &lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s2"&gt;"org.corectrl.helperkiller.init"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt;
        &lt;span class="n"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;local&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt;
        &lt;span class="n"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;active&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt;
        &lt;span class="n"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isInGroup&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"wheel"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;polkit&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Result&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;YES&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Older than 106&lt;/strong&gt; gets a pkla file at &lt;code&gt;/etc/polkit-1/localauthority/50-local.d/90-corectrl.pkla&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="k"&gt;[User permissions]&lt;/span&gt;
&lt;span class="na"&gt;Identity&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;unix&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;group&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;wheel&lt;/span&gt;
&lt;span class="na"&gt;Action&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;org&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;corectrl&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="na"&gt;ResultActive&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;yes&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Swap &lt;code&gt;wheel&lt;/code&gt; for &lt;code&gt;sudo&lt;/code&gt; if that is your admin group. Note what the rules version is actually checking: local session, active session, correct group. It is not a blanket "skip auth", which is why it is a reasonable thing to put on your own machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  MangoHud, three ways
&lt;/h2&gt;

&lt;p&gt;Unlike CoreCtrl, MangoHud is not persistent. You tell it to attach, per game.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Steam:&lt;/strong&gt; right-click the game, Properties, Launch Options:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mangohud %command%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Bottles:&lt;/strong&gt; Settings, Performance, enable Monitor Performance. No command needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Wine or a bare executable:&lt;/strong&gt; prefix it.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mangohud &lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games wine &lt;span class="s2"&gt;"/path/to/game.exe"&lt;/span&gt;
mangohud ./your-game
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Vanilla MangoHud shows very little: CPU usage, GPU usage, API and FPS, frametime graph. Press &lt;strong&gt;Shift+F10&lt;/strong&gt; in-game to cycle preset layouts until you get the detail level you want, no restart required. For a permanent layout, write &lt;code&gt;~/.config/MangoHud/MangoHud.conf&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest part
&lt;/h2&gt;

&lt;p&gt;I do not overclock. My card is an RX 580 8GB in an i5-4460 box, and there is no headroom worth chasing there.&lt;/p&gt;

&lt;p&gt;What I actually use this stack for is a custom fan curve and a profile that activates automatically when Bottles launches. CoreCtrl's automatic activation takes an executable path and applies the profile when that binary runs, so the card is quiet at the desktop and aggressive when a game starts, with nothing to click.&lt;/p&gt;

&lt;p&gt;That is the part worth the setup even if you never touch a voltage slider. Unlocking the kernel parameter is what makes the fan curve editor behave properly in the first place, which is why it is step one rather than an advanced extra.&lt;/p&gt;

&lt;p&gt;The full walkthrough with screenshots of every CoreCtrl tab, the profile and fan curve setup in detail, and a longer FAQ is on my site: &lt;a href="https://www.musabase.com/2026/04/msi-afterburner-alternative-on-linux.html" rel="noopener noreferrer"&gt;MSI Afterburner Alternative on Linux: CoreCtrl and MangoHud for AMD GPUs&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It sits alongside the rest of my Linux gaming series: &lt;a href="https://www.musabase.com/2026/01/run-windows-games-on-linux-using-steam-proton.html" rel="noopener noreferrer"&gt;Steam and Proton&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/02/run-non-steam-games-on-arch-linux-bottles.html" rel="noopener noreferrer"&gt;Bottles&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/03/windows-games-on-arch-linux-with-wine.html" rel="noopener noreferrer"&gt;Wine&lt;/a&gt;, and a &lt;a href="https://www.musabase.com/2026/04/gaming-on-linux-vs-windows.html" rel="noopener noreferrer"&gt;year of gaming on both Linux and Windows&lt;/a&gt;. The &lt;a href="https://www.musabase.com/p/linux-gaming-roadmap-complete-musabase.html" rel="noopener noreferrer"&gt;Linux Gaming Roadmap&lt;/a&gt; indexes all of it.&lt;/p&gt;

&lt;p&gt;If you run LACT instead of CoreCtrl, I would like to hear why in the comments. It has a more modern interface and I keep meaning to give it a proper run.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/04/msi-afterburner-alternative-on-linux.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>amd</category>
      <category>gaming</category>
      <category>archlinux</category>
    </item>
    <item>
      <title>Proton and Bottles are both Wine. Here is every click they were hiding, as a command.</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Mon, 09 Nov 2026 07:15:53 +0000</pubDate>
      <link>https://dev.to/retro-1o1/proton-and-bottles-are-both-wine-here-is-every-click-they-were-hiding-as-a-command-bf9</link>
      <guid>https://dev.to/retro-1o1/proton-and-bottles-are-both-wine-here-is-every-click-they-were-hiding-as-a-command-bf9</guid>
      <description>&lt;p&gt;Proton is Wine with Valve's gaming patches. Bottles is a GUI that manages Wine environments for you. Both are excellent, and if your games run, there is no reason to leave them.&lt;/p&gt;

&lt;p&gt;The reason to learn raw Wine is the day one doesn't. When Bottles shrugs and Proton gives you a black screen, a tool that hides the machinery leaves you with nothing to try. So after two parts of this series on Proton and on Bottles, here is the same job done by hand, with each command mapped to the button that was running it for you.&lt;/p&gt;

&lt;p&gt;Nothing here is new behaviour. It is the same layer, with the lid off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Install
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pacman &lt;span class="nt"&gt;-S&lt;/span&gt; wine wine-mono wine-gecko
&lt;span class="nb"&gt;sudo &lt;/span&gt;pacman &lt;span class="nt"&gt;-S&lt;/span&gt; winetricks
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;wine-mono&lt;/code&gt; and &lt;code&gt;wine-gecko&lt;/code&gt; cover .NET applications and anything embedding a browser, and you want them from the start rather than when something fails confusingly. For newer patches:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pacman &lt;span class="nt"&gt;-S&lt;/span&gt; wine-staging
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Multilib has to be on first. Plenty of Windows games are still 32-bit, and Wine cannot run them without it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-E&lt;/span&gt; &lt;span class="s2"&gt;"^&lt;/span&gt;&lt;span class="se"&gt;\[&lt;/span&gt;&lt;span class="s2"&gt;multilib&lt;/span&gt;&lt;span class="se"&gt;\]&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; /etc/pacman.conf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  The prefix is the entire idea
&lt;/h2&gt;

&lt;p&gt;Every command below starts with &lt;code&gt;WINEPREFIX=&lt;/code&gt;. That is not boilerplate, it is the whole concept.&lt;/p&gt;

&lt;p&gt;A prefix is a folder holding a fake Windows install: its own C: drive, its own registry, its own installed libraries. Wine defaults to &lt;code&gt;~/.wine&lt;/code&gt; if you say nothing, which is how people end up with one shared prefix where a dependency installed for one game breaks another.&lt;/p&gt;

&lt;p&gt;Bottles calls these bottles, and gives you a Create button. Proton makes one per game, silently, under your Steam library. Doing it yourself is two lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;mkdir&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt; ~/wine/my-games
&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games winecfg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;winecfg&lt;/code&gt; builds the prefix and opens a settings window where you set the Windows version and per-library overrides. That window is the same thing Bottles exposes as its Compatibility tab.&lt;/p&gt;

&lt;p&gt;One prefix per game, or per small group of games that need the same dependencies. That is the habit worth forming, and it is also the thing the convenience tools were quietly doing right.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the one-click tools install for you
&lt;/h2&gt;

&lt;h3&gt;
  
  
  DirectX translation
&lt;/h3&gt;

&lt;p&gt;Bottles pulls these in when you create a bottle. Here, you install them and point them at your prefix:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;yay &lt;span class="nt"&gt;-S&lt;/span&gt; dxvk-bin vkd3d-proton-bin
&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games setup_dxvk &lt;span class="nb"&gt;install
&lt;/span&gt;&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games setup_vkd3d_proton &lt;span class="nb"&gt;install&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;DXVK converts Direct3D 9 through 11 calls into Vulkan. VKD3D-Proton does Direct3D 12. Without them you are on Wine's own Direct3D-to-OpenGL path, which is slower and will show it.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Windows runtimes
&lt;/h3&gt;

&lt;p&gt;This is the part Bottles' installers and Proton's bundled components handle invisibly, and the part that produces the cryptic missing-DLL errors when it is absent.&lt;/p&gt;

&lt;p&gt;Visual C++ runtimes, all of them, because games pick whichever they were built against:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games winetricks vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015 vcrun2017 vcrun2019 vcrun2022
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If &lt;code&gt;vcrun2017&lt;/code&gt; collides with the newer ones, install those separately:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games winetricks &lt;span class="nt"&gt;--force&lt;/span&gt; vcrun2017 vcrun2019 vcrun2022
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then .NET, DirectX helper libraries, and fonts:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games winetricks dotnet48 dotnet472
&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games winetricks d3dx9 d3dx10 d3dx11_43 d3dcompiler_43 d3dcompiler_47
&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games winetricks corefonts
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Skip &lt;code&gt;corefonts&lt;/code&gt; and you get games with missing or mangled text, which looks like a rendering bug and isn't.&lt;/p&gt;

&lt;h2&gt;
  
  
  Launching
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;WINEPREFIX&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;~/wine/my-games wine &lt;span class="s2"&gt;"path/to/game.exe"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is it. No install step, no library entry, no launcher. Point Wine at an executable.&lt;/p&gt;

&lt;p&gt;Games I run this way on Arch: Far Cry 3 Remastered, Need for Speed Heat, Death Stranding 2 On the Beach, and Ori and the Will of the Wisps.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you want the middle ground
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;yay &lt;span class="nt"&gt;-S&lt;/span&gt; winegui
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;WineGUI manages prefixes graphically while leaving them as ordinary folders you can still drive from a terminal. Useful when you want the overview without giving up the command line, and it sits closer to Wine than Bottles does.&lt;/p&gt;

&lt;h2&gt;
  
  
  When this is actually the right call
&lt;/h2&gt;

&lt;p&gt;Honestly: not for daily gaming. For a Steam title, use Proton. For an Epic or GOG game, use Bottles. Both will be faster to set up and will work.&lt;/p&gt;

&lt;p&gt;Drop to Wine when something refuses to run and you need to see why, when you want a genuinely clean prefix with only the libraries one game needs, or when you want to understand the layer the other two are built on. That last one pays off every time you troubleshoot afterwards, because you stop guessing at what the GUI is doing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full guide
&lt;/h2&gt;

&lt;p&gt;The complete walkthrough with screenshots, the WineGUI prefix workflow, the Wine architecture breakdown and a long FAQ is on my site: &lt;a href="https://www.musabase.com/2026/03/windows-games-on-arch-linux-with-wine.html" rel="noopener noreferrer"&gt;Run Windows Games on Arch Linux with Wine&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is part 3 of a series. &lt;a href="https://www.musabase.com/2026/01/run-windows-games-on-linux-using-steam-proton.html" rel="noopener noreferrer"&gt;Part 1 covers Steam and Proton&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/02/run-non-steam-games-on-arch-linux-bottles.html" rel="noopener noreferrer"&gt;part 2 covers Bottles&lt;/a&gt;, and the &lt;a href="https://www.musabase.com/p/linux-gaming-roadmap-complete-musabase.html" rel="noopener noreferrer"&gt;Linux Gaming Roadmap&lt;/a&gt; indexes all of it.&lt;/p&gt;

&lt;p&gt;If you keep a winetricks verb list that saves you time, I would like to see it in the comments. Mine is above and it is certainly not optimal.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/03/windows-games-on-arch-linux-with-wine.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>archlinux</category>
      <category>wine</category>
    </item>
    <item>
      <title>I installed Bottles twice on Arch to settle the Flatpak vs AUR question</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Thu, 29 Oct 2026 09:58:09 +0000</pubDate>
      <link>https://dev.to/retro-1o1/i-installed-bottles-twice-on-arch-to-settle-the-flatpak-vs-aur-question-1ge7</link>
      <guid>https://dev.to/retro-1o1/i-installed-bottles-twice-on-arch-to-settle-the-flatpak-vs-aur-question-1ge7</guid>
      <description>&lt;p&gt;Steam on Linux is a solved problem. Proton handles it, and most of your library just works.&lt;/p&gt;

&lt;p&gt;Everything else is where people give up and keep a Windows partition around. Six years of Epic freebies you claimed and never opened. GOG classics. That one &lt;code&gt;.exe&lt;/code&gt; sitting on an old drive. &lt;a href="https://usebottles.com/" rel="noopener noreferrer"&gt;Bottles&lt;/a&gt; handles all of it, and the install takes one command.&lt;/p&gt;

&lt;p&gt;The catch is that there are two commands, and the one you pick decides how much configuration you do afterwards. I ran both on the same machine, so here's the comparison instead of a coin flip.&lt;/p&gt;

&lt;h2&gt;
  
  
  The two paths
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# AUR&lt;/span&gt;
yay &lt;span class="nt"&gt;-S&lt;/span&gt; bottles

&lt;span class="c"&gt;# Flatpak&lt;/span&gt;
flatpak &lt;span class="nb"&gt;install &lt;/span&gt;flathub com.usebottles.bottles
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Both give you working Bottles. They don't conflict, and you can genuinely have both installed, which is how I ended up with two entries in my application menu.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;AUR&lt;/th&gt;
&lt;th&gt;Flatpak&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Integration&lt;/td&gt;
&lt;td&gt;Native system libraries and GPU drivers&lt;/td&gt;
&lt;td&gt;Sandboxed, bundled dependencies&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Permissions&lt;/td&gt;
&lt;td&gt;Nothing to configure&lt;/td&gt;
&lt;td&gt;Flatseal, manually, per folder&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GPU drivers&lt;/td&gt;
&lt;td&gt;Uses your system Vulkan and Mesa directly&lt;/td&gt;
&lt;td&gt;Needs runtime extensions installed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Game drives&lt;/td&gt;
&lt;td&gt;Sees them&lt;/td&gt;
&lt;td&gt;Can't see them until you say so&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Isolation&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;Full sandbox&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What the sandbox actually costs
&lt;/h2&gt;

&lt;p&gt;This is the part most guides skip, and it's three extra things.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Flatseal, or Bottles can't see your games.&lt;/strong&gt; A sandboxed app can't read outside its sandbox, so your second drive full of Windows games is invisible. You grant access per folder with &lt;a href="https://flathub.org/apps/com.github.tchx84.Flatseal" rel="noopener noreferrer"&gt;Flatseal&lt;/a&gt;. You can tick "All system files" instead, and it works, but that hands any game you run access to your entire system, which is the exact thing the sandbox existed to prevent. Grant the folders you need.&lt;/p&gt;

&lt;p&gt;You also need "All devices" on, which isn't obvious. Games want GPU acceleration, shared memory and input devices. Without it they'll launch and then run badly, or not see your controller.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GPU runtime extensions, or things render wrong.&lt;/strong&gt; The Flatpak build doesn't inherit your full graphics stack. Wine and most Windows games still want 32-bit graphics libraries:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;flatpak &lt;span class="nb"&gt;install &lt;/span&gt;flathub org.freedesktop.Platform.GL.default
flatpak &lt;span class="nb"&gt;install &lt;/span&gt;flathub org.freedesktop.Platform.GL32.default
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The 32-bit one is the one people forget. NVIDIA usually matches the host driver automatically, so you shouldn't need to do this by hand there.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;MangoHud separately, if you want an overlay.&lt;/strong&gt; The Monitor Performance toggle in Bottles sits greyed out until the Flatpak layer exists:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;flatpak &lt;span class="nb"&gt;install &lt;/span&gt;flathub org.freedesktop.Platform.VulkanLayer.MangoHud
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;None of this is hard. It's just three steps the AUR build doesn't ask for, which is why I'd tell most Arch users to run &lt;code&gt;yay -S bottles&lt;/code&gt; and move on. Take Flatpak if you specifically want the isolation, and know you're paying for it in setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part that's genuinely easy
&lt;/h2&gt;

&lt;p&gt;Once Bottles is running, the workflow is short. Create a bottle, name it, pick &lt;strong&gt;Gaming&lt;/strong&gt; as the purpose, leave the runner on &lt;strong&gt;Soda&lt;/strong&gt;, click Create. Bottles pulls DXVK, VKD3D and the rest itself.&lt;/p&gt;

&lt;p&gt;For Epic: open the bottle, Install Programs, pick Epic Games Store, Start Installation. Two to five minutes. It then appears in Programs with a play button, and the launcher behaves like it does on Windows, updates, login and all. GOG works the same way through the same installer list.&lt;/p&gt;

&lt;p&gt;For a loose &lt;code&gt;.exe&lt;/code&gt;, including games already installed on a Windows drive: Programs, Add Shortcuts, browse to the executable, done. No install step at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  The trick worth stealing
&lt;/h2&gt;

&lt;p&gt;I wanted Need for Speed Most Wanted 2005 at 1080p. It officially caps at 720p, and the usual fix is a widescreen mod, which doesn't reliably work through Wine because the mod's hook DLL never gets loaded.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F42psb40q39so8vskogkp.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F42psb40q39so8vskogkp.webp" alt="Need for Speed Most Wanted 2005, running on Linux at 1080p" width="800" height="481"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Bottles has this built in. Open the bottle, Compatibility, DLL Overrides, type &lt;code&gt;dinput8&lt;/code&gt;, save.&lt;/p&gt;

&lt;p&gt;That tells the bottle to prefer the mod's DLL over Wine's built-in one, and the mod starts working. It's a two-second fix that applies to a lot of older games, since &lt;code&gt;dinput8&lt;/code&gt; is what a large share of mods hook into.&lt;/p&gt;

&lt;h2&gt;
  
  
  When something won't launch
&lt;/h2&gt;

&lt;p&gt;Working order, cheapest first:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Permissions&lt;/strong&gt;, if you're on Flatpak. It's the most common cause and the easiest to miss.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Switch the runner.&lt;/strong&gt; Settings, Components, Runner. Soda is the default, but a different Proton or Wine build ships different patches, DXVK versions and game-specific fixes. &lt;a href="https://github.com/DavidoTek/ProtonUp-Qt" rel="noopener noreferrer"&gt;ProtonUp-Qt&lt;/a&gt; installs GE-Proton into Bottles the same way it does for Steam.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DLL overrides&lt;/strong&gt;, as above.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://www.protondb.com/" rel="noopener noreferrer"&gt;ProtonDB&lt;/a&gt;&lt;/strong&gt;, for anything game-specific other people already solved.
And restart Bottles fully after changing permissions or runners. Some changes don't take effect until you do.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What this doesn't fix
&lt;/h2&gt;

&lt;p&gt;Kernel-level anti-cheat. Valorant, Call of Duty and similar titles won't run through Bottles, Proton, or anything else, because the studios haven't enabled Linux support in their anti-cheat. That's a decision, not a technical wall, but it's not one you can work around from your end.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full walkthrough
&lt;/h2&gt;

&lt;p&gt;Everything above with screenshots of each step, the Flatseal settings in detail, Epic sign-in, the GOG notes and a longer FAQ is on my site: &lt;a href="https://www.musabase.com/2026/02/run-non-steam-games-on-arch-linux-bottles.html" rel="noopener noreferrer"&gt;Run Non-Steam Games on Arch Linux with Bottles&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It's part 2 of a series. &lt;a href="https://www.musabase.com/2026/01/run-windows-games-on-linux-using-steam-proton.html" rel="noopener noreferrer"&gt;Part 1 covers Steam and Proton&lt;/a&gt;, &lt;a href="https://www.musabase.com/2026/03/windows-games-on-arch-linux-with-wine.html" rel="noopener noreferrer"&gt;part 3 goes into plain Wine&lt;/a&gt;, and the &lt;a href="https://www.musabase.com/p/linux-gaming-roadmap-complete-musabase.html" rel="noopener noreferrer"&gt;Linux Gaming Roadmap&lt;/a&gt; indexes the lot.&lt;/p&gt;

&lt;p&gt;If you went the Flatpak route and hit something I didn't, especially on NVIDIA, I'd like to hear it in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/02/run-non-steam-games-on-arch-linux-bottles.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>archlinux</category>
      <category>flatpak</category>
    </item>
    <item>
      <title>I benchmarked Steam's bundled runtime against the native one on Arch, and the native build lost</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Wed, 28 Oct 2026 10:18:26 +0000</pubDate>
      <link>https://dev.to/retro-1o1/i-benchmarked-steams-bundled-runtime-against-the-native-one-on-arch-and-the-native-build-lost-4g8</link>
      <guid>https://dev.to/retro-1o1/i-benchmarked-steams-bundled-runtime-against-the-native-one-on-arch-and-the-native-build-lost-4g8</guid>
      <description>&lt;p&gt;Getting Windows games running on Arch Linux through Steam and Proton is a handful of commands. The part that actually decides whether a game is playable is which Steam runtime you launch, and almost nobody benchmarks that.&lt;/p&gt;

&lt;p&gt;So I did. Same four games, same settings, same Proton versions, launched once under Valve's bundled runtime and once under the native one. The results were not what I expected going in.&lt;/p&gt;

&lt;p&gt;Tested on: Arch Linux, KDE Plasma 6.5.5 on Wayland, kernel 6.18.6-arch1-1, Intel Core i5-4460, AMD Radeon RX 580 8GB on amdgpu with Mesa, 16GB DDR3. That's one machine, so treat the numbers as "works for me" until you've tried it yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup, in four commands
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Enable multilib.&lt;/strong&gt; Steam needs 32-bit libraries. Uncomment these two lines in &lt;code&gt;/etc/pacman.conf&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[multilib]
include = /etc/pacman.d/mirrorlist
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then sync:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pacman &lt;span class="nt"&gt;-Syu&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Skip this and Steam dies on launch with a wall of missing 32-bit library errors.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Install Steam and ProtonUp-Qt.&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;yay &lt;span class="nt"&gt;-S&lt;/span&gt; steam
yay &lt;span class="nt"&gt;-S&lt;/span&gt; protonup-qt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;3. Optionally install the native runtime,&lt;/strong&gt; which is the thing I tested against. It's deprecated, which is worth knowing before you build a setup around it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;yay &lt;span class="nt"&gt;-S&lt;/span&gt; steam-native-runtime
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;4. Launch it.&lt;/strong&gt; Plain &lt;code&gt;steam&lt;/code&gt; uses Valve's bundled runtime. The environment variable picks the other one:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;steam
&lt;span class="nv"&gt;STEAM_RUNTIME&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0 steam
&lt;span class="nv"&gt;STEAM_RUNTIME&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;1 steam
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To confirm which one you're actually on, check Steam's Help, System Information. The bundled runtime reports a version string like &lt;code&gt;steam-runtime_1.0.20251202.187498&lt;/code&gt;. The native one reports &lt;code&gt;&amp;lt;Runtime disabled&amp;gt;&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Proton, briefly
&lt;/h2&gt;

&lt;p&gt;Steam ships Proton Experimental, Sniper and Legacy. For anything they won't run, GE-Proton is the community build, installed through ProtonUp-Qt with Steam fully closed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;protonup-qt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then per game: Properties, Compatibility, tick "Force the use of a specific Steam Play compatibility tool", pick your version.&lt;/p&gt;

&lt;p&gt;Check &lt;a href="https://www.protondb.com/" rel="noopener noreferrer"&gt;ProtonDB&lt;/a&gt; before you launch anything. It's where you find both the Proton version other people got working and the launch options that fixed their crashes. That's where mine came from:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mangohud RADV_TEX_ANISO=0 PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1 ENABLE_HDR_WSI=1 %command%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's Red Dead Redemption 2 on GE-Proton 10.27. Forza Horizon 5 needed a DLL override instead:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mangohud WINEDLLOVERRIDES="winmm=n,b" %command%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And GTA V Enhanced, on GE-Proton 10.25:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mangohud WINEDLLOVERRIDES="socialclub=n,b;version=n,b" %command%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  The runtime results
&lt;/h2&gt;

&lt;p&gt;Here's the part worth the post.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Dota 2&lt;/strong&gt;, which runs natively on Linux: the native runtime was smoother in team fights. That one makes sense. Native game, native libraries, no translation layer in the way.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk0ofrcmgpg1v2kucro5l.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk0ofrcmgpg1v2kucro5l.webp" alt="Dota 2 running natively on Arch Linux" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Red Dead Redemption 2&lt;/strong&gt; through Proton: standard Steam was more predictable. 60 to 75 FPS in open areas, dropping to the mid 30s in crowded ones.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnps1p4fe84vqrxzkj388.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnps1p4fe84vqrxzkj388.webp" alt="Red Dead Redemption 2 running on Arch Linux" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Forza Horizon 5&lt;/strong&gt; through Proton: standard Steam held a steady 60. The native runtime swung between 35 and 60 on the same settings.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjb6xjrbxziwiuhmaag5q.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjb6xjrbxziwiuhmaag5q.webp" alt="Forza Horizon 5 running on Arch Linux" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GTA V Enhanced&lt;/strong&gt; through Proton on GE-Proton 10.25: both runtimes sat at a stable 60+, and the native one actually posted a slightly higher average.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fykaut4syxi3i6vypa3s7.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fykaut4syxi3i6vypa3s7.webp" alt="Gta V Enhanced running on Arch Linux" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So the honest answer is not the one I expected. Three of the four games either didn't care or mildly preferred the native runtime. Forza was the outlier, and it was a big one: same hardware, same Proton build, same graphics settings, with the runtime as the only variable, and the frame rate floor dropped by nearly half.&lt;/p&gt;

&lt;p&gt;That's the thing worth knowing. Not "always use runtime X", but that the runtime is a variable that can quietly cost you 25 FPS in a specific game while doing nothing at all in the other three. If a game runs worse than ProtonDB says it should and you've already tried the obvious fixes, switch runtimes before you start blaming your GPU.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My default is standard Steam&lt;/strong&gt;, because it's the supported path and it never lost badly in my testing. I keep the native runtime installed to test against when a game misbehaves. Worth knowing before you build around it: &lt;code&gt;steam-native-runtime&lt;/code&gt; is deprecated.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full guide
&lt;/h2&gt;

&lt;p&gt;The complete walkthrough on my site has the per-game settings, the full comparison tables including GTA V Enhanced, screenshots of every step, the common mistakes section and an FAQ: &lt;a href="https://www.musabase.com/2026/01/run-windows-games-on-linux-using-steam-proton.html" rel="noopener noreferrer"&gt;Windows Games on Arch Linux (Part 1): Steam, Proton and ProtonUp-Qt Setup&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It's part of a series. &lt;a href="https://www.musabase.com/2026/08/protonup-qt-and-ge-proton-on-arch-linux.html" rel="noopener noreferrer"&gt;ProtonUp-Qt and GE-Proton&lt;/a&gt; goes deep on custom Proton builds, &lt;a href="https://www.musabase.com/2026/02/run-non-steam-games-on-arch-linux-bottles.html" rel="noopener noreferrer"&gt;Bottles&lt;/a&gt; covers non-Steam games, &lt;a href="https://www.musabase.com/2026/03/windows-games-on-arch-linux-with-wine.html" rel="noopener noreferrer"&gt;Wine&lt;/a&gt; covers the layer underneath all of it, and the whole thing starts at the &lt;a href="https://www.musabase.com/p/linux-gaming-roadmap-complete-musabase.html" rel="noopener noreferrer"&gt;Linux Gaming Roadmap&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;One machine, four games, one GPU vendor. If you've tested the two runtimes on Nvidia or on newer AMD hardware and got different results, I'd genuinely like to hear it in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/01/run-windows-games-on-linux-using-steam-proton.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>gaming</category>
      <category>archlinux</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Installing Omarchy 4 on a partition you choose, without shrinking Windows or wiping a disk</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Sun, 25 Oct 2026 13:44:00 +0000</pubDate>
      <link>https://dev.to/retro-1o1/installing-omarchy-4-on-a-partition-you-choose-without-shrinking-windows-or-wiping-a-disk-39dl</link>
      <guid>https://dev.to/retro-1o1/installing-omarchy-4-on-a-partition-you-choose-without-shrinking-windows-or-wiping-a-disk-39dl</guid>
      <description>&lt;p&gt;Omarchy 4 (Quattro) installs from its ISO. It either takes a whole drive, or, for dual booting, installs into unallocated space on the disk you pick, which on a single-disk Windows machine means shrinking Windows first.&lt;/p&gt;

&lt;p&gt;I already had my own layout, with Arch Linux on a partition I set up myself, and I wanted Omarchy there. The old manual route, curl -fsSL &lt;a href="https://omarchy.org/install" rel="noopener noreferrer"&gt;https://omarchy.org/install&lt;/a&gt; | bash, now returns a 404. So I went the long way round: install Omarchy 3.8.4 on top of Arch, then upgrade it to Omarchy 4 with Omarchy's own upgrade script.&lt;/p&gt;

&lt;p&gt;This post covers the route and the commands that matter. The full walkthrough, with the Snapper fix, screenshots of every step and the troubleshooting, is on my site, linked at the end.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhpgynbdxvkdtdvysj3bw.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhpgynbdxvkdtdvysj3bw.webp" alt="Omarchy 4 Quattor manually installed proof" width="799" height="412"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Tested in October 2026: Omarchy 3.8.4 upgraded to Omarchy 4, with Windows 10 on its own disk and both booting from Limine.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5gg6x9v902tv23sts4rp.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5gg6x9v902tv23sts4rp.webp" alt="Proof of Omarchy and Windows installed on 2 separate partitions" width="799" height="412"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Arch Linux on Btrfs&lt;/strong&gt;, on the partition you want Omarchy on, booting with GRUB. Btrfs is required: the Omarchy 4 upgrade sets up Snapper snapshots, which need it. A traditional ext4 install won't work for this.&lt;/li&gt;
&lt;li&gt;A regular user with sudo rights. Run everything from tty1 as that user, not as root.&lt;/li&gt;
&lt;li&gt;At least 40 GB on that partition. My test install already uses about 25 GB.&lt;/li&gt;
&lt;li&gt;A backup. The upgrade to Quattro is one-way, and its own script says you cannot downgrade.
## Why go through Omarchy 3.8.4?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In October 2026, upstream removed its &lt;code&gt;master&lt;/code&gt; branch, the &lt;code&gt;omarchy.org/install&lt;/code&gt; script started returning a 404, and the &lt;code&gt;omarchy-walker&lt;/code&gt; package was retired. Together those broke every manual 3.x install.&lt;/p&gt;

&lt;p&gt;So I made &lt;a href="https://github.com/musabase/omarchy-legacy" rel="noopener noreferrer"&gt;omarchy-legacy&lt;/a&gt;: a snapshot of upstream's v3.8.4 installer with the smallest set of changes needed to make it install again. It swaps the retired walker package for &lt;code&gt;walker&lt;/code&gt;, skips the Elephant setup that no longer installs, and stops the installer from aborting when Limine isn't present. The README lists every changed file, so you can check the diff before you run anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  The route
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Install Omarchy 3.8.4.&lt;/strong&gt; On tty1, as your normal user:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ~
curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://raw.githubusercontent.com/musabase/omarchy-legacy/legacy-3.8.4/boot.sh | bash
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The installer warns that it requires the Limine bootloader. Answer Yes to "Proceed anyway". Your system keeps booting with GRUB for now, and Limine arrives with the upgrade. If the install stops on an error, choose Retry installation. Don't rerun the curl command, because &lt;code&gt;boot.sh&lt;/code&gt; deletes &lt;code&gt;~/.local/share/omarchy&lt;/code&gt; and clones it again from scratch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Boot into Omarchy 3.8.4.&lt;/strong&gt; Pick the Arch entry in GRUB, open a terminal with Super+Enter, and confirm the install came from the legacy branch:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git &lt;span class="nt"&gt;-C&lt;/span&gt; ~/.local/share/omarchy log &lt;span class="nt"&gt;--oneline&lt;/span&gt; &lt;span class="nt"&gt;-1&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It should print a commit ending in &lt;code&gt;Keep the 3.8.4 installer working after upstream changes&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Check Snapper before upgrading.&lt;/strong&gt; Run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;findmnt /.snapshots
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If it prints a line, you already have a &lt;code&gt;.snapshots&lt;/code&gt; subvolume, and the upgrade's Snapper setup will fail until you swap it out first. &lt;a href="https://www.musabase.com/2026/06/install-omarchy-os-manually-separate-partition.html#prepare-quattro-upgrade" rel="noopener noreferrer"&gt;The fix is in the full guide&lt;/a&gt;. If it prints nothing, move on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Upgrade to Omarchy 4 (Quattro).&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; ~
curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-upgrade-to-quattro &lt;span class="nt"&gt;-o&lt;/span&gt; upgrade-to-quattro
bash upgrade-to-quattro
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiwptz7b0n7up4fcpu9bi.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiwptz7b0n7up4fcpu9bi.webp" alt="Upgrading Omarchy 3 to Omarchy 4 Quattro manually" width="800" height="406"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It installs Omarchy 4, Limine and Snapper, and swaps iwd for NetworkManager. Don't reboot if it says "Upgrade incomplete - do NOT reboot" or warns that &lt;code&gt;root=&lt;/code&gt; is missing. Otherwise, answer Yes to the reboot prompt. From here on, Limine is your bootloader, so don't run &lt;code&gt;grub-mkconfig&lt;/code&gt; again.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F04pgxhtkkf2ztjfhl2b6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F04pgxhtkkf2ztjfhl2b6.webp" alt="Omarchy 4 manually installed" width="800" height="406"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Add Windows to Limine.&lt;/strong&gt; After the reboot, the Limine menu replaces GRUB. In Omarchy 4:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;limine-scan
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Type the number of Windows Boot Manager and press Enter. Windows shows up in the Limine menu on the next boot. You don't need os-prober for this.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things to know before you start
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One way only.&lt;/strong&gt; There's no going back to Omarchy 3 after the upgrade.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The launcher on 3.8.4.&lt;/strong&gt; Super+Space may not fully work on 3.8.4, because its Elephant backend is gone. It doesn't affect the upgrade.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;BitLocker.&lt;/strong&gt; If Windows has device encryption on, booting it from Limine may ask for your recovery key the first time. The guide covers this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;If upstream moves the upgrade script.&lt;/strong&gt; The repo keeps an unmodified copy of it, pinned to the upstream commit I tested with, as a fallback.
## The full guide&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://www.musabase.com/2026/06/install-omarchy-os-manually-separate-partition.html" rel="noopener noreferrer"&gt;full guide on my site&lt;/a&gt; has the Snapper fix commands, screenshots of each step, GParted proof that Windows' disk is left untouched, BitLocker and boot-order notes, and an FAQ. The installer is in the &lt;a href="https://github.com/musabase/omarchy-legacy" rel="noopener noreferrer"&gt;omarchy-legacy repo&lt;/a&gt;. If you'd rather install Omarchy the official way, start with my &lt;a href="https://www.musabase.com/2026/05/how-to-install-omarchy-os.html" rel="noopener noreferrer"&gt;Omarchy OS installation guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;omarchy-legacy is unofficial and not affiliated with Omarchy, DHH or Basecamp. I wrote both the repo and the guide, so weigh my testing with that in mind. If something breaks, leave a comment or open an issue on the repo with a screenshot and I'll take a look.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/06/install-omarchy-os-manually-separate-partition.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>omarchy</category>
      <category>archlinux</category>
      <category>linux</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Caelestia only ships an Arch installer, so I wrote the NixOS version with a flake and Home Manager</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Sat, 24 Oct 2026 10:43:56 +0000</pubDate>
      <link>https://dev.to/retro-1o1/caelestia-only-ships-an-arch-installer-so-i-wrote-the-nixos-version-with-a-flake-and-home-manager-2e6o</link>
      <guid>https://dev.to/retro-1o1/caelestia-only-ships-an-arch-installer-so-i-wrote-the-nixos-version-with-a-flake-and-home-manager-2e6o</guid>
      <description>&lt;p&gt;Caelestia is a Hyprland setup with its own shell and a small CLI for wallpapers and color schemes. Its official installer only targets Arch Linux, and NixOS has no AUR, so there is nothing to run.&lt;/p&gt;

&lt;p&gt;I set it up by hand instead: a flake that pulls Caelestia's shell and CLI from the upstream repos, plus a Home Manager config that puts the dotfiles in place. This post walks through the pieces and the steps that matter. The complete files, screenshots and the full walkthrough are on my site, linked at the end.&lt;/p&gt;

&lt;p&gt;Tested on: a base NixOS install with Budgie and LightDM as the starting desktop, built against &lt;code&gt;nixos-unstable&lt;/code&gt;. Treat it as "works for me" until you've tried it on yours.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7ln1wn31fedfqrp8m3y6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7ln1wn31fedfqrp8m3y6.webp" alt="Caelestia dots running on NixOS" width="800" height="457"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A base NixOS install. I started from Budgie with LightDM.&lt;/li&gt;
&lt;li&gt;x86-64 CPU, 8 GB RAM minimum, and a 30 GB root partition or more. Caelestia itself takes about 15 GB.&lt;/li&gt;
&lt;li&gt;A GPU from 2015 or newer.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A stable connection. The first build compiles quickshell from source.&lt;/p&gt;
&lt;h2&gt;
  
  
  The three files
&lt;/h2&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;&lt;code&gt;flake.nix&lt;/code&gt;&lt;/strong&gt; (new, in &lt;code&gt;/etc/nixos&lt;/code&gt;): the inputs are nixpkgs on unstable, Home Manager, and Caelestia's shell and CLI taken straight from the &lt;code&gt;caelestia-dots&lt;/code&gt; GitHub org. It defines one system that loads your &lt;code&gt;configuration.nix&lt;/code&gt; and your Home Manager user.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;&lt;code&gt;configuration.nix&lt;/code&gt;&lt;/strong&gt; (your existing file, with additions): Hyprland with XWayland, the GTK desktop portal, polkit, GNOME Keyring, the fonts (JetBrains Mono and Caskaydia Cove Nerd Fonts, Material Symbols, Rubik, Noto), and the tools Caelestia leans on, such as foot, fish, Thunar, starship, fastfetch, btop, micro and a set of clipboard and screenshot utilities.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;&lt;code&gt;home.nix&lt;/code&gt;&lt;/strong&gt; (new, in &lt;code&gt;/etc/nixos&lt;/code&gt;): enables Caelestia's Home Manager module together with its CLI, clones the &lt;code&gt;caelestia-dots/caelestia&lt;/code&gt; repo once into &lt;code&gt;~/.local/share/caelestia-dots&lt;/code&gt;, and links its config folders (hypr, fish, foot, fastfetch, btop, micro, Thunar, starship) into &lt;code&gt;~/.config&lt;/code&gt;. The links point outside the Nix store, so you can edit the dotfiles live without rebuilding.&lt;br&gt;
Your username sits in both &lt;code&gt;flake.nix&lt;/code&gt; and &lt;code&gt;home.nix&lt;/code&gt;, and &lt;code&gt;home.nix&lt;/code&gt; also needs your state version.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Get the three files:&lt;/strong&gt; &lt;a href="https://www.musabase.com/2026/09/install-caelestia-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;copy them from the full guide on MusaBase&lt;/a&gt;. I'm not pasting them here.&lt;/p&gt;

&lt;h2&gt;
  
  
  The steps
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Enable flakes.&lt;/strong&gt; Skip this if you already have them. Add this line to &lt;code&gt;/etc/nixos/configuration.nix&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nix"&gt;&lt;code&gt;&lt;span class="nv"&gt;nix&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nv"&gt;settings&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="nv"&gt;experimental-features&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"nix-command"&lt;/span&gt; &lt;span class="s2"&gt;"flakes"&lt;/span&gt; &lt;span class="p"&gt;];&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then rebuild once, without &lt;code&gt;--flake&lt;/code&gt; for now:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;nixos-rebuild switch
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;2. Look up your details.&lt;/strong&gt; You need these for the two files that hold your user:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;whoami
grep &lt;/span&gt;stateVersion /etc/nixos/configuration.nix
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;3. Create the three files.&lt;/strong&gt; Take them from the &lt;a href="https://www.musabase.com/2026/09/install-caelestia-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;guide&lt;/a&gt;. Add &lt;code&gt;flake.nix&lt;/code&gt; and &lt;code&gt;home.nix&lt;/code&gt; to &lt;code&gt;/etc/nixos&lt;/code&gt;, then add the Caelestia section to your existing &lt;code&gt;configuration.nix&lt;/code&gt;. Put your username and state version in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Rebuild against the flake.&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; /etc/nixos
&lt;span class="nb"&gt;sudo &lt;/span&gt;nix-shell &lt;span class="nt"&gt;-p&lt;/span&gt; git &lt;span class="nt"&gt;--run&lt;/span&gt; &lt;span class="s2"&gt;"nixos-rebuild switch --flake .#nixos"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;nix-shell&lt;/code&gt; wrapper puts git on the path for the build, in case it isn't installed yet. Expect 10 to 25 minutes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Reboot and log in.&lt;/strong&gt; Pick Hyprland from your login manager's session list.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Set the color scheme.&lt;/strong&gt; To have it follow your wallpaper:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;caelestia scheme &lt;span class="nb"&gt;set&lt;/span&gt; &lt;span class="nt"&gt;-n&lt;/span&gt; dynamic
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or lock it to one wallpaper:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;caelestia wallpaper &lt;span class="nt"&gt;-f&lt;/span&gt; path_to_wallpaper
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1dvwlodde6bvwtx34m2i.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1dvwlodde6bvwtx34m2i.png" alt="Caelestia dotfiles home screen on NixOS" width="800" height="455"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What was tricky
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;No installer to lean on.&lt;/strong&gt; The official route is Arch-only, so every dependency has to come from the flake inputs or nixpkgs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Upstream names can move.&lt;/strong&gt; The flake tracks Caelestia's repos without a pinned revision. If the shell, the CLI or the Home Manager module path gets renamed, the flake stops evaluating. Check the current upstream layout before assuming your own config is wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Editable dotfiles on a read-only store.&lt;/strong&gt; Caelestia expects to be edited live, so the dotfiles are cloned once and symlinked from outside the Nix store instead of being copied in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Updating and going back
&lt;/h2&gt;

&lt;p&gt;To pull newer dotfiles, run &lt;code&gt;git pull&lt;/code&gt; inside &lt;code&gt;~/.local/share/caelestia-dots&lt;/code&gt; and rebuild. Updates can change the file layout, so look at what changed first.&lt;/p&gt;

&lt;p&gt;Every rebuild creates a new generation. If something breaks, pick the previous one from the boot menu.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full guide
&lt;/h2&gt;

&lt;p&gt;The full guide on my site has the complete files to copy, screenshots of each step and the FAQ: &lt;a href="https://www.musabase.com/2026/09/install-caelestia-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;How to Install Caelestia Hyprland Dotfiles on NixOS&lt;/a&gt;. The repo is &lt;a href="https://github.com/musabase/caelestia-dots-nixos" rel="noopener noreferrer"&gt;caelestia-dots-nixos&lt;/a&gt;. If you want to compare it with other setups, I also wrote up &lt;a href="https://www.musabase.com/2026/10/install-end-4-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;End-4's dotfiles on NixOS&lt;/a&gt;, and the series starts at &lt;a href="https://www.musabase.com/p/best-hyprland-dotfiles-for-linux.html" rel="noopener noreferrer"&gt;Best Hyprland Dotfiles 2026&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I wrote both the config and the site linked above, so weigh my testing with that in mind. If something breaks for you, leave a comment or open an issue on the repo with the first &lt;code&gt;error&lt;/code&gt; line from the rebuild and I'll take a look.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/09/install-caelestia-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>nixos</category>
      <category>linux</category>
      <category>hyprland</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How I run End-4's Hyprland dotfiles on NixOS with flakes and Home Manager</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Fri, 23 Oct 2026 11:28:09 +0000</pubDate>
      <link>https://dev.to/retro-1o1/how-i-run-end-4s-hyprland-dotfiles-on-nixos-with-flakes-and-home-manager-l6e</link>
      <guid>https://dev.to/retro-1o1/how-i-run-end-4s-hyprland-dotfiles-on-nixos-with-flakes-and-home-manager-l6e</guid>
      <description>&lt;p&gt;End-4's illogical-impulse (the Quickshell-based Hyprland setup, repo name &lt;code&gt;dots-hyprland&lt;/code&gt;) ships installers for Arch, Fedora and Gentoo. NixOS isn't on that list. The project's own Nix-based installer is aimed at other distros, not NixOS.&lt;/p&gt;

&lt;p&gt;I wanted it on NixOS anyway, so I wrote a flake plus Home Manager config for it. It's three files. This post gives you the files and explains how they fit together. The full walkthrough, with every command and screenshot, is on my site, linked at the end.&lt;/p&gt;

&lt;p&gt;Tested on: NixOS unstable (26.11.20261015), starting from a Budgie install, with End-4 at commit &lt;code&gt;2f2a376&lt;/code&gt; and QuickShell at &lt;code&gt;4f508be&lt;/code&gt;, October 2026. That is one VM, so treat it as "works for me" until you've tried it yourself.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsy4b91cwwuoj3spbpg4u.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsy4b91cwwuoj3spbpg4u.webp" alt="End4 dotfiles running on NixOS" width="800" height="404"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A base NixOS install. I used Budgie as the starting desktop, but any works.&lt;/li&gt;
&lt;li&gt;x86-64 CPU, 8 GB RAM minimum, and about 45 GB for the root partition.&lt;/li&gt;
&lt;li&gt;Hyprland 0.55 or newer. End-4's current config needs it, and the flake follows &lt;code&gt;nixos-unstable&lt;/code&gt;, which ships a recent enough version.&lt;/li&gt;
&lt;li&gt;A stable connection. The build compiles QuickShell from source.
## Get the files&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All three go in &lt;code&gt;/etc/nixos&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; /etc/nixos
&lt;span class="nb"&gt;sudo &lt;/span&gt;curl &lt;span class="nt"&gt;-fLO&lt;/span&gt; https://raw.githubusercontent.com/musabase/end4-hyprland-nixos/main/flake.nix
&lt;span class="nb"&gt;sudo &lt;/span&gt;curl &lt;span class="nt"&gt;-fLO&lt;/span&gt; https://raw.githubusercontent.com/musabase/end4-hyprland-nixos/main/end4.nix
&lt;span class="nb"&gt;sudo &lt;/span&gt;curl &lt;span class="nt"&gt;-fLO&lt;/span&gt; https://raw.githubusercontent.com/musabase/end4-hyprland-nixos/main/end4-home.nix
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read them before you build anything. They configure your whole system and the rebuild runs as root, so don't take my word for what's in them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the three files do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;flake.nix&lt;/code&gt;&lt;/strong&gt;: the inputs (nixpkgs unstable, Home Manager, and a pinned QuickShell commit) and the system definition that pulls in the other two files. It also holds my username, which you'll need to replace with yours.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;end4.nix&lt;/code&gt;&lt;/strong&gt;: system level. Hyprland and its portals, audio, Bluetooth, networking, authentication, Qt integration, fonts, and the packages End-4's interface depends on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;end4-home.nix&lt;/code&gt;&lt;/strong&gt;: user level, through Home Manager. QuickShell with the Qt/QML modules it needs, the Python packages End-4's scripts import, a clone of the original dotfiles repo, and symlinks from its config folders into &lt;code&gt;~/.config&lt;/code&gt;.
## Building it&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Flakes need to be enabled on your system first. After that, open &lt;code&gt;flake.nix&lt;/code&gt;, replace my hardcoded username with your own, and rebuild NixOS against the flake. The first build compiles QuickShell and took about 20 minutes on my machine. When it finishes, reboot and pick Hyprland from your login manager's session list.&lt;/p&gt;

&lt;p&gt;The exact commands, how to confirm the build worked, and what to do if it looks stuck are in the full guide.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbvawyrlzivw19o1uy1al.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbvawyrlzivw19o1uy1al.webp" alt="Rebuilding NixOS after adding End4 dotfiles" width="800" height="404"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Keeping it from breaking
&lt;/h2&gt;

&lt;p&gt;End-4's repo moves fast, and a NixOS port that tracks &lt;code&gt;main&lt;/code&gt; blindly will break the first time something changes upstream. So I pin two things: the dotfiles are cloned at a specific commit, and QuickShell is pinned to the commit End-4's own Arch package uses.&lt;/p&gt;

&lt;p&gt;A GitHub Action checks End-4's repo every week. When something changed, it bumps both pins together and opens a draft pull request. It also evaluates the NixOS config on a stub host, so a bump that doesn't evaluate fails in CI instead of on my machine. I still test each update on a fresh NixOS install before merging.&lt;/p&gt;

&lt;p&gt;The pin only applies to fresh installs, so updating an existing install has one extra manual step. That's covered in the full guide too.&lt;/p&gt;

&lt;h2&gt;
  
  
  What doesn't work
&lt;/h2&gt;

&lt;p&gt;Two packages from End-4's Arch list are missing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;MicroTeX&lt;/strong&gt;, so LaTeX formulas in the AI sidebar won't render.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Breeze Plus icon theme.&lt;/strong&gt;
Neither is in nixpkgs. I checked with &lt;code&gt;nix search&lt;/code&gt; on nixos-unstable in October 2026 and it finds neither. End-4's own Nix installer lists both as TODO for the same reason.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The full guide
&lt;/h2&gt;

&lt;p&gt;The full guide on my site has the exact build commands, screenshots, how to check the build, updating, uninstalling, the keybinds and an FAQ: &lt;a href="https://www.musabase.com/2026/10/install-end-4-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;How to Install End-4 (illogical-impulse) on NixOS&lt;/a&gt;. The files are in the &lt;a href="https://github.com/musabase/end4-hyprland-nixos" rel="noopener noreferrer"&gt;end4-hyprland-nixos repo&lt;/a&gt;. If you're on Arch instead, End-4's official installer does everything and I wrote that up &lt;a href="https://www.musabase.com/2025/10/how-to-install-end-4-hyprland-dotfiles-on-arch-linux.html" rel="noopener noreferrer"&gt;here&lt;/a&gt;. It's part of a series comparing Hyprland dotfiles, which starts at &lt;a href="https://www.musabase.com/p/best-hyprland-dotfiles-for-linux.html" rel="noopener noreferrer"&gt;Best Hyprland Dotfiles 2026&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I wrote both the config and the site linked above, so weigh my testing with that in mind. If something breaks for you, open an issue on the repo with the first &lt;code&gt;error&lt;/code&gt; line from the build and I'll take a look.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.musabase.com/2026/10/install-end-4-hyprland-dotfiles-on-nixos.html" rel="noopener noreferrer"&gt;MusaBase&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>nixos</category>
      <category>linux</category>
      <category>hyprland</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Windows Is Secretly Hiding a Full Linux Desktop (WSL2 Guide)</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Sun, 03 May 2026 23:14:20 +0000</pubDate>
      <link>https://dev.to/retro-1o1/run-a-full-linux-desktop-on-windows-without-dual-booting-wsl2-guide-4504</link>
      <guid>https://dev.to/retro-1o1/run-a-full-linux-desktop-on-windows-without-dual-booting-wsl2-guide-4504</guid>
      <description>&lt;p&gt;For years I thought my only options were dual booting or using a clunky virtual machine. Dual boot meant constant reboots, and VirtualBox ate my RAM. Then I discovered Windows Subsystem for Linux 2, and honestly it changed how I work.&lt;/p&gt;

&lt;p&gt;Now I run a complete Ubuntu desktop right next to my Windows applications. I can code in a native Linux environment, test web servers, and even fire up Linux-only GUI tools without ever leaving my main OS. Let me walk you through why WSL matters and how to set it up, including a full desktop environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Do We Need WSL on Windows?
&lt;/h2&gt;

&lt;p&gt;WSL isn’t just a novelty. It solves real problems for developers and tinkerers.&lt;/p&gt;

&lt;p&gt;First, a lot of modern development tooling assumes you’re on Linux. Servers run Linux. CI/CD pipelines run Linux. Containers are built on Linux kernel features. On plain Windows you’re constantly fighting path differences, missing packages, and subtle bugs that don’t appear in production. WSL gives you an actual Linux kernel running inside Windows, so your local environment matches your deployment target.&lt;/p&gt;

&lt;p&gt;Second, performance. WSL1 used a translation layer that worked but got slow with heavy file operations. WSL2 runs a lightweight virtual machine with a real Linux kernel. I saw my &lt;strong&gt;npm install&lt;/strong&gt; times drop significantly after switching. It also supports systemd, Docker, and even GPU acceleration for machine learning tasks. You get the speed of bare metal without the resource overhead of VirtualBox.&lt;/p&gt;

&lt;p&gt;Third, it’s seamless. You can access your Windows files from Linux and vice versa. You can run VS Code on Windows with a remote connection to your WSL instance. You can copy files between the two with a simple &lt;strong&gt;/mnt/c/&lt;/strong&gt; path. No shared folders to configure, no network bridges to set up.&lt;/p&gt;

&lt;p&gt;And if you add a desktop environment, you gain a visual workspace for things like GIMP, Krita, or browser testing, all integrated neatly into your Windows desktop. It’s the best of both worlds, and once you use it, going back feels like a step backward.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting WSL2 Up and Running
&lt;/h2&gt;

&lt;p&gt;The installation is almost too easy now. On &lt;strong&gt;Windows 10 version 2004 or later&lt;/strong&gt;, or Windows 11, you need just a couple of commands.&lt;/p&gt;

&lt;p&gt;First, enable the necessary Windows features. Open PowerShell as Administrator and run these two lines. They turn on the subsystem and the virtual machine platform.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight batchfile"&gt;&lt;code&gt;&lt;span class="nb"&gt;dism.exe&lt;/span&gt; &lt;span class="na"&gt;/online /enable-feature /featurename&lt;/span&gt;&lt;span class="nl"&gt;:Microsoft&lt;/span&gt;&lt;span class="na"&gt;-Windows-Subsystem-Linux /all /norestart
&lt;/span&gt;&lt;span class="nb"&gt;dism.exe&lt;/span&gt; &lt;span class="na"&gt;/online /enable-feature /featurename&lt;/span&gt;&lt;span class="nl"&gt;:VirtualMachinePlatform&lt;/span&gt; &lt;span class="na"&gt;/all /noresta
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5zbg04v7e9pz6x1i5yyf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5zbg04v7e9pz6x1i5yyf.png" alt="Enabling WSL features from Powershell on Windows 11" width="800" height="416"&gt;&lt;/a&gt;&lt;br&gt;
Restart your PC. Then open PowerShell as Admin again and type:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight batchfile"&gt;&lt;code&gt;&lt;span class="kd"&gt;wsl&lt;/span&gt; &lt;span class="na"&gt;--install
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That’s it. This one command downloads the Linux kernel, sets WSL2 as your default, and installs Ubuntu. After another reboot, you’ll find an Ubuntu shortcut in your Start menu. Launch it and you’ll be asked to create a username and password. You’re now inside a minimal Ubuntu terminal running on Windows.&lt;/p&gt;

&lt;p&gt;From here you can run &lt;strong&gt;sudo apt update&lt;/strong&gt; and install any CLI tool you like. But what if you want a graphical desktop?&lt;/p&gt;

&lt;h2&gt;
  
  
  Adding a Full Desktop Environment
&lt;/h2&gt;

&lt;p&gt;WSL2 is &lt;strong&gt;headless&lt;/strong&gt; by default. It has no display server, so GUI apps can’t draw anything. We can solve that by using an &lt;strong&gt;X server on Windows&lt;/strong&gt;.&lt;br&gt;
I prefer this approach because Linux apps appear as normal windows on your desktop. You need an X server for Windows; I use VcXsrv, which is free and reliable.&lt;/p&gt;

&lt;p&gt;First, inside your Ubuntu terminal, install the GNOME desktop.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt update
&lt;span class="nb"&gt;sudo &lt;/span&gt;apt &lt;span class="nb"&gt;install &lt;/span&gt;ubuntu-desktop gnome
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now comes a critical fix most guides skip. The &lt;strong&gt;acpid&lt;/strong&gt; package handles ACPI events like power button presses. WSL2 doesn’t have that hardware, so if acpid gets installed or upgraded later, it will flood your logs with errors and crash the desktop session. Hold it so it never gets installed.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;apt-mark hold acpid
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Next, enable systemd. Edit the WSL config file with &lt;strong&gt;sudo nano /etc/wsl.conf&lt;/strong&gt; and add:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="nn"&gt;[boot]&lt;/span&gt;
&lt;span class="py"&gt;systemd&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;true&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9qnpqfxfntf41rojhjya.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9qnpqfxfntf41rojhjya.png" alt="Enabling Systemd for Desktop session on WSL on Windows 11" width="800" height="455"&gt;&lt;/a&gt;&lt;br&gt;
Save and exit. Then shut down WSL from PowerShell using &lt;strong&gt;wsl --shutdown&lt;/strong&gt; so the change applies.&lt;/p&gt;

&lt;p&gt;We also need to create a runtime directory for user services and point the DISPLAY variable to our X server. Add these lines to your &lt;strong&gt;~/.bashrc&lt;/strong&gt; file.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;export &lt;/span&gt;&lt;span class="nv"&gt;DISPLAY&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="si"&gt;$(&lt;/span&gt;ip route | &lt;span class="nb"&gt;awk&lt;/span&gt; &lt;span class="s1"&gt;'{print $3; exit}'&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;:0
&lt;span class="nb"&gt;export &lt;/span&gt;&lt;span class="nv"&gt;XDG_RUNTIME_DIR&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"/run/user/1000"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now create that directory and set the right ownership.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo mkdir&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt; /run/user/1000
&lt;span class="nb"&gt;sudo chmod &lt;/span&gt;700 /run/user/1000
&lt;span class="nb"&gt;sudo chown&lt;/span&gt; &lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;whoami&lt;/span&gt;&lt;span class="si"&gt;)&lt;/span&gt;: /run/user/1000
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1sxcw2vxyhqfxt77gwzn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1sxcw2vxyhqfxt77gwzn.png" alt="Making directory and giving user ownershup for desktop session on WSL" width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You’re almost there. Launch VcXsrv from the Start menu (search for XLaunch). Choose "One large window" or "Fullscreen", then "Start no client". On the extra settings screen, tick all boxes and add &lt;strong&gt;-dpms&lt;/strong&gt; in the additional parameters. Click Finish, and a black screen appears.&lt;/p&gt;

&lt;p&gt;Back in your WSL terminal, start the desktop.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dbus-launch &lt;span class="nt"&gt;--exit-with-session&lt;/span&gt; gnome-session
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1spnirrinngl56nttb42.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1spnirrinngl56nttb42.webp" alt="GNOME Desktop session on WSL" width="600" height="375"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Your Ubuntu desktop will fill the VcXsrv window. You can resize it, move it around, and use Linux GUI apps alongside Windows programs seamlessly.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I’ve Learned From Using This Daily
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The desktop environment does work, but I’ll be honest: it’s clunky and a bit slow compared to a traditional virtual machine&lt;/strong&gt;. That’s not the point of WSL, though. WSL was built to give you a bare‑minimum Linux system for running and testing applications and code, all without leaving Windows or dual booting. The desktop is a bonus, not the main event.&lt;/p&gt;

&lt;p&gt;The acpid hold trick saved me hours of debugging early on. Before I knew about it, my GNOME session kept crashing after a package update, and the logs were nothing but acpid error loops. Now I mark that package on hold every time I set up a new WSL instance. It’s one of those tiny fixes you only discover by breaking things.&lt;/p&gt;

&lt;p&gt;With or without a desktop. You can run &lt;strong&gt;Docker&lt;/strong&gt;, code in &lt;strong&gt;Python&lt;/strong&gt; or &lt;strong&gt;Node&lt;/strong&gt;, and test websites, all while keeping your Windows comfort zone intact.&lt;/p&gt;

&lt;p&gt;For a full walkthrough with every screenshot, detailed VcXsrv configuration, and alternative desktop options, check out my complete guide on MusaBase: &lt;a href="https://www.musabase.com/2025/04/how-to-install-linux-distribution-on.html" rel="noopener noreferrer"&gt;How to Install a Linux Distribution on Windows 10/11 with WSL and WSL2&lt;br&gt;
&lt;/a&gt;. I go deeper into each step and show exactly what you should see on screen.&lt;/p&gt;

&lt;p&gt;Hope this helps you stop dual booting and start doing more actual work. Give it a try and let me know how it goes.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>virtualmachine</category>
      <category>wsl</category>
      <category>opensource</category>
    </item>
    <item>
      <title>The Undocumented Steps to Virtualizing SteamOS (Steam Deck's OS) on QEMU/KVM"</title>
      <dc:creator>Abdullah Musa</dc:creator>
      <pubDate>Thu, 30 Apr 2026 21:43:20 +0000</pubDate>
      <link>https://dev.to/retro-1o1/virtualizing-steamos-with-qemukvm-the-steps-nobody-tells-you-2mcm</link>
      <guid>https://dev.to/retro-1o1/virtualizing-steamos-with-qemukvm-the-steps-nobody-tells-you-2mcm</guid>
      <description>&lt;p&gt;&lt;strong&gt;SteamOS&lt;/strong&gt; is not a standard Linux distribution. It ships as a recovery image for the Steam Deck, not a generic ISO. That fact explains every strange requirement you face when you try to run it in a virtual machine. The file you download is a &lt;strong&gt;.bz2&lt;/strong&gt; archive, not an installer. The VM must present the virtual drive as &lt;strong&gt;NVMe&lt;/strong&gt;. And if you let the system reboot right after installation it will launch into Gaming Mode, which cannot work without the Deck's custom AMD GPU.&lt;/p&gt;

&lt;p&gt;I have a full in-depth walkthrough on my blog. This post gives you the reasoning and the exact commands to get a working VM, plus the one intervention that saves you from a permanent black screen.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7c7u2ay8pjhj8fjhouf9.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7c7u2ay8pjhj8fjhouf9.webp" alt="Neofetch inside SteamOS running on QEMU/KVM" width="799" height="458"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The .bz2 Archive Hides a Raw Disk Image
&lt;/h2&gt;

&lt;p&gt;Head to Valve's official SteamOS page and you get a steamOS-recovery-image.bz2 file. Decompress it with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;tar&lt;/span&gt; &lt;span class="nt"&gt;-xjf&lt;/span&gt; steamOS-recovery-image.bz2
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Inside you'll find a .img file. It's a raw block-level copy of a full SteamOS installation, not a live environment. It contains a GPT partition table, the bootloader, and the A/B root partitions used for atomic updates. Valve compresses it with BZIP2 to keep the download small. That's fair.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why You Must Use an NVMe Virtual Drive
&lt;/h2&gt;

&lt;p&gt;The Steam Deck uses an NVMe SSD. The recovery image's installer scripts look for a block device at &lt;strong&gt;/dev/nvme0n1&lt;/strong&gt;. If you attach the virtual disk as a SATA or IDE drive, the kernel sees &lt;strong&gt;/dev/sda&lt;/strong&gt; and the installer will say no valid target is found. It's not a bug. It's what the script expects.&lt;br&gt;
In QEMU you emulate an NVMe controller. First create a virtual disk:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;qemu-img create &lt;span class="nt"&gt;-f&lt;/span&gt; qcow2 steamOSDrive.qcow2 16G
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then map it in the launch command. The crucial flags are:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;-&lt;span class="n"&gt;drive&lt;/span&gt; &lt;span class="n"&gt;if&lt;/span&gt;=&lt;span class="n"&gt;none&lt;/span&gt;,&lt;span class="n"&gt;id&lt;/span&gt;=&lt;span class="n"&gt;nvme0&lt;/span&gt;,&lt;span class="n"&gt;file&lt;/span&gt;=&lt;span class="n"&gt;steamOSDrive&lt;/span&gt;.&lt;span class="n"&gt;qcow2&lt;/span&gt;
-&lt;span class="n"&gt;device&lt;/span&gt; &lt;span class="n"&gt;nvme&lt;/span&gt;,&lt;span class="n"&gt;drive&lt;/span&gt;=&lt;span class="n"&gt;nvme0&lt;/span&gt;,&lt;span class="n"&gt;serial&lt;/span&gt;=&lt;span class="n"&gt;badbeef&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The serial number is required and can be any string. The moment the recovery environment sees an NVMe namespace, the install option lights up.&lt;/p&gt;

&lt;h2&gt;
  
  
  UEFI Firmware Is Not Optional
&lt;/h2&gt;

&lt;p&gt;SteamOS boots via UEFI with a GPT partition layout. Legacy BIOS won't work. QEMU provides UEFI through the OVMF firmware. You need two files:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;OVMF_CODE.fd (read-only firmware code)&lt;/li&gt;
&lt;li&gt;OVMF_VARS.fd (persistent NVRAM for boot variables)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On most distros these live in &lt;strong&gt;/usr/share/ovmf/x64/&lt;/strong&gt;. Pass them as pflash drives:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;-&lt;span class="n"&gt;drive&lt;/span&gt; &lt;span class="n"&gt;if&lt;/span&gt;=&lt;span class="n"&gt;pflash&lt;/span&gt;,&lt;span class="n"&gt;format&lt;/span&gt;=&lt;span class="n"&gt;raw&lt;/span&gt;,&lt;span class="n"&gt;unit&lt;/span&gt;=&lt;span class="m"&gt;0&lt;/span&gt;,&lt;span class="n"&gt;file&lt;/span&gt;=&lt;span class="n"&gt;OVMF&lt;/span&gt;.&lt;span class="n"&gt;fd&lt;/span&gt;,&lt;span class="n"&gt;readonly&lt;/span&gt;=&lt;span class="n"&gt;on&lt;/span&gt;
-&lt;span class="n"&gt;drive&lt;/span&gt; &lt;span class="n"&gt;if&lt;/span&gt;=&lt;span class="n"&gt;pflash&lt;/span&gt;,&lt;span class="n"&gt;format&lt;/span&gt;=&lt;span class="n"&gt;raw&lt;/span&gt;,&lt;span class="n"&gt;unit&lt;/span&gt;=&lt;span class="m"&gt;1&lt;/span&gt;,&lt;span class="n"&gt;file&lt;/span&gt;=&lt;span class="n"&gt;OVMF_VARS&lt;/span&gt;.&lt;span class="n"&gt;fd&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Without these, the VM tries BIOS mode, finds nothing on a GPT disk, and halts.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Full Installation Command
&lt;/h2&gt;

&lt;p&gt;With all pieces in place, the complete QEMU command for the installation phase looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;qemu-system-x86_64 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-cpu&lt;/span&gt; host &lt;span class="nt"&gt;-enable-kvm&lt;/span&gt; &lt;span class="nt"&gt;-smp&lt;/span&gt; 2 &lt;span class="nt"&gt;-m&lt;/span&gt; 8G &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-drive&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;pflash,format&lt;span class="o"&gt;=&lt;/span&gt;raw,unit&lt;span class="o"&gt;=&lt;/span&gt;0,file&lt;span class="o"&gt;=&lt;/span&gt;OVMF.fd,readonly&lt;span class="o"&gt;=&lt;/span&gt;on &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-drive&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;pflash,format&lt;span class="o"&gt;=&lt;/span&gt;raw,unit&lt;span class="o"&gt;=&lt;/span&gt;1,file&lt;span class="o"&gt;=&lt;/span&gt;OVMF_VARS.fd &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-drive&lt;/span&gt; &lt;span class="nv"&gt;file&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;SteamOS.img,format&lt;span class="o"&gt;=&lt;/span&gt;raw &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-drive&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;none,id&lt;span class="o"&gt;=&lt;/span&gt;nvme0,file&lt;span class="o"&gt;=&lt;/span&gt;steamOSDrive.qcow2 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-device&lt;/span&gt; nvme,drive&lt;span class="o"&gt;=&lt;/span&gt;nvme0,serial&lt;span class="o"&gt;=&lt;/span&gt;badbeef &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-display&lt;/span&gt; &lt;span class="s2"&gt;"gtk,gl=on"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-device&lt;/span&gt; usb-tablet &lt;span class="nt"&gt;-usb&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvqht6w1irfdkfjfqtngd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvqht6w1irfdkfjfqtngd.png" alt="QEMU launch command to run SteamOS recovery image on VM" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It boots the recovery image with the empty NVMe drive ready. Inside the VM, open the Wipe Devices &amp;amp; Install SteamOS option and click Proceed. The installer will write the A/B partitions to your virtual NVMe.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Gaming Mode Trap (Cancel the Reboot)
&lt;/h2&gt;

&lt;p&gt;Once the installation finishes, the wizard asks you to restart. If you click Proceed, SteamOS boots into Gaming Mode, which expects AMD GPU hardware. Inside a VM you get nothing but a black screen.&lt;/p&gt;

&lt;p&gt;Do not reboot. Instead, press Ctrl + Alt + T inside the VM to open a terminal. From there you force SteamOS to boot into the KDE Plasma desktop. Run these chroot commands on both partition sets:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;steamos-chroot &lt;span class="nt"&gt;--disk&lt;/span&gt; nvme0n1 &lt;span class="nt"&gt;--partset&lt;/span&gt; A &lt;span class="nt"&gt;--no-overlay&lt;/span&gt;
steamos-readonly disable
&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s1"&gt;'[Autologin]'&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; /etc/sddm.conf.d/zz-steamos-autologin.conf
&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s1"&gt;'Session=plasma.desktop'&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt; /etc/sddm.conf.d/zz-steamos-autologin.conf
steamos-readonly &lt;span class="nb"&gt;enable
exit&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fnfeetkqjewm3nk51hbaj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fnfeetkqjewm3nk51hbaj.png" alt="Changing SteamOS default gaming mode to KDE Plasma Desktop" width="800" height="502"&gt;&lt;/a&gt;&lt;br&gt;
Repeat the same block for --partset B. Then type reboot. The VM will now start directly into a working KDE Plasma session.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why All This Matters
&lt;/h2&gt;

&lt;p&gt;SteamOS is a locked-down appliance OS built for one device. Running it in a VM reveals the assumptions baked into the installer and teaches you a lot about how Valve's immutable filesystem and A/B update scheme work. And once you have a working desktop session, you can use it almost like any Arch-based system.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fl9vcboo4gz3rmieu9x6u.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fl9vcboo4gz3rmieu9x6u.png" alt="SteamOS running on QEMU VM fully updated" width="800" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For a deeper dive that covers additional configuration, GPU passthrough notes, and troubleshooting, check out the full original guide on MusaBase:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.musabase.com/2025/04/how-to-virtualize-steamos-test-its.html" rel="noopener noreferrer"&gt;How to Virtualize SteamOS: Test Its Power Within QEMU/KVM (2026 Updated)&lt;br&gt;
&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That's it. No magic, just an OS that wants to be on real Deck hardware. With a few QEMU tricks, you can convince it to run anyway.&lt;/p&gt;

</description>
      <category>steamos</category>
      <category>linux</category>
      <category>virtualmachine</category>
      <category>qemu</category>
    </item>
  </channel>
</rss>
