known issues, tracked in the open.

What's broken: in Microsoft Edge on Linux, the Copilot toolbar button is present but non-functional — clicking it does nothing. The feature works on other platforms, so this is a Linux-specific gap, not a disabled feature.

What we've done: submitted through Edge's built-in feedback system on 23 September 2026 with a screenshot, a screen recording, and a detailed write-up, identifying as a navi maintainer evaluating Edge as a reliable distro browser option. The full submission is logged in our public Edge-on-Linux feedback tracker.

Update — likely root cause: community reports indicate the Linux build ships without the HubApps profile file the Copilot sidebar needs — placing it in ~/.config/microsoft-edge/Default/ restores the sidebar. That reframes this from "button does nothing" to a Linux packaging gap, which is a much more actionable report. The same symptoms are tracked publicly at MicrosoftEdge/DevTools#278 across Mint, NixOS, Fedora, and Arch. We're folding both into our tracker. (We're not shipping the manual file-drop as a fix — downloading an unsigned profile file from a stranger's dotfiles repo is not something a distro should bless.)

Update — fixed in Dev, 11 October 2026: Raven installed Edge Dev to verify, and the Copilot button now works — the sidebar opens and functions normally. Whether our September feedback contributed to the fix is unknown (the Edge team's internal bug notes aren't visible to us), but the timing is suggestive. Stable channel still pending verification, per our own rule: a vendor fix isn't done until it's confirmed on real navi hardware.

What it blocks: nothing we ship — Edge is an evaluated option, not a default. But it matters for the evaluation: a flagship AI feature dead on arrival on Linux is exactly the kind of paper cut that keeps a browser out of a distro's recommendations.

What's broken: enabling Use system title bar and borders in Edge's appearance settings produces no visual change on Linux. The toggle exists, the window ignores it.

What we've done: submitted alongside EDGE-LINUX-001 on 23 September 2026, same evidence package, same public log. Two issues, one submission session.

What it blocks: desktop integration. navi is a coherent desktop; a browser that can't hand its window chrome to the system compositor is a browser that always looks slightly foreign. Small, visible, fixable.

What's happening: launching a mod while another window is already floating also centers the pre-existing window behind it. The likely cause is overly broad match criteria in mod-open.sh.

What we're doing: nothing, for now — deliberately. The common case (no floating window behind the launch) works correctly, and we'd rather not churn the launcher on a cosmetic edge case while bigger eiri work is in flight. It's documented here so nobody has to rediscover it.

What was happening: the volume OSD is a single-flight daemon, so replacing its script didn't replace the running server — the old code kept serving the old UI and a real fix looked broken on updated machines.

What we did: the daemon now self-retires stale servers — a pidfile carrying the script's code id, a client-side staleness check before connecting, and /proc cmdline verification before signaling anything.

Confirmed fixed on real hardware, 23 September 2026 — updates now show the new UI immediately.

What was new: waybar text and pill borders animate through the nightshadeNeon cycle — cyan to pink to green — with state cues (battery warnings, mute, idle inhibitor) keeping their solid colors via animation: none.

Confirmed fixed on real hardware, 23 September 2026 — working as expected and looking beautiful.

What was happening: on the Lenovo Ideapad L340, the firmware silently discarded the EFI NVRAM boot entry the installer wrote — the machine couldn't find navi at boot. Reported by community member programmervsworld (issue #5), whose diagnosis the team adopted.

What we did: the installer now also writes the --removable fallback (EFI/BOOT/BOOTX64.EFI), so machines whose firmware drops NVRAM entries still boot. Harmless on machines that keep their entries.

Confirmed fixed — issue closed 12 October 2026. This one also gave us our firmware quirk taxonomy: class-1 (NVRAM writes fine, BIOS picker needed — Cloudbook) vs. class-2 (firmware drops the entry — Ideapad).