I have been running Omarchy on my gaming desktop for a couple of months now. It has been running smoothly, but for whatever reason, I tried doing an update today.
Long story short, the upgrade failed. I unfortunately, didn’t pay too much attention to the console and it closed when I pressed something. So I have no idea what the original error was. I knew the update failed, and that hyprland is showing 690K errors in the config.
Rolling back
I didn’t panic, remembering that it created a system snapshot, I rebooted and selected the snapshot in the boot menu. It seemed to have done its thing, but the hyprland errors still persisted.
The system was usable, however the error messages were annoying and always showed up in the active workspace, and didn’t go away when you went fullscreen. It was not possible to game, but coding was fine.
I tried a few things randomly on and off when I got ticked off by the message, including:
- checking out random tags/versions in the ~/.local/share/omarchy repo
- removing my hypr config files, a lot of my ~/.config dirs are symlinked to a repo, and I thought maybe that was causing issues. I had to undo this, because my keybindings and bar went poof.
- clearing
pacmancache
Fixing the update
This evening, I really wanted to play some games, but this annoying error message is in the way. So I tried updating one more time, and then it clicked. The update is actually updating packages in pacman and one of the packages is not signed with a trusted key. I was so pre-occupied with the hyprland errors, that I didn’t pay attention to the update error.
After some searching on the web, I found this command:
pacman -Sy archlinux-keyringThis presumably updated the trusted keys in my system. This finally unblocked the update, which got rid of most of the errors. I ran into this issue which I just copied the fix verbatim:
windowrule = match:class (Alacritty|kitty), scroll_touchpad 1.5
windowrule = match:class com.mitchellh.ghostty, scroll_touchpad 0.2I then realized that my hyrpland errors were probably because of breaking changes in the config format and that migration scripts probably fixed it as soon as I fixed the package that was blocking the update!
Last step was fixing hyprscrolling. After the update, setup reverted to the usual BSP layout. hyprpm showed that hyprscrolling is enabled, but any commands to enable/disable/remove always failed with an error message saying it wasn’t found. This was quickly resolved by running:
hyprpm updateAfter running this, hyprscrolling just started working without any additional steps.
Anyway, I survived, I was ready to run omarchy-reinstall if I couldn’t figure it out, but not tonight!