Installing omarchy
In 2016, I wrote a blog called Installing Linux, which was mostly about rEFInd, partition tables, and a somewhat challenging afternoon. This one is shorter because the install genuinely wasn’t the hard part.
I installed Omarchy 4.0.1 on an HP EliteBook 6 G1a (AMD Ryzen 5 230, 32GB DDR5, and a 512GB SSD) on 21 August. From start to usable desktop was about 15 minutes, with most of that spent downloading the ISO! It asks for your name, a password, timezone and your disk, and then it gets on with it — Arch underneath, btrfs, and a working Hyprland desktop at the end with a menu bar, multiple themes and keybinds (lots and lots of keybinds – SUPER + K is your friend!) already set up. No bootloader archaeology, no dual boot, no rEFInd, although dual-booting with Windows is supposed to be equally easy.
So the install is the boring bit, and I mean that as a compliment. The interesting bit is the weeks afterwards, which is where I actually learned anything. Here’s what I had to fix, roughly in the order I hit it.
The fan
On this EliteBook, after installing, the fan would spin up and stay up. There’s no fan widget in Omarchy, so I wrote one – a little menu bar plugin that reads the embedded controller and shows temperatures plus a history graph. I then realised that my scaling maths was wrong and it was happily reporting 0% while the fan was still spinning. More on that in the plugins post, because it got a little out of hand, but just let that sink in. I wrote one!
Restart on Reboot
Another thing I didn’t realise I missed so much is macOS reopening applications after a reboot. This was another that I fixed without breaking a sweat, and it’s worked perfectly ever since. I even have my own keyboard shortcut (SHIFT-CRTL-SUPER-S) that captures the latest positions across all Workspaces. Another that I fixed!
Rounded window corners
Strangely, I also kind of missed the round corners on macOS. I know, but it was easy enough to change, so why not? I simply set rounding = 8 in looknfeel.lua. But how did I know this, and why was it so easy?
The locale
The installer gave me a UK keyboard layout and Europe/London as my timezone, but then set the system locale to en_US.UTF-8, which means American date order, weeks starting on a Sunday, and — the one that actually got me — US Letter as the default paper size.
In my defence, it’s a quiet failure. In my prosecution, it took me five weeks to work out why everything printed slightly wrong. One localectl set-locale and a locale-gen later, it’s British English throughout. The Brother driver needed a separate memo about A4!
My (new) monitor setup
My config still had the display layout from an old UPERFECT monitor, which is useless on the new MSI screen. Omarchy has a plugin called hyprmoncfg for this, and I’ve ended up with saved profiles — laptop only, and the MSI MP161 portable screen sitting above it.
I first blogged about using a portable monitor off a laptop back in August 2020, although like other Linux/FreeBSD desktops, it never really stuck. It almost didn’t with this, until I caught the issue. The UPERFECT monitor resets the brightness when it’s only connected by USB-C from a laptop. It needs to be USB-C powered to retain brightness, which defaults to 30% and is much too low. At the time, it wasn’t expensive, but I picked up the new MSI one for half the price, and that works perfectly with just a single USB-C cable. I also bought a Flexsta tripod to mount the keyboard above my laptop screen, which works really well as a home and mobile setup.
A PATH trap
This one is worth a paragraph as it cost me an evening. I have my own scripts in ~/.local/bin, and some of them deliberately shadow Omarchy’s own commands. From a terminal, this worked perfectly. Anything Hyprland launched directly got the Omarchy version instead, every time.
The reason is that Omarchy’s own envs.lua puts its bin directory first in PATH for the session, so my overrides were silently losing — even though a login shell got the order right via .bashrc. The fix is one line in hyprland.lua forcing ~/.local/bin at the front. Nothing was broken, which is exactly why it took so long to spot. Are you noticing a trend yet?
A polkit dialog that says no
I also run a Windows VM in Docker (yes, you can do that very easily in Omarchy from the menu, but I’ve even managed to get macOS running similarly) and launching it pops up a password prompt. That prompt would intermittently reject the correct password. Not a typo, not Caps Lock — the right password, refused, repeatedly.
It turned out to be a genuine bug in the Quickshell dialog rather than anything I’d done, so I’ve reported it upstream and in the meantime put my user in the docker group so the prompt doesn’t appear at all. That’s root-equivalent, and I’m not too thrilled about it, but this user already has full sudo access, so I decided I wasn’t giving too much away. I’ll remove it once the bug has been squashed. It’s almost like this isn’t me, right?
The VPN
Twice in the first few weeks, my network went strange in ways that had nothing to do with Omarchy and everything to do with NordVPN — once routing my own LAN traffic down the tunnel so I couldn’t see my own NAS, and once leaving me staring at Cloudflare challenges on half the internet. New OS, so I assumed that was the problem, but it wasn’t. NordVPN is a little more hidden by default, but you can unhide that pretty easily, and Nord settings and IP routing are now the first two things I check.
What I should have done on day one
Started the dotfiles repo. I installed on the 21st, and my first commit is dated the 30th, which means nine days of fiddling that I had to reconstruct from memory and shell history.
But what is the dotfiles repo, I hear you ask? One of the things Apple does so well, not just on MacBooks but on iPhones too, is transferring everything to a new device with just a few clicks. Omarchy doesn’t, so I tried to create something that at least made that possible. Dotfiles is a git repo with my config, a package list, a Borg backup running nightly at three in the morning, and a restore guide I’ve actually tested on a clean install rather than merely believed it works. Anyone who read the CrashPlan posts knows I’ve learned this lesson before, and apparently needed to learn it again!
So that covers some of the install gotchas. Not really install, which couldn’t really be any easier. But that’s enough for now. I think anyone who’s read any of my other blogs will know I did do all of this myself. Not only did AI (Claude Code specifically) help with all of the post-installation tinkering, but it also helped write this blog post. Most of it is still me, but there are still some of Claude’s wise words sprinkled throughout.
The AI integration and some of the software to make that feel SO integrated (yes, you herdr) is what makes omarchy feel so different and something I keep coming back to, even when I have a £2000 MacBook I could be picking up instead. I’m going to write another blog about the five or six plugins I’ve (we’ve) written, which is the part where this stopped being a migration and turned into almost a hobby!
October and November are feeling like a strong blogging end to 2026, although it has been 10 years, after all!!!

Recent Comments