$ the-wire · showcase
Tracing merge lands as late-arriving displays and failed commands get fixed in Omarchy
By RepoJournal · Filed · About Linux · Composed from the cited sources · methodology
2 people shipped this
Linus merged the tracing pull for v7.3-rc2 and a batch of urgent entry, IRQ, objtool, and perf fixes, while Omarchy closed two long-standing presentation bugs and retired a CODEOWNERS file that never enforced anything.
Merge tag 'trace-v7.3-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace torvalds/linux
The tracing pull for v7.3-rc2 reorders teardown so user event fields are destroyed only after the event is successfully removed from visibility, closing a window where a failed removal left a still-visible event with no fields. Function graph state is also initialized before the call in fork.
Show a failure state when a presented command exits non-zero basecamp/omarchy
The floating-terminal wrapper used to print the green "Done!" prompt for every exit code except Ctrl-C, so a failed update or channel switch closed looking like a success. It now passes the exit code through to omarchy-show-done and renders red "Failed (exit code N)!" on non-zero, and the pkg install and remove pickers got the same treatment.
Re-center the Plymouth prompt when a display appears late (#11641) basecamp/omarchy
Plymouth's theme laid out the logo, password entry, and progress bar once at startup, while Plymouth sizes its window to the largest display present, so a Thunderbolt display, dock, or MST hub that comes up after plymouthd started had its prompt drawn at the internal panel's coordinates. The prompt is now re-centered when a display appears late.
Merge tag 'core-urgent-2026-09-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip torvalds/linux
Ingo Molnar's entry fix guards the syscall_enter_audit() invocation with CONFIG_AUDITSYSCALL, repairing a generic entry code cross-build failure on !CONFIG_AUDITSYSCALL kernels using older RISCV64 and S390 cross-compilers. The IRQ, objtool, and perf pulls in the same batch fix gic-v5 corrupting unrelated ICC_CR0_EL1 state, KLP checksum false positives under GCC, and sched_cb_list corruption dur...
Keep the conflict tests inside their fixture despite the scope wrapper basecamp/omarchy
The update conflict tests stub sudo and pacman, but omarchy-update-pacman now sits systemd-run between them, so on a systemd-booted host the tests would reach for the real system manager; systemd-run is now stubbed. Removing CODEOWNERS would follow, since no branch is protected and it only auto-requested reviews nobody acted on.
