waybar network widget hardcoded to iwd — errors for adopters #4

Open
opened 2026-06-29 03:03:02 +00:00 by padreug · 0 comments
Owner

Problem

The waybar network module (its on-click / associated tool) is wired to iwd, because the maintainer's own machine runs iwd. Adopters — who get no iwd from core (see the no-wifi-backend issue) — see:

Can not access the iwd service.
Error: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

when interacting with the network icon. The wifi may still work via nmcli/nm-applet, but the bar's network control is broken.

Impact

Low — cosmetic / UX; doesn't block networking once a backend is enabled. But it's confusing and reinforces the "Omnixient assumes iwd but ships no backend" inconsistency.

Suggested fix

Make the network widget backend-agnostic, or align it with whatever backend core enables (NetworkManager, per the no-wifi-backend issue) — e.g. on-click opens nm-connection-editor / a NetworkManager menu instead of an iwd tool.

Found while helping a friend adopt the template on existing NixOS.

## Problem The waybar network module (its on-click / associated tool) is wired to **iwd**, because the maintainer's own machine runs iwd. Adopters — who get no iwd from core (see the no-wifi-backend issue) — see: ``` Can not access the iwd service. Error: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable ``` when interacting with the network icon. The wifi may still work via `nmcli`/`nm-applet`, but the bar's network control is broken. ## Impact Low — cosmetic / UX; doesn't block networking once a backend is enabled. But it's confusing and reinforces the "Omnixient assumes iwd but ships no backend" inconsistency. ## Suggested fix Make the network widget backend-agnostic, or align it with whatever backend core enables (NetworkManager, per the no-wifi-backend issue) — e.g. on-click opens `nm-connection-editor` / a NetworkManager menu instead of an iwd tool. Found while helping a friend adopt the template on existing NixOS.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aiolabs/omnixient#4
No description provided.