These components are grouped by maintenance tasks, not dependencies. udiskie assists removable-media use; Btrfs tools administer filesystems; Snapper manages snapshots. Power Profiles Daemon exposes power profiles and works alongside, rather than inside, the snapshot workflow.
Snapshots: Btrfs provides filesystem snapshot capabilities, Snapper manages configuration and lifecycle, and Omarchy connects updates and recovery. In the documented bootable-snapshot workflow, Limine supplies the selection entry. btrfs-progs is an administration toolkit, not a separate replacement for the kernel filesystem implementation.
Removable drives: the kernel recognizes the device and filesystem, mounting services and authorization handle access, udiskie provides user-side assistance, and Nautilus displays accessible locations. Copying personal files to independent storage is another operation; system snapshots do not do it automatically.
The power panel uses the profile service for supported performance and energy settings. Mount failures, missing snapshots, missing recovery entries and battery drain therefore follow different diagnostic paths.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
A user-facing helper for mounting and managing removable media. It makes inserting a USB drive convenient without being the filesystem driver itself.
How it works and connects
Works with UDisks services and authorization. The file manager displays mounted locations; kernel drivers still determine whether the filesystem is supported.
Configuration and customization
Use its documented configuration for automount behavior and device preferences. Distinguish mounting a filesystem from unlocking an encrypted container.
Troubleshooting approach
Check whether the device exists, whether the filesystem is recognized and whether authorization succeeded. A failed filesystem check is not fixed by repeated mounting.
Limits and change considerations
Unmount before physically disconnecting writable media. Automount convenience is not a backup strategy and does not guarantee media health.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi udiskie
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Filesystem snapshot manager used in the snapshot setup. Root snapshots do not replace backups of /home.
Package
snapper
Membership
Other install candidates
Omarchy configuration or entry point
Update / snapshot workflow
Purpose and everyday use
Manages filesystem snapshots used to compare or recover system state. Omarchy’s documented update workflow creates snapshots that can participate in system rollback.
How it works and connects
Snapshots refer to filesystem state; integration tools make selected snapshots bootable. Snapper, Btrfs and Limine have complementary responsibilities.
Configuration and customization
Snapshot configuration defines the target and retention behavior. Inspect the existing configuration and use Omarchy’s documented workflow for restoring its system.
Troubleshooting approach
If a snapshot is missing, check creation and retention separately from boot-menu synchronization. A snapshot on disk and a bootable menu entry are different facts.
Limits and change considerations
The documented rollback excludes /home and its user configuration. Snapshots on the same disk do not protect against losing that disk.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi snapper
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Userspace tools for Btrfs filesystems, distinct from the filesystem driver in the kernel.
Package
btrfs-progs
Membership
Other install candidates
Purpose and everyday use
Provides userspace administration tools for Btrfs, including inspection of filesystems and subvolumes. Installing tools does not convert an existing filesystem.
How it works and connects
The kernel implements the filesystem; these tools communicate with it. Copy-on-write enables efficient snapshots, while shared extents complicate intuitive space accounting.
Configuration and customization
Understand mounted subvolumes, free space and snapshot policy before tuning. Compression, quotas and maintenance operations solve different problems.
Troubleshooting approach
Identify the mounted filesystem first. For space pressure, examine snapshots and metadata as well as visible files; avoid repair commands without a diagnosed filesystem problem.
Limits and change considerations
Snapshot deletion and filesystem repair are not ordinary file browsing. Same-device snapshots are not independent backups, and maintenance can consume substantial I/O.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi btrfs-progs
btrfs version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Provides power profiles exposed by the desktop power panel.
Package
power-profiles-daemon
Membership
Core manifest
Purpose and everyday use
Exposes power profiles used by the desktop power panel. Profiles provide a convenient performance-versus-energy choice when supported by the hardware.
How it works and connects
Coordinates supported platform mechanisms through a system service. Available profiles and their effect depend on hardware and drivers.
Configuration and customization
Use the power panel for ordinary selection. Understand whether settings differ on battery and AC before diagnosing an unexpected profile change.
Troubleshooting approach
Check service state and compare workload, thermal conditions and power source. High battery drain can come from applications or devices beyond profile control.
Limits and change considerations
It is not a complete battery-health or fan-control system. Multiple tools attempting to set the same platform controls can conflict.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi power-profiles-daemon
systemctl status power-profiles-daemon --no-pager
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.