Prebuilt NVIDIA modules replace repeated driver compilation
dhh merged omacom/omarchy#17409 into the Quattro development branch to use prebuilt NVIDIA open modules with linux-omarchy. The corresponding package work is committed on omarchy-pkgs master. Modules are built and signed alongside their exact kernel, avoiding local DKMS compilation on eligible machines.
greptile-apps[bot] flagged that removing DKMS could leave an additional recovery kernel without graphics support. The final committed change retains DKMS when another kernel is installed. The eevdf and muqss variants also keep DKMS, as recorded in omacom/omarchy@97316b0bb66f and omacom/omarchy-pkgs@bffb8bf70650.
ARM FFmpeg gains NVIDIA recording support on edge
ryanrhughes merged
dhh's omacom/omarchy-pkgs#2074 into master, enabling NVENC and NVDEC in the aarch64 FFmpeg package. This addresses the missing encoder support that prevented Omarchy screen recording through gpu-screen-recorder on GB10 and N1x hardware.
dhh reported successful recording tests on a DGX Spark.
github-actions[bot] reported publication of FFmpeg 2:9.0.2-2.1 to edge/aarch64 in omacom/omarchy-pkgs#2074:issuecomment-6609673849. The carry follows Arch Linux ARM manually; its description warns that a newer upstream package can replace it without NVIDIA support until the upstream change lands.
Quake opens an agent picker or running local model
dhh merged omacom/omarchy#17457 into Quattro. An empty Quake console now offers the agent picker and prefers a running local model when a compatible agent is available. Agents installed from the console open tiled inside it rather than remaining in the floating installation terminal.
greptile-apps[bot] identified a failure when several terminal windows shared one process ID.
dhh responded with a unique installer window title and a regression test in omacom/omarchy#17457:discussion_r4456536132. Separate commits add Amp Desktop packaging on master and installation and removal menus in Quattro; removal preserves the Amp CLI's directories, as described in omacom/omarchy@8c76648872bf.
Package builds reject files owned by local account IDs
emirb's committed package build safeguard rejects archives containing files owned by a non-root user or an unexpected group. omacom/omarchy-pkgs@98353c6bab94 explains the trigger: the aarch64 Bitwarden package contained 222 files owned by numeric ID 1001, potentially giving a matching local account control over its installed binary.
A separate master commit changes Bitwarden extraction to use root ownership: omacom/omarchy-pkgs@8896655942d7. The safeguard rejects affected builds before publication; the commit reports that Bitwarden on aarch64 was the sole exception found in its examination of 525 edge packages.
Hyprland update proposal targets monitor removal crashes
MPavleski's omacom/omarchy-pkgs#2064 remains open. It now proposes Hyprland 0.57.1-2 together with matching titlebars, replacing its initial session-lock and dmabuf backports because the upstream release includes those fixes.
Before that change of approach, MPavleski reported that a locally patched 0.57.0 build survived HDMI removal without the Firefox crash and shell exit seen previously. Those are contributor test results for that build.
l2aptor separately requested priority after reporting loss of HDMI output after unlock, with one successful boot using another patch included upstream. These reports explain the update's urgency without establishing a published fix.
Superwhisper setup repairs reach Quattro
dhh closed
AnPod's omacom/omarchy#15622 without merging it, explaining that alternative changes had addressed first-run setup, tray placement and the missing aarch64 image package. The proposal had described fresh installations lacking Superwhisper's per-user profile and shortcuts.
Quattro also gained a committed repair for existing unconfigured installations and a shared Hyprland reload helper. omacom/omarchy@5c0d91a18549 addresses setup invoked outside the desktop session: reloads use Hyprland's instance selection, report real failures, and no longer cause dictation setup to fail after saving configuration.
ARM kernel adds device trees for four Snapdragon laptops
ryanrhughes merged
birkskyum's omacom/omarchy-pkgs#2049 into master, adding device trees for the Acer Swift 14 AI, Swift Go 14, Dell Latitude 5455 and HP EliteBook 6 G1q. The submission says firmware packages and systemd hardware identifiers were already present, allowing image selection to use the new trees.
github-actions[bot] reported linux-omarchy 7.3-11 published to edge/aarch64 in omacom/omarchy-pkgs#2049:issuecomment-6592465708. The proposal reports successful tree builds but explicitly states that none of the four laptops had booted this kernel, so publication does not establish working hardware support.
Omapasskey is published after terminal output hardening
Divanyx's TPM-backed Omapasskey submission was published and closed. In omacom/omarchy-plugin-marketplace#13302:issuecomment-6602986228,
Divanyx reported that version 1.2.2 escapes untrusted terminal control characters in account and device names, including already stored names, with regression tests.
HANCORE-linux then confirmed the previously reported findings were resolved at the reviewed commit and accepted the explicit setup of its dedicated system service.
github-actions[bot] recorded publication in omacom/omarchy-plugin-marketplace#13302:issuecomment-6614926435. Users still need native service installation and PIN setup; verification applies to the exact marketplace snapshot and is not a security audit.
PrimoDock update remains blocked on an app identity launch path
PrimoGameStudio's omacom/omarchy-plugin-marketplace#13628 remains open. Follow-ups removed raw application identities from automatic icon paths, passed restore arguments as data, and replaced an eval-based webapp launch route.
HANCORE-linux confirmed the webapp fix but identified another path at the latest target: an unknown pinned application's client-supplied identity could still reach a shell after the user closed and relaunched it. omacom/omarchy-plugin-marketplace#13628:issuecomment-6618047712 leaves approval withheld. The finding describes conditional execution as the desktop user, based on static review, with no root or zero-click claim.
Shell update pause proposal advances with recovery gaps
taxin-404's open omacom/omarchy#16900 proposes pausing plugin loads during package replacement, then restarting the shell. It targets old engines loading incompatible new QML mid-update and leaving shell keybindings unusable.
After greptile-apps[bot] raised concerns,
taxin-404 reported fixes for uncertain lock states, foreign shell identification, bar changes during a pause and notification timestamp symlinks. Failed refresh and channel-switch transactions still need a shared recovery decision. The latest contributor report also leaves one configuration check failing because companion packaging hooks are absent; the proposal has not merged.
