Merged

Super+comma acts on notifications instead of simply dismissing them

dhh proposed and merged omacom/omarchy#16699 and its follow-up omacom/omarchy#16701 into quattro. Super+comma now invokes a notification's sole action or opens keyboard selection when several choices exist. Plain dismissal moves to Super+Alt+comma.

The follow-up accounts for clickable notifications without buttons, such as WhatsApp web notifications. The resulting commit also counts a native sender's own window as an available action, covering apps such as Signal. These are development-branch changes.

Merged

Network speed tests count their own traffic and stop with the panel

emirb proposed and merged omacom/omarchy#16681 into quattro, replacing the fast.com script with the separately packaged Omarchy speed-test client. It counts its own payloads rather than the interface's total traffic and receives the panel's process ID so closing the panel ends the test. A 20-second watchdog reports stalled phases.

emirb reported that unrelated downloads inflated the old readings and that upload workers survived panel closure; the supplied comparisons are the author's measurements. greptile-apps[bot] reviewed the replacement and noted the release dependency requirement. That dependency is now committed in omacom/omarchy-pkgs@9d9c35b5b886, explicitly without changing stable 4.0.6; it is intended to arrive with the release carrying the new launcher.

Open proposals

Try Omarchy proposes a desktop session directly from USB

emirb opened omacom/omarchy-iso#332 to add a Try Omarchy boot-menu entry. The proposal shares a read-only root image between installation and the live desktop, with temporary session writes held in RAM. Install remains the default, and a failed Try boot does not fall through into installation. The PR remains open.

greptile-apps[bot] reported no new blocking issue in its review, while github-actions[bot] reported passing installation checks on x86_64 and aarch64. emirb also reported USB desktop testing on an MSI Z690 and a smaller ISO. NVIDIA and T2 driver layers are included in the proposal, but the author explicitly reports no testing on that hardware.

Merged

New encrypted installs use 4096-byte sectors where possible

emirb proposed and merged omacom/omarchy-iso#336 into quattro, requesting 4096-byte encryption sectors on both installation paths when the partition size permits them. It also fixes free-space partitions being one 512-byte sector larger than requested, which prevented that sector size from working.

hegjon supplied a three-install-per-side ThinkPad T460s comparison, reporting root-image writes around 2.46 seconds with 512-byte sectors and 2.16 seconds with 4096-byte sectors, alongside faster sequential reads. These are contributor measurements, not a universal performance guarantee. The change affects formatting new encrypted volumes; changing an existing volume's encryption sector size requires rewriting it.

Merged

Snapdragon fixes address missing boot data and silent unlock keyboards

emirb proposed and merged omacom/omarchy#16688 into quattro so supported Snapdragon laptops load the I2C HID driver early enough to type an encrypted-disk passphrase. The author reported successful unlocking on an ASUS Zenbook 14 UX3480QA. After review, the detection uses Omarchy's shared Snapdragon helper; greptile-apps[bot] confirmed its earlier helper concern was fixed.

A related installer fix moves image-provided boot files onto the EFI System Partition, preventing the mounted partition from hiding Snapdragon device trees needed to build a bootable image. That work was merged into the ISO repository's quattro branch, as recorded by omacom/omarchy-iso@1fe8d0599c94. Neither development-branch merge establishes a stable release.

Committed

Background intros stop polling after their cover disappears

A quattro commit associated with emirb, omacom/omarchy@67faeb0d2b55, stops the background intro's frame-status timer once neither its cover nor a theme transition remains. Previously, a still-wallpaper handoff could leave the shell repeatedly starting status processes for the rest of the session.

The commit reports 62.5 process launches per second on a Snapdragon laptop. Its supporting comparison found lower battery power without a simulated polling loop, but that is an author-reported experiment rather than a measured guarantee for the shipped fix.

Merged

Apple GPU packages pair M3 defaults with runtime lifetime fixes

chriskearney's kernel packaging work in omacom/omarchy-pkgs#1622 pins merged M3 defaults and GPU runtime lifetime fixes. maralcbr discussed pairing the kernel with the boot handoff and then merged the PR into master. github-actions[bot] subsequently reported linux-aurora 7.2.11.aurora7-1 and its headers live on edge for aarch64.

Related default-branch commits update Mesa integration and the M3 MacBook Air boot package. The latter adds GPU start and power handoff settings for J613 and J615 at installation and relevant upgrades. The kernel PR's supplied description still records a hold for testing the exact kernel, Mesa and boot combination together; its merge and edge publication do not establish that this hardware-validation gate passed or that the combination reached stable.

Closed

Audio Cast reaches the marketplace after receiver access fixes

Audio Cast, submitted by yangkang5303 in omacom/omarchy-plugin-marketplace#11924, was published according to github-actions[bot]. The widget controls LAN audio casting through a separately installed Python CLI. Its receiver now starts with an empty source-IP allowlist, requiring owners to select trusted hosts before incoming connections are admitted.

Review progressed through access and revocation fixes. yangkang5303 replaced the internal TCP audio-server listener with the owner's private Unix socket. HANCORE-linux then identified a race in which an accepted connection could survive switching to restricted mode; yangkang5303 corrected registration to check the proxy's running state under the stop lock. HANCORE-linux confirmed that final fix and retention of the earlier corrections before publication. Manual CLI setup remains required, and the publication notice limits verification to the reviewed marketplace snapshot.

Open proposals

Strata Control listing pauses over runtime security requirements

The Strata Control submission remains open in omacom/omarchy-plugin-marketplace#12853, with schmittcn putting listing on hold pending upstream runtime fixes. During review, schmittcn corrected copied model configurations that could expose API keys to other local accounts, tightening directory and file permissions.

HANCORE-linux subsequently identified automatic URL-supplied prompts using saved credentials and enabled tools, plus affected image decoding in the reviewed Strata dependency. The reviewer required a supported runtime that prevents those paths rather than warnings alone. schmittcn argued that these belonged to Strata itself, then chose to wait for upstream releases before enforcing refusal of affected runtimes. The plugin remains available from its repository, according to the submitter, but this submission has not produced a marketplace listing.

Open proposals

Active Directory proposal repairs authentication and upgrade handling

CappieGold's open omacom/omarchy#16270 proposes domain setup, directory-password screen unlocking and restoration of SSSD account lookup after settings upgrades. In background review dated October 23, chessing234 identified incorrect PAM jumps and failure-tally handling. On October 26, CappieGold reported correcting those jumps, unprivileged SSSD detection and failed-read handling raised during review.

Further review exposed a repair trap: once an upgrade removes directory lookup, sudo cannot identify the directory user trying to restore it. CappieGold added a privileged pacman hook and pre-upgrade hook installation. greptile-apps[bot]'s latest summary describes that sequence and a non-blocking root-test issue. CappieGold explicitly distinguishes a remaining first-update packaging gap for previously joined machines without the hook. The proposal remains unmerged.

Open proposals

DST rollback reports connect clock warnings to failed application launches

mweinbergh opened omacom/omarchy#16677 after the October 25 clock rollback, reporting millions of timer warnings, accumulated shell logs filling the runtime filesystem and failures launching applications through UWSM. AzrielSins added a London report with warning timestamps and subsequent logger and application-daemon failures, while explicitly noting that filesystem occupancy could no longer be established after reboot.

Dominik-O22 supplied a Berlin report and traced the suspected loop to Quickshell's handling of ambiguous local times in SystemClock. The issue remains open. These reports support investigation of the clock and logging paths; they do not establish a merged fix.

Merged

Omaroll viewer becomes available on edge for both architectures

ryanrhughes merged btsouth's Omaroll package submission, omacom/omarchy-pkgs#295, into master. Omaroll 1.18.0 provides local image, video and PDF viewing, with camera RAW previews and a library accessible from the quick viewer.

github-actions[bot] reported the package live on edge for x86_64 and aarch64. The recipe stays on the normal release ring because it links Qt, so this publication does not establish availability on rc or stable.