Repository navigation
Tags
Tags
Stop re-sampling the wallpaper for the transparent bar on unrelated s… …tate writes (omacom#8307) (omacom#16799) * Stop re-sampling the wallpaper for the transparent bar on unrelated state writes The bar watched ~/.local/state/omarchy/current for background changes. A directory path never sits in QFileSystemWatcher's file set, so Quickshell's FileView re-emitted fileChanged for every entry created, renamed or removed in ~/.local/state/omarchy as well. Any plugin writing there atomically (tmp + rename) re-ran omarchy-bar-text-color, and on a 5K display that ImageMagick pass cost ~2.6 core-seconds across every thread. One plugin saving every 10 s held ~40% of a core for the whole session, invisible in quickshell's own CPU figure because magick is a reaped grandchild. Watching the symlink directly does not work: inotify follows it to the old image and ln -nsf never touches that inode. Keep the directory watch, resolve the link with readlink -f and only refresh when the wallpaper actually moved. Sample at a reduced scale in omarchy-bar-text-color too. The strip is averaged to one pixel, so shrink the geometry by an integer factor (never upscale) and let the JPEG decoder skip the detail: 2.58 -> 0.065 core-seconds per sample on a 2912x1632 JPEG at 5120x2160, same result. * Resolve the background link at startup and cover the watcher in the runtime smoke test FileView reports no change for its initial load, so without a baseline the first unrelated write in the state directory still compared against "" and sampled once. Run the probe when the bar starts. The smoke test now stubs omarchy-bar-text-color and counts calls in the running shell: turning transparency on samples once, an atomic write of an unrelated file in ~/.local/state/omarchy does not sample again, and repointing current/background does. Against the previous Bar.qml the unrelated write registers as a second sample and the test fails. * Drop the reduced-scale helper tests, which omacom#14281 covers The merge took quattro's omarchy-bar-text-color, whose 1920px canvas, JPEG size hint and resource caps from omacom#14281 already bound the sample this branch shrank, so its tests for the old downscale go with it. * Watch inside current/ so unrelated state writes do not re-sample the bar FileView watches its path's parent directory too, and re-emits fileChanged for every entry created, renamed or removed there whenever the path itself is not a watched file. Watching ~/.local/state/omarchy/current made that parent ~/.local/state/omarchy, which plugins write to constantly, so the transparent bar re-ran ImageMagick on every unrelated save. Watching current/theme moves the parent to current/, where omarchy-theme-set swaps the theme and omarchy-theme-bg-set repoints the background link, and both still arrive. This replaces a readlink probe that resolved the link on every event: no extra process, and a theme switch that lands on a same-named background still re-samples. --------- (cherry picked from commit bc220e7) Co-authored-by: Ryan Yogan <ryanyogan@gmail.com> Co-authored-by: Omarchybot <317366263+omarchybot@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Codex Medium <noreply@openai.com>
Merge pull request omacom#15932 from omacom/notifications-omapager Replace the notification engine with Omapager
Route links from every app through the running default browser (omaco… …m#14441) * Focus the matching window used last when several match A browser hands a new tab to the window that was focused last, so that is the one to bring forward. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Route links from every app through the running default browser Electron apps open links through the desktop portal, which runs the default browser's desktop entry without an activation token, so the window that took the tab stays out of sight. A Hyprland-specific mimeapps list now points http and https at omarchy-browser.desktop, which opens them through omarchy-launch-browser to hand them over and focus the window. The browser itself stays in mimeapps.list, where xdg-settings and the browsers keep it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Stop browsers asking to be the default behind the link routing Links reach the browser through omarchy-browser.desktop, so the browser's own check finds another handler in front of it and asks to be made the default. Chromium-family browsers skip that check with --no-default-browser-check, which the hand-off accepts as one of Omarchy's own flags, and a managed DefaultBrowserSettingEnabled=false policy hides the button that would rewrite mimeapps.list behind Omarchy's back. Firefox and Zen get the DontCheckDefaultBrowser policy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 9f49906)
Merge pull request omacom#11901 from omacom/fix/v4-0-4-complete-kerne… …l-headers Treat kernel headers as part of the 4.0.4 base system
Credit @Chainfire for the asdcontrol security report Chainfire (@Chainfire) privately reported the passwordless asdcontrol watchdog reboot on August 25, 2026. The fix landed in the 4.0.2 security work: omacom#9200 (df819a6) removed Omarchy's unrestricted sudo grant, while omacom/omarchy-pkgs#242 and omacom/omarchy-pkgs#243 restricted the package's grant. This records the reporter credit omitted from those changes. Reported-by: Chainfire (https://github.com/Chainfire) (cherry picked from commit 5b91db5)
PreviousNext