Qt 6.12 blacks out the menu, Glassy windows land, and Xournal++ makes way for Signed

📦Releases & Changes

• Signed — Omacom's in-house PDF signer ships by default in place of Xournal++; upgrades install it via migration, and existing Xournal++ installs are left alone.

• ARM update flow — omarchy update on ARM machines no longer insists on a reboot after every single update.

• Session locking — Lock code now reads live lock state directly so suspend can't sleep an unlocked machine, and recovery waits instead of grabbing locks another locker may hold.

✨Features & Workflow

• Window Transparency — Appearance gains Transparent, Opaque and Glassy window modes, plus bar backgrounds you can cycle by double-clicking — clear, glassy or opaque.

• Window Corners — Appearance > Window Corners offers Sharp, Rounded (Solitude's corners) or Theme corners, and the choice survives a failed save.

• Bar clock format — Appearance > Menu Bar > Indicators > Clock lists every format the cycling clock uses, labelled by how it reads, current one checked.

• Tray drawer — Bar widgets can now be parked inside the tray's drawer — drag one onto the tray — and plugins can adopt that spot by default.

🎨Themes & Ricing

• Theme-intro wallpaper fix — Switching to a theme with an intro animation could leave the desktop bare: the shell got the new wallpaper only when the intro failed, and otherwise kept a path the swap had deleted. The image is now handed over in both cases, and the shell re-checks the background link whenever the desktop returns or a load fails. A dead link falls back to the theme's first background. GitHub

• Tokyo Night background migration — Liftoff's move to the front of Tokyo Night renumbered every other wallpaper, so a 4.0.x upgrade pointed at a file that no longer existed and quietly dropped you onto Liftoff. A new migration remaps such picks to the one background with the same name under a different number, for the current background and each theme's remembered choice. Wallpapers that still load, ones you added yourself, symlinks and picks without a unique match are all left alone. GitHub

🗣DHH & Direction

• I'm sorry, but you still have to think — Piotr Sarnacki dissects DHH's AI-written Campfire rewrites in Rust and Elixir: each answered unspecified trade-offs differently (the Rust one drops the CSRF token), and throughput benchmarks hid a 1% notification delivery rate under load. Relevant if you follow DHH's agent-heavy direction: someone still has to read the code a clanker writes. Widening the Rust broadcast channel from 256 to 16384 lifted delivery at 100 req/s from roughly 14% to roughly 90%, but pushed worst-case latency from 11 seconds to over 130. itsallaboutthebit.com

💡Worth Trying