This layer combines applications, an installation helper and a background service rather than four mutually dependent apps. yay assists package workflows, Chromium browses the web, Nautilus browses files, and CUPS handles print jobs. Installed applications do not need to run through yay during everyday use.
Example: downloading and printing a document. Chromium downloads it; Nautilus helps locate it. A compatible application opens the file and submits a print job; CUPS manages the queue and delivery to the printer. The reader might be a browser or a separate application—file browsing does not imply support for interpreting every document format.
Network printing may involve Avahi discovery. Removable storage in the file manager can involve udiskie and mounting services. Applications consume capabilities from other layers rather than implementing them all.
Distinguish package-installation failures, application launch failures, inaccessible locations and failed print queues before choosing which component to investigate.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
Web browser and a foundation for browser-based applications.
Package
chromium
Membership
Core manifest
Purpose and everyday use
A web browser used for websites and browser-based applications. Browser profiles hold settings and site state independently of the desktop theme.
How it works and connects
Web content, extensions, graphics acceleration and desktop integration form different layers. Screen sharing also depends on the portal and media stack.
Configuration and customization
Use browser settings for permissions, downloads and profiles. Omarchy can supply policies and integration, so inspect managed settings before assuming a preference is user-controlled.
Troubleshooting approach
Compare another site and extensions-disabled behavior when appropriate. Network failures across all apps require system networking checks, not only browser cache changes.
Limits and change considerations
Extensions and site permissions can access sensitive content. Deleting a profile may remove local state; exporting bookmarks does not back up everything.
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 chromium
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.
Graphical file manager. Network mounts and previews use companion packages.
Package
nautilus
Membership
Core manifest
Purpose and everyday use
Provides graphical file browsing, copying, moving and opening. It also exposes connected locations through supporting desktop services.
How it works and connects
Local filesystem access differs from network mounts and removable-media handling. GVfs companions provide integrations while mounting may involve other services.
Configuration and customization
Adjust view and file-association preferences in the desktop workflow. Network credentials and mount behavior should be handled separately from folder display settings.
Troubleshooting approach
If a location fails, distinguish permissions, missing mounts and connectivity. Test another local folder before blaming the file manager.
Limits and change considerations
Trash behavior differs across filesystems and remote locations. Moving across filesystems can become copy-and-delete, so large operations need time and space.
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 nautilus
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.
Package helper for repository and AUR workflows; AUR build scripts still need review.
Package
yay
Membership
Core manifest
Purpose and everyday use
Assists with repository and AUR package workflows. It makes discovery and builds convenient, but AUR entries are build recipes rather than official repository binaries.
How it works and connects
Build recipes obtain sources and run package-building steps. The resulting packages are managed locally, while repository packages follow their configured repositories.
Configuration and customization
Review build-file changes and package choices before confirming updates. Follow Omarchy’s update workflow for the integrated system rather than mixing unrelated partial upgrades.
Troubleshooting approach
Separate network download errors, build failures and dependency conflicts. Preserve the first meaningful error instead of repeatedly retrying installation.
Limits and change considerations
Build scripts execute code. Popularity does not guarantee trustworthiness, and removing a package can affect dependent applications.
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 yay
yay --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.
Printing service with additional filters and configuration tools.
Package
cups
Membership
Core manifest
Purpose and everyday use
Manages printer queues and print jobs. Desktop print dialogs submit work to the printing system rather than communicating identically with every printer.
How it works and connects
Discovery, queue configuration, document conversion and device communication are distinct steps. Avahi can assist discovery, while filters adapt document data.
Configuration and customization
Configure the intended printer queue and supported options. Check paper size, duplex settings and destination before blaming the document application.
Troubleshooting approach
Inspect whether the service is running and whether a job is held, rejected or sent. A test document helps separate document-specific failures from device problems.
Limits and change considerations
Queued documents may contain private information. Printer sharing and remote administration expose additional services and should be configured deliberately.
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 cups
systemctl status cups --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.