Adding plugins preserves running panels and services
dhh authored and merged omacom/omarchy#18198 into the quattro development branch. Plugin discovery now synchronizes plugins in place instead of unloading running services and panels. This addresses first-login disruption when Superwhisper adds its panel: open menus closed and the wallpaper briefly went black.
greptile-apps[bot] reported that queued rescans could still trigger full reloads and that plugin folder names could differ from manifest IDs. Its final review says both findings were addressed. Updates and edits to loaded plugins retain a full reload path; the author reported smoke-test coverage but had not yet watched a real first login with the fix.
Snapdragon X1 kernel fixes reach edge
dhh proposed and
ryanrhughes merged omacom/omarchy-pkgs#2342 into master, combining lid-switch, RTC timezone and audio-probe fixes in kernel package 7.3-39.
github-actions[bot] subsequently reported successful publication of the kernel, headers and NVIDIA packages to edge/aarch64. This establishes edge availability, not stable promotion.
The changes restore repeated lid events, honor the timezone stored with the firmware RTC offset and deliver DSP replies during sound-card probing. The proposal reports individual testing on an ASUS Zenbook 14 UX3480QA, but says the patches had not run together on hardware. It also discloses a possible one-time clock shift until NTP corrects an offset written by the old driver and an open upstream review point on failed audio probes.
Snapdragon installation fixes firmware staging and USB-C startup
dhh authored and merged omacom/omarchy-iso#409 into quattro. The configurator now creates its firmware-log directory before attempting Windows firmware staging and warns only about files not covered by packages in the offline mirror. Installation-time staging had remained functional. Expected early EFI-variable and DSP fallback messages are also quieted.
greptile-apps[bot] identified a counting error that could mistake a package-covered staged file for missing firmware being saved; its subsequent review says that error was fixed. Separately,
dhh committed the gpio-sbu-mux driver addition in omacom/omarchy-iso@521d68279485 to prevent Type-C startup retries on affected boards, and a 256 MiB live boot-image build limit in omacom/omarchy-iso@80178e491b70 to stop unchecked image growth.
AMD USB4 display workaround is reverted
dhh merged omacom/omarchy#18213 into quattro, reverting an AMD boot option committed earlier in omacom/omarchy@f24713c2352c. The option was intended to preserve the firmware's USB4 display link, but the revert reports that it instead left a Framework Desktop with an Apple Pro Display XDR black and required a non-USB4 cable to boot.
After the revert merged, greptile-apps[bot] warned that deleting the setup code did not remove the generated setting from existing installations. Its comment requests a rollback migration and verified boot-image rebuild. The supplied records establish the merged revert and that follow-up concern, without establishing a completed cleanup for affected installations.
Papers replaces Evince as the document viewer
dhh authored and merged omacom/omarchy#18200 into quattro. Papers becomes the PDF default and replaces Evince, removing the duplicate Document Viewer entries caused by Sushi already depending on Papers. Papers receives the existing floating-window treatment.
greptile-apps[bot] caught a migration problem with symlinked personal file associations.
dhh confirmed the migration now follows the symlink and updates its target. One capability changes with the replacement: the proposal notes that Papers does not open the PostScript, EPS or DVI formats Evince supported.
Sources
Glassy applies consistent opacity to every window
dhh authored and merged omacom/omarchy#18186 into quattro. Glassy now applies 0.75 opacity to all windows, including terminals, fullscreen windows and windows on floating workspaces, instead of visibly changing only Nautilus.
The change removes the additional transparent terminal backgrounds that previously compounded the window fade while retaining blur settings. dhh reported live checks across several applications and passing targeted tests; these are the author's verification reports.
ProArt P16 sleep proposal gains a second-machine comparison
The kernel proposal omacom/omarchy-pkgs#1958 remains open. jlobue10 reported controlled comparisons on a second H7607BA BIOS 303 machine: stock and control kernels woke almost immediately, while the proposed sleep patches sustained sleep, with two usable energy intervals around 1.55 W. These are contributor measurements on a specific configuration, not broad hardware qualification.
Proposer jibanez-staticduo documented provisional admission for 18-CPU models, retaining structural firmware checks while explicitly lacking physical testing of that SKU. Later,
jibanez-staticduo reported one successful mouse-triggered USB wake cycle after adding NVIDIA wake-route fixes.
RTC wake remains unresolved. Responding to jlobue10's captures,
jibanez-staticduo explained that a retained RTC timestamp reflects cached software state and does not independently prove a hardware timer was armed. The investigation narrowed toward timer command responses rather than assigning the failure to coordinated suspend or firmware.
Package promotion proposal checks destination dependencies
birkskyum opened omacom/omarchy-pkgs#2354 to refuse promotions that introduce unresolved dependencies before publishing packages. The open proposal checks the destination package set alongside its Arch snapshot, addressing cases where moving a kernel without its device-tree package could prevent users from updating.
emirb argued against automatic holdbacks and requested resolution against the channel snapshot.
birkskyum reported restoring refusal with an explanatory package name and adding snapshot resolution.
emirb then reported another mismatch with pacman's result and requested using pacman itself for before-and-after checks.
greptile-apps[bot] also flagged that checking only the final plan can miss broken intermediate publication batches. These discussions show the promotion safeguard is still under review, rather than an installed protection for channel updates.
Background Umami update publishes with a required legacy upgrade step
Background Umami's verification request omacom/omarchy-plugin-marketplace#14411 closed after publication. During review, samjage accepted that the shell could open a previously selected legacy image before asynchronous plugin cleanup ran, and challenged the lack of a reproducible startup-ordering test.
samjage then moved cleanup into the installer and made it mandatory for upgrades from 0.1.7 or earlier, with the shell stopped before installation.
HANCORE-linux accepted the exact revised commit under that documented upgrade path, explicitly without claiming an automatic startup barrier.
github-actions[bot] reported the update published with maintainer-reviewed verification. That verification applies to the marketplace snapshot and is not a security audit. Users of affected older versions must follow the required pre-startup cleanup procedure.
Global workspace toggle addresses monitor numbering regressions
ShaneHeldsinger's omacom/omarchy#17868 remains open and proposes an optional global workspace mode while retaining per-monitor numbering as the default.
littleme02 reported that changed numbering broke monitor pins and a custom workspace widget on a three-monitor setup.
ShaneHeldsinger responded that the setting is read before renumbering and that switching to global moves workspaces above 10 into available numbers from 1 through 10. After
greptile-apps[bot] flagged workspace creation on the wrong monitor,
ShaneHeldsinger reported adding monitor focus before creating an unused workspace.
The proposal still documents limitations: switching modes can change which saved layout a workspace inherits, and excess workspaces remain above 10 when all ten numbers are occupied.
Isolated AI compartment proposal absorbs its companion stack
TerexitariusStomp opened omacom/omarchy#18129 for VM-based AI compartments with local inference, constrained guest commands, request filtering and a networkless signing VM. It remains an open proposal. The author reports checks on an existing provisioned system but says a complete fresh-system installation was not tested.
chessing234 demonstrated that the initial installer could proceed toward privileged execution from an unverified companion checkout after a failed fetch.
TerexitariusStomp first described pinned staging, then replaced that design by incorporating the compartment stack into Omarchy itself.
greptile-apps[bot] subsequently identified first-boot provisioning problems. Its final summary says the latest change addressed the first-boot finding and appeared safe to merge. That source-review assessment does not establish a completed fresh-system installation or a merged feature.
Wi-Fi timezone proposal receives field feedback and a race fix request
dhh's open proposal omacom/omarchy#17234 offers opt-in timezone detection from nearby Wi-Fi rather than a VPN's apparent location.
emirb reported end-to-end operation on an XPS 16 through the IP fallback, while noting that access-point filtering discarded the networks BeaconDB knew locally.
chessing234 requested changes after reproducing a network-switch race that could save one access point's detected zone against another.
chessing234 then reported a fix in a separate proposal and passing timezone tests, while disclosing failures elsewhere in the full test run.
isc suggested retaining rounded Wi-Fi coordinates for weather auto-detection, describing large errors from IP-based location. That remains a discussion suggestion; the supplied records establish neither its adoption nor a merge of automatic timezone detection.
