Skip to content
omarchyFIELD GUIDE
PRACTICAL KNOWLEDGE / FIELD GUIDE

Desktop interaction

Menus, panels and notifications provide controls for services beneath them.

← Back to the system map

This layer connects desktop controls to underlying capabilities. Quickshell hosts Omarchy’s bar, menus, panels and notifications; wl-clipboard gives command-line programs access to the Wayland clipboard. They cooperate within the desktop rather than forming a mandatory sequence.

Opening the network panel: the user interacts with the shell, NetworkManager manages the connection, and the interface presents its state. Likewise, the audio panel is the user-facing control while PipeWire and WirePlumber handle media and routing.

Copying from a terminal: wl-copy offers data through the Wayland clipboard mechanism, and the target application requests a suitable format. wl-paste lets a terminal read clipboard data. A clipboard-history interface is an additional feature, not the entire responsibility of wl-clipboard.

For one incorrect panel, investigate its service too. For a missing shell, start with the shell itself. Working copy/paste with broken history suggests separating data transfer from history management.

Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.

All 2 components catalogued in this category

Quickshell

Runtime for the Omarchy shell: bar, menu, notifications, panels and lock screen.

Detailed guide: integration, practical tasks and diagnosis →

Package
quickshell
Membership
Core manifest
Omarchy configuration or entry point
~/.config/omarchy/shell.json

Purpose and everyday use

Provides the runtime for Omarchy’s bar, menus, panels, notifications and lock screen. In this snapshot these are parts of one integrated shell rather than separate bar and launcher applications.

How it works and connects

Quickshell is a Qt/QML toolkit. Omarchy supplies the actual shell UI, which displays and controls services such as networking and audio; it does not replace those services.

Configuration and customization

The documented Omarchy entry is ~/.config/omarchy/shell.json. It holds bar layout and idle settings. Once a personal file exists, it is authoritative rather than a deep merge of new defaults.

Troubleshooting approach

When one panel fails, check its underlying service as well as shell configuration. When every panel disappears, inspect the shell process and recent configuration changes first.

Limits and change considerations

Custom QML/plugins extend a running desktop process and should be treated as executable code. Resetting layout can discard personal arrangements; save them first.

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 quickshell

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.

Related components and next steps

Continue with the practical guide →

Sources and scope

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.

wl-clipboard

Command-line clipboard tools for Wayland.

Package
wl-clipboard
Membership
Core manifest

Purpose and everyday use

Supplies wl-copy and wl-paste for moving text or other data between terminal tools and the Wayland clipboard. Useful for composing command-line workflows.

How it works and connects

Uses Wayland clipboard protocols and offered MIME types. Clipboard transfer, primary selection and persistent history are different features; a history UI may be supplied elsewhere.

Configuration and customization

Choose text/binary types deliberately when building scripts. Run it in the intended Wayland session so the relevant display environment is available.

Troubleshooting approach

For empty or wrong-format pastes, check offered types and whether the source application is still available. Compare terminal-to-terminal and terminal-to-GUI behavior.

Limits and change considerations

Clipboard contents may include secrets. Avoid recording clipboard output in logs; these utilities do not provide secure storage or a synchronized clipboard service.

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 wl-clipboard

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.

Related components and next steps

Continue with the practical guide →

Sources and scope

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.

Search all components · Official package manifest index

This page follows the shared catalogue and its pinned source snapshot; it does not represent every release or all transitive dependencies.