Pacman answers its own conflict question with No under --noconfirm, so one
retired package can stop every update after it. Which package to drop is a
decision rather than a cleanup, so run the upgrade again with pacman asking
when there is a terminal to answer on, and report instead when -y promised
not to ask.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The pacman cache grows without bound across updates, and nothing in the
update flow ever reclaimed it. On a machine that has been updating for a
while it reaches several gigabytes of superseded versions that nothing
will ever install again.
Prune it with paccache -rk2 as the first step of an update. Both halves
of that placement are load-bearing.
Keeping two versions rather than one preserves the rollback path. The
cache is Arch's only offline downgrade: when an update breaks a single
package, reinstalling its predecessor from here is the surgical fix,
where a snapshot rollback would revert every other package too. Pruning
before the packages update means the installed version is still the
newest cached, so it survives along with a spare. Retention is by
version order and never consults what is installed, so that holds while
the installed version is among the two newest cached; a deliberate
downgrade or repeated failed transactions can stack newer archives on
top of it.
Running before the snapshot is what actually frees the space. The cache
sits on the snapshotted root subvolume, so a prune taken afterwards
leaves the fresh snapshot holding those extents and reclaims nothing
until it ages out of the number cleanup.
A failed prune warns and continues. Cache housekeeping should not trip
the update's ERR trap and tell the user their update went wrong.
This runs after omarchy-update-requires-free-space, so it reclaims space
during healthy updates but does not rescue a machine already under the
10 GiB gate.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Fail the snapshot when Snapper is installed but has no configs
omarchy-snapshot create loops over the configs snapper reports. With none,
the loop body never runs, so it prints "Create system snapshot" and exits 0
without capturing anything. Every update then reports a snapshot it never
took, and the absence only surfaces when a rollback is needed and the
snapshot list turns out to be empty.
* Say so when the update proceeds without a snapshot
The update ignores exit 127 so a system without snapper updates quietly.
Any other snapshot failure was being swallowed by the same expression,
which let the update continue with no indication that it was now
unprotected. Keep continuing, but say it out loud.
* Point the snapshot repair hint at how the installer runs it
Also hold the green header until a snapshot will actually be attempted,
so the no-config failure doesn't open with a success banner.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Continue the quattro upgrade when the pre-upgrade snapshot fails
The upgrade runs under set -e, so the new non-zero exit from an
unconfigured Snapper would have aborted a re-run at the snapshot step
instead of proceeding like omarchy-update does.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* Warn when disk space is low before updating
* Simplify update free space warning
* Stop updates without enough free space
* Allow forcing updates with low disk space
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
The retired omarchy-update-user-notify.path stays loaded in sessions that
started before the update removing it, and pacman writes the migrations
directory mid-transaction, so it fired a critical toast for migrations that
omarchy-migrate was about to apply a step later. Migration 1785095882 stops
that watcher, but migrations run after pacman, so it lands 11 seconds too
late to prevent the toast it exists to retire.
Check the lock omarchy-update holds for its whole pipeline instead of
trusting that no trigger exists. That covers the stale watcher and anything
added later: during an update every pending migration is by definition
already being applied. The check repeats after waiting for the notification
server, which is long enough for an update to start underneath it.
Only this user's runtime directory is read, never the /tmp path the updater
falls back to without XDG_RUNTIME_DIR. A shared lock file belongs to whoever
created it first, so honouring it would let one user silence another user's
notification; a redundant toast is the better failure.
The sleep inhibitor now starts with the lock descriptor closed. It outlives
the step that starts it, so an update killed before restore_update_inhibitors
left it holding the flock indefinitely. That already blocked later updates,
and now that the notifier reads the same lock it would have silenced
migration notices at every login.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Remove legacy online installer entrypoints, collapse migrations for 4.0, and move setup responsibilities into target-side system, hardware, and user commands.
* Persist urgent notifications
* Create omarchy-snapshot
* Create snapshot before pulling
* Extract alternative bootloader configs
* Add limine-snapper config
* Fix check
* Update login scripts
* Make chroot friendly
* Extract cmdline instead of using blkid due to error
* Add restore command
* Export $TERMINAL so we get clickable restore notifications
* Remove sync -- causes errors...we have nothing to sync yet
* Executable
* Minor cleanup and compatibility for non-ISO
* Give login its own section
* Give no-arg guard and inline commands
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Add safeguard to prevent omarchy-update from beginning an update during an AUR ddos
* Fix spacing
* Update omarchy-update
Return a non-zero error code when failing to reach AUR
* Add user-agent string
Good courtesy that makes it easier for the AUR folks to interpret the HEAD requests and tell us if there is an issue.
* Ensure entire icon will fit
* Migration to fit entire icon for update-available in waybar
* feat: add precise media control shortcut
* Fix a handful of typos
* Add state based app restarts for migrations (#637)
* Look for app restart state files and restart them after update
* Convert existing migrations to set states
* Revert "Convert existing migrations to set states"
This reverts commit 1eb8a56b075cab5652a028202dc9dc81e556c4dc.
* Fix waybar update icon spacing (#672)
* Fix waybar update icon spacing
Remove clock from margin rule and add custom-update to prevent horizontal cutoff and reduce excessive spacing between clock and update icon.
* making the update icon smaller, looks better in the center
* Fixed this in CSS instead
* We now have a global $OMARCHY_PATH
* Fix screen recording on Intel graphics (#669)
* Fix screen recording on Intel graphics
Use wf-recorder for Intel graphics instead of wl-screenrec due to VAAPI compatibility issues that prevent recording from starting.
* combining greps for nvidia and intel graphics
* Update omarchy-cmd-screenrecord
* Force working version of uwsm until we get the fixed one from upstream
* Split upgrading system packages into two steps
* uwsm was already fixed upstream with 0.23.2
* Add burst limit to login to prevent endless retries (#690)
* Fix kernel update detection for alternative kernel variants (#585)
* Fix omarchy-update kernel update message to support alternative kernel variants
* fix: omarchy-update-restart kernel update message to support alternative kernel variants
* Add elan to the keywords used to detect if a fingerprint reader exists (#692)
* fix pgrep and pkill (#687)
* Make a function to create a smaller webshare version
* Set sudo max tries to 10, binary for easy lockout reset (#686)
* set sudo max fail count to 10, bin for easy reset
* Slim down
Let the failure just fail in the shell
* Rename to be more descriptive
* No need for the 00- prefix
* Add migration to raise sudo try limit
---------
Co-authored-by: Manuel <manuel.ramsaier@gmail.com>
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Install `gum` prior to the preflight guard (#684)
* Use `read` instead of `gum` in the preflight guard
* Revert "Use `read` instead of `gum` in the preflight guard"
This reverts commit 759dbb70454dccc27b78b198bf077e076750fefc.
* Install `gum`, if required, at the beginning of `install.sh`
* `gum` is already installed by the `presentation.sh` stage
* Use existing structure
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Always install `base-devel` in case `yay` needs to build a package (#710)
* chore: Enable Walker list cycling (#709)
Enable the `cycle` behaviour for Walker lists; this allows one to
quickly jump from the default-selected first item in a list, to the
last item, simply by pressing the "up" arrow key (or other key
sequence bound to "previous").
Refs: https://github.com/abenz1267/walker/wiki/Basic-Configuration
* Add one wallpaper for nord (#707)
* Use `pacman` instead of `yay` to install `gum` (#705)
* Direct access to Walker clipboard + emojis with hotkey
* Turn off the walker service until the memory leak is fixed
See https://github.com/basecamp/omarchy/issues/698
* Can't use clipboard module when Walker is not running as a service
See https://github.com/basecamp/omarchy/issues/698
* pacman needs sudo
* Add disable chaotic aur env flag (#746)
* Add missing modifier combinations to omarchy-menu-keybindings (#715)
While these aren't currently used directly in the Omarchy code, when the
user adds custom bindings they are not properly displayed by the
omarchy-menu-keybindings script.
Co-authored-by: Chris Miller <chris@diddado.com>
* Make this resilient to file already being removed
* Use omarchy-chromium-bin to give live theme changes
* Transcoding is really from any image format
* Include Brave in the same opacity treatment as chromium
* Only ask for the identification if it has not already been provided
* Need to make the new disk writeable too
* Stop using tte until package is fixed
* Use host's DNS resolver in Docker containers (#812)
* Symlink /etc/resolve.conf to systemd-resolved's stub
Since systemd-resolved is managing the DNS configuration, ensure that
/etc/resolv.conf uses it.
* Use systemd-resolved from Docker containers
* No longer needed now that we have .config/chromium-flags.conf
* Add brave-flags.conf as a new default to ensure that anyone using Brave as their browser runs it under wayland
* Must restart waybar when timezone is changed to have it reflect immediately
* Add migration for adding .config/brave-flags.conf
* Only do system package updates if there is a network connection
This prepares us for offline ISO install
* Catch both cases of brave-browser identification
* Skip pinta until we can resolve the certificate issue on manual build
cc @Torxed
* Add dust to reveal used space
Co-authored-by: @tobi
* Add minimal starship prompt to terminal
Co-authored-by: @tobi
* Always noconfirm
* If NOT starship, install it
* Add `--force` when enabling ufw to bypass prompt (#794)
* Add current theme to fastfetch config (#889)
* Turn off tte until the package is fixed
* Turn off auto-launching screensaver until tte is fixed
* Add current theme to fastfetch config
fastfetch has a module for displaying colors, which is often used by
default. It shows the current colors in use by the terminal. Given that
themes are core to Omarchy, I thought it made sense to show the current
theme in fastfetch. I've also added a compressed version of the palette
(similar to the circle config of the colors module).
* Add migration
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Don't fail in case chromium package is not there
In case another package has been used to provide chromium
* No prefix needed
* Lines up better with the new starship prompt
* fix: missing python-poetry-core make Omarchy install fail (#862)
* fix: missing python-poetry-core
* added migration
* Flesh out migration to fix all tte issues
* Turn TTE back on
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Add color to install / remove to differentiate (#858)
* Add color to install / remove to differentiate
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Ensure Zoom is not made transparent
* Ensure the directory is present
* No double logo
* fix: add python-object to make installation of Omarchy work (#806)
* Explicitly add python-object to make powerprofile work
* added migration
* Explain the why, not the how
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Turn screensaver back on now that we have fixed the tte install
* Add migration to turn on screensaver again
* Even more minimal and theme matching
* Use italic instead of bold for git branch
* Minimal git status too
* Correct spacing
* Less aggressive untracked icon
* Consistent color before the >
* Stick to color
* Really just stick to one color everywhere
* Force the link
* Make resilient towards it already being the same file
* Offer install scripts a way to know if they're in chroot
* Different iwd needed on chroot install
* Address installation inside a chroot
* Can't reuse when needing to set for user
* Simplify
No other args
* Get the latest indexes if online
* Now available as an official package instead of AUR
* Add single server for mirrorlist for now
* Try a different mirror for testing and need to use pacman for pkg update before we have yay
* Use same shebang as everywhere
* Let it roll for testing
* Add debug to failure
* Force wifi to unblock when we go to set it up
Wifi can sometimes get turned off by computers when running on low power
or in some sleep modes
* Fix positive exit
* Put chroot provision into its own preflight
* Restore to the global mirror
* Clean up after ISO install without sudo
* Reduce ceremony -- a start and an end is enough
* If we installed from the installer, we should remind user to unplug USB
* Extra CR not needed
* Bring uwsm out of the doghouse
* Ensure latest uwsm is installed now that we have lifted the lock
* Fix JetBrains IDEs flickering and focus issues in Hyprland (#888)
* Fix JetBrains IDEs flickering and focus issues in Hyprland
Add window rules to prevent tooltip and tab dragging flickering issues
in JetBrains IDEs when running under Hyprland compositor.
* Fix JetBrains IDEs flickering and focus issues in Hyprland
Add window rules to prevent tooltip and tab dragging flickering issues
in JetBrains IDEs when running under Hyprland compositor.
Uses the new windowrule syntax (Hyprland v0.48.0+) instead of deprecated windowrulev2.
# Conflicts:
# default/hypr/apps/jetbrains.conf
* Fix JetBrains floating popup size issue in Hyprland
* Style
---------
Co-authored-by: Mike Veerman <mike@nonect.com>
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Don't need wget, since curl is already part of arch
* This is still a problem
* Feature/screensaver toggle instead of launch (#784)
* sceensaver-toggle and run if enabled using state file
* replace commands in menu and hyperidle
* migration file
* sed corrections
* added backup of changed files in migration
* review comments implemented
* hypridle config restore
* Use normal path style
* Use nerdfont icon for notification
* Make executable
* Allow a force start of screensaver so it can run even when disabled when manually triggered
* Add screensaver to system menu now that the toggle actually means toggle
* Known path without expansion spaces
* It should be an error return when it doesn't start
---------
Co-authored-by: Manuel <manuel.ramsaier@gmail.com>
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Add 60 second inactivity timeout to Walker launcher (#701)
* Add 60 second timeout to Walker launcher
This will close the launcher after 60 seconds of inactivity.
* Update 1754929737.sh
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* adding mongodb docker install (#972)
* Add suggestion for eu keyboard layout for iso
Closes#937
Co-authored-by: @chriopter
* Add Super + Tab to go forward through workspaces and Super + Shift + Tab to go backwards
Co-authored-by: @rafaelbernard
Closes#652
* move import to bottom (#917)
* Add missing package for Intel Graphics Card based device (#910)
* Add missing package for Intel Graphics Card based device
* Add migration to add the missing package
* Fix USB autosuspend causing peripheral disconnection issues (#906)
* Fix USB autosuspend causing peripheral disconnection issues
Add configuration to disable USB autosuspend by setting usbcore.autosuspend=-1
in modprobe.d configuration. This prevents USB devices from being automatically
suspended which can cause keyboards, mice, and other peripherals to disconnect
unexpectedly.
* Add migration to apply autosuspend to existing systems
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* retry cmd on failed install should take into consideration bare mode (#904)
* retry cmd on failed install should take into consideration bare mode
* A little duplication beats too much indirection
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Switch from lazydocker-bin to lazydocker
It's now in the official repo as a compiled version!
* add reverse window cycling with cycleprev (#874)
* add reverse window cycling with cycleprev
* Include the bringactivetotop fix
---------
Co-authored-by: observable <x@observable.art>
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Stop using SIGUSR1 with Waybar to prevent stacking
Closes#873
* Omarchy install - capture install log (#868)
* Omarchy install log
* Slim down the logging setup a bit, put it in a known directory, tell user about it
* Stick to what was
* Not needed here
* Prefer the duplication
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Allow customizing the screensaver logo (#863)
* check for custom screensaver logo or fall back to default
* move logo location to omarchy config folder
* fix missed location check
* add menu item to copy logo.txt and open in editor
* move to setup menu
* Just always use a user-editable screensaver.txt file
* No longer needed
* Be clearer
---------
Co-authored-by: Christopher Moore <cmoore@yozu.co.uk>
Co-authored-by: David Heinemeier Hansson <david@hey.com>
* Visual improvements for pkg-install and pkg-remove (#852)
* Shorten it up a bit
* Extract precondition into its own file and use it for the package installer too
* But don't actually fail unless it is down!
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
Co-authored-by: Michal Zaborowski <zaborowskimchl@gmail.com>
Co-authored-by: Richard Macklin <code@rmacklin.dev>
Co-authored-by: Ryan Hughes <ryan@heyoodle.com>
Co-authored-by: Alan Sikora <alansikora@gmail.com>
Co-authored-by: Eric Swanson <960576+ericrswanny@users.noreply.github.com>
Co-authored-by: not-NEK0 <86556080+not-NEK0@users.noreply.github.com>
Co-authored-by: Maximiliano Guzenski <maxguzenski@gmail.com>
Co-authored-by: Manuel <manuel.ramsaier89@gmail.com>
Co-authored-by: Manuel <manuel.ramsaier@gmail.com>
Co-authored-by: Dylan Bridgman <light@ether.org.za>
Co-authored-by: Simon Dawson <spdawson@gmail.com>
Co-authored-by: Swarnim <134050970+Swarnim114@users.noreply.github.com>
Co-authored-by: Bruce <hi+gh@bruceroettgers.eu>
Co-authored-by: Chris Miller <github@reaperville.com>
Co-authored-by: Chris Miller <chris@diddado.com>
Co-authored-by: Kevin McConnell <kevin.mcconnell@gmail.com>
Co-authored-by: Gary Rennie <gazler@gmail.com>
Co-authored-by: Shigeto Kumagai <shk@all.daynight.jp>
Co-authored-by: David Anderson <kataqatsi@gmail.com>
Co-authored-by: MikeVeerman <mike.veerman@gmail.com>
Co-authored-by: Mike Veerman <mike@nonect.com>
Co-authored-by: Rob Zolkos <rob@zolkos.com>
Co-authored-by: Valberto Enoc <valbertoenoc@gmail.com>
Co-authored-by: Saeed Vaziry <61919774+saeedvaziry@users.noreply.github.com>
Co-authored-by: Brosseau Valentin <c4software@gmail.com>
Co-authored-by: jw <jw@codasite.ai>
Co-authored-by: michaldziurowski <mdziurowski@gmail.com>
Co-authored-by: Observable Art <123117871+iamobservable@users.noreply.github.com>
Co-authored-by: observable <x@observable.art>
Co-authored-by: Chris24680 <moore12321@gmail.com>
Co-authored-by: Christopher Moore <cmoore@yozu.co.uk>
Co-authored-by: Luis Daniel Casais <71148501+rajayonin@users.noreply.github.com>
* Add omarchy to system path
* Remove unnecessary duplicate
* Remove path def since it's global now
* Migration for system-wide path
* Remove debug code
* Refresh after update
* Add common state script
* Restart on state detected
* Set state instead
* Export own path for menu
