Quattro gains audio repair, independent display scaling and default gestures

01Audio repair targets silent app deaths and dropouts

emirb merged omacom/omarchy#16824 into the Quattro development branch. It installs rtkit across platforms, lets host PipeWire clients request realtime scheduling directly, and repairs running sessions before enabling the service. The proposal identifies a zero realtime budget as the cause of silent application kills, alongside audio threads missing deadlines under load.

The repair raises existing zero limits before installation and coordinates concurrent updates. The PR reports no upgrade-induced kills on two tested physical machines and reductions from 111 and 92 audio underruns to zero in their low-buffer tests. These are contributor-reported measurements. Flatpak clients and WirePlumber retain portal-related limitations, so the merge does not establish that every affected path is fixed.

02Monitor scaling persists independently across displays

dhh proposed and merged omacom/omarchy#16923 into Quattro, replacing persistence through a shared scale setting with a rule for the focused monitor. Changing a laptop panel's scale should therefore stop changing an external display after configuration reloads.

In follow-up responses, dhh described atomic writes that preserve configuration symlinks and safeguards that leave complex monitor rules untouched. dhh then merged omacom/omarchy#16950 to derive session-wide GDK_SCALE from the lowest enabled monitor scale. This addresses oversized XWayland applications on a lower-density screen, with the stated tradeoff that they can appear slightly small on the denser display.

03Default touchpad gestures reach Quattro

dhh proposed and merged omacom/omarchy#16891 into Quattro. Three-finger swipes switch workspaces, toggle the AI console or open the Omarchy menu; four-finger swipes move the active window between workspaces or toggle fullscreen.

Existing custom gestures receive an opt-out migration to avoid conflicting bindings. During follow-up, dhh expanded detection to nested configuration files and symlinks and preserved symlinked configuration when editing it. Users can disable all default gestures or unset an individual binding before replacing it.

04The shell takes over background intro sequencing

dhh proposed and merged omacom/omarchy#16884 into Quattro, moving background intro sequencing from shell scripts into the desktop shell. The sequence holds the outgoing frame until the replacement is ready and coordinates the background link, intro playback and eventual Hyprland reload.

dhh's follow-up responses describe locking background changes against theme switches, checking intro activity while the reload lock is held, and falling back to an ordinary transition when an older running shell lacks the new handover. The changes target flashes, interrupted transitions and conflicting rapid selections.

05A native Wayland screensaver replaces terminal windows

omarchybot merged omacom/omarchy#16800 into Quattro. The replacement draws an overlay on every display and dismisses on mouse movement, clicks, scrolling or keys, replacing terminal windows that did not respond to mouse input.

The idle service also stops the screensaver for activity the overlay cannot receive, such as bound media keys, and cancels the pending lock when the user returns. The PR reports that the package is available on edge for both architectures; promotion to rc and stable remains necessary before an Omarchy release carrying the change reaches those rings.

06Password-selected family accounts remain under development

omarchybot opened omacom/omarchy#16920, an open Quattro proposal for multiple adults and children on one installation. Each account would have its own disk-unlock key slot, with the unlocking password selecting the desktop. Child accounts would add app restrictions, theme collections, screen time and a web allowlist.

Follow-up responses from omarchybot report fixes for cross-account access to child DNS resolvers, interrupted transfers of responsibility for root's password, and account creation when sudo requires a password. These are fixes within the proposed branch, rather than merged functionality.

The proposal explicitly limits its child controls: a determined child can alter their session, and a known disk password permits reading the disk from a live USB. Apple Silicon also needs boot-package support before accepting another person's key slot.

07Mise precedence discussion turns toward explicit opt-out

omarchybot opened omacom/omarchy#16881 about uninstalled lazy mise defaults taking precedence over separately installed commands. An earlier in-day response from omarchybot relayed a maintainer preference for putting only uninstalled defaults behind other installations.

cobrakoral subsequently reported tests showing that proposed PATH arrangements could bypass explicit project versions or fail inside mise execution. cobrakoral also distinguished an upstream reporting improvement from executable selection: displaying a tool as lazy does not change which binary runs.

Responding to those findings, jdx said explicit opt-out should be the resolution and asked that automatic fallback not be pursued in mise or Omarchy. jdx recommended disable_tools for individual commands or Remove > Preinstalls for Omarchy's defaults. The issue remains open; the supplied discussion establishes this recommendation, rather than a merged Omarchy precedence change.

08Installer proposal reduces USB startup contention

hegjon opened omacom/omarchy-iso#355, which remains open. It gives verification services separate I/O accounting, avoids unnecessary startup-shell work and prebuilds console fonts, aiming to reach the installer greeter sooner while retaining media verification.

After initial virtual-machine measurements, hegjon reported a real ThinkPad X200 test using the same USB stick: kernel start to greeter fell from 25.5 to 20.5 seconds, followed by a successful full installation. These are the proposer's measurements. The follow-up narrows the expected benefit on that machine, where the unchanged initramfs phase remained the largest delay.

09M3 Max display and GPU loader defaults reach edge

chriskearney's omacom/omarchy-pkgs#1707 was merged into master by ryanrhughes. The loader package enables existing display and GPU handoffs by default on the J516C 16-inch M3 Max, subject to admission checks, and includes a dependent memory handoff for T6030 external displays.

Approving reviewer maralcbr required the matching kernel and Mesa delivery to precede the loader so edge would not pair it with the old kernel. github-actions[bot] subsequently reported successful publication of m1n1-aurora 1.6.1.aurora22-1 to edge for aarch64.

The PR distinguishes earlier hardware tests from qualification of this exact combined package. Existing installations need a rebuilt and booted boot.bin to use the new Stage2, and installer rebuilds and full rc or stable qualification remain separate.

10Omarchy Files is listed after privacy fixes

spalencsar submitted the Omarchy Files launcher widget through omacom/omarchy-plugin-marketplace#13098. It launches a separate file-manager application and offers a confirmation-based installation under the user's home directory when that application is missing.

Reviewer HANCORE-linux confirmed earlier folder-history and delivery fixes, then identified private filenames and raw errors being exposed through notification command arguments. A later review confirmed that the v0.1.3 delivery resolved those findings and that the pinned archive checksums matched.

github-actions[bot] then reported publication and verification, and the submission closed. The verification applies to the reviewed marketplace snapshot and is explicitly not a security audit.