Kernel selection, graphical updates and stronger ARM boot coverage

01A proposed Kernel menu makes the default boot choice accessible

dhh opened omacom/omarchy#15966 to let users choose an installed kernel from Update > Kernel, with one authentication prompt and a notification offering to reboot. The open proposal rebuilds the selected kernel and checks that it leads the Limine menu; Direct Boot configurations are refused.

After greptile-apps[bot] raised overlapping-switch risks, dhh reported adding a lock across the operation in omacom/omarchy#15966:discussion_r4315153646. dhh also reported atomic configuration writes and rollback to the previous menu leader. A later review raised a display issue where an unambiguous wildcard default receives no checkmark in omacom/omarchy#15966:discussion_r4315436162.

02Terminal apps could inherit their terminal's touchpad scrolling

dhh proposed matching terminal apps with custom app IDs to their terminal's touchpad settings in omacom/omarchy#15972. Such windows currently miss class-based rules; dhh reported the console scrolling about five times slower than a plain foot terminal. The proposal remains open, with live-window property checks reported for foot, kitty, Alacritty and Ghostty.

03The update-window proposal tightens recovery and package reporting

GruperTal's graphical update and one-click installation proposal remains open in omacom/omarchy#15455, originally opened October 14. It presents package progress and authentication dialogs while allowing work to continue after the window closes. On October 19, GruperTal reported fixing abandoned runs that captured subsequent requests and returning OpenClaw's onboarding wizard to a terminal.

Locale handling was narrowed so parsed package and authentication messages use English while launched applications retain the session language. After greptile-apps[bot] warned that skipped AUR updates could receive completion checkmarks, GruperTal reported checking installed package versions instead in omacom/omarchy#15455:discussion_r4313657505.

04Omapager is proposed as the built-in notification engine

ryanrhughes opened omacom/omarchy#15932 to replace the notification engine with Omapager. Its current description, updated October 20, includes source stacks, snoozes, history, inline replies and KDE Connect, with image decoding inside networkless sandboxes and migration from the separate plugin.

During October 19 review, greptile-apps[bot] warned that a full persistence queue could lose dismissals and quiet settings in omacom/omarchy#15932:discussion_r4311280276. The bot's summary updated October 20 subsequently assessed the proposal as safe to merge and reported a demo replay fix. The PR remains open.

05Games could join the existing application launcher

michtesar proposed a Games category using local Steam and Heroic records in omacom/omarchy#15944. Games would share the existing grid and global search, while clients remain under Apps. Discovery requires no network access or additional dependency.

After greptile-apps[bot] identified shortcut-removal persistence problems, michtesar reported saving removal preferences before deletion and journaling interrupted cleanup. Discovery failures now receive a retry message while existing entries remain available, according to omacom/omarchy#15944:discussion_r4312402864. The PR remains open; running UI checks and real-client launch verification are still listed as outstanding.

06A failed kernel image build is reported to leave NVIDIA systems black

qrfeng opened omacom/omarchy#15921 after reporting that an update skipped a failed new-kernel image build, then booted an older image whose NVIDIA modules mismatched the updated userspace driver. qrfeng requested explicit failure reporting, module reindexing and version checks. The issue remains open.

aron-intframe challenged the proposed race explanation and supplied reproductions suggesting the expected module index write never happened. The responder also demonstrated how one successful image build could conceal another kernel's failure from the log analyzer in omacom/omarchy#15921:issuecomment-6259026463. n4zguu1 separately reported a similar black screen with a DKMS build failure and a successful snapshot boot.

07A stable-channel report renews concern over non-Latin disk unlocking

pkolbas reported a stable-channel 4.0.5 disk-unlock loop after an October 19 update in omacom/omarchy#15802:issuecomment-6271281736. The report attributes it to Plymouth bundling a non-Latin console layout into the boot image and requests reopening the issue until a fix reaches stable.

As background, giuseppecipollone opened omacom/omarchy#15802 on October 18 with the same reported mechanism, and emirb closed it that day. It remains closed at the current check. pkolbas reported recovery by putting the US console layout first and rebuilding the image; the supplied records do not establish that this report was resolved by a subsequent release.

08Edge publishing now carries the release candidate package pair

ryanrhughes committed a publishing change on the package repository's master branch in omacom/omarchy-pkgs@7f6ec980bde9. It carries the exact pinned package pair from rc into edge, with protection against moving edge backwards. The commit explains that separate builds had left edge on 4.0.4 when 4.0.5 could not find matching settings.

The first carry attempt failed because the builder could not write its directory; ryanrhughes committed a permission correction in omacom/omarchy-pkgs@aabd8f1f24cd. A separate master commit records Release omarchy 4.0.6 in omacom/omarchy-pkgs@61e6d13a3f46, without supplying release contents or channel-delivery confirmation.

09Hardware changes address N1x docks, Snapdragon cameras and fingerprint discovery

A package master commit by ryanrhughes changes N1x DMA protection handling so Bolt can authorize new docks without manual enrollment in omacom/omarchy-pkgs@a8f9d7512a7f. The commit reports successful testing with OWC and CalDigit docks on a ProArt P14.

On Omarchy's quattro development branch, birkskyum's camera change installs the libcamera PipeWire bridge for Qualcomm hardware and enables Chromium's camera feature in omacom/omarchy@b5f8593dfc92. scottjones's fingerprint change adds platform-declared reader detection, including usable Touch ID readers, while retaining USB detection in omacom/omarchy@81fd2d23ca6e. These commits do not establish stable-release availability.

10ISO checks exercise N1x firmware and VM kernel-update bootability

emirb committed stronger ARM installation checks on quattro. omacom/omarchy-iso@d2a0d47ed320 explains that earlier N1x checks could pass without exercising the installed system's N1x configuration. omacom/omarchy-iso@6edcc58cbf60 supplies the VM with the firmware signals Omarchy actually detects, rather than replacing its detector. ARM installation tests also switched to published edge packages.

A separate VM-image fix removes the build machine's identity from the Limine entry so clones update that entry correctly after kernel changes. emirb reported that the expanded checks failed on the published 4.0.5 image and passed after resealing with the change in omacom/omarchy-iso@bcc340933978. Its merge into quattro is recorded by omacom/omarchy-iso@fd1c9a549a9f; this is development-branch work.

11rwsm is proposed as a compatible session-manager replacement

yamz8 opened omacom/omarchy#15965 to install rwsm, a Rust rewrite of uwsm's executable, on fresh installations while retaining the interfaces Omarchy calls. The proposal depends on package publication and a package-reinstallation change. yamz8 reported a successful ISO installation and 50 login, launch and logout cycles; those are contributor-reported results. The PR remains open.

12OmaDroid is listed after text and app-inventory privacy fixes

github-actions[bot] confirmed OmaDroid's marketplace publication with maintainer-reviewed verification in omacom/omarchy-plugin-marketplace#12139:issuecomment-6279773090. mateuspim's submission includes Android integration with optional text sending and webcam setup.

HANCORE-linux identified private text in process arguments and later app-inventory exposure. mateuspim reported moving text through standard input, removing inventory data from awk arguments and tightening cache permissions. HANCORE-linux then confirmed the reported exposures were fixed and accepted the documented setup privileges in omacom/omarchy-plugin-marketplace#12139:issuecomment-6279679513. Verification applies to the listed snapshot and is not a security audit.