OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network high very-common DISPUTE

Fix the Wi-Fi password prompt that never appears on Hyprland

omarchyarchendeavouroscachyosmanjarolaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The problem is real and the generic Arch half is verbatim-correct, but three Omarchy 4 / Hyprland 4 specifics are fabricated, and the cause conflates two different agents. Checked on the live Omarchy 4.0.0 install. (1) omarchy-shell.service does not exist as a user unit: systemctl --user cat omarchy-shell.service returns "No files found", there is no such file in /usr/lib/systemd/user, and worse, omarchy-shell.service is listed in the retired_user_units array of /usr/bin/omarchy-upgrade-to-quattro and actively deleted from ~/.config/systemd/user. The shell is started from Hyprland's autostart (hl.exec_cmd("omarchy-launch-shell") in /usr/share/omarchy/default/hypr/autostart.lua) and restarted with omarchy-restart-shell (omarchy restart shell). (2) hl.exec_once(...) is not a Hyprland Lua API. The hyprland-wiki page content/configuring/core/autostart.md shows the only documented form is hl.on("hyprland.start", function() hl.exec_cmd("...") end), and strings /usr/bin/Hyprland on 0.56 has exec_cmd but no exec_once (only the legacy hyprlang keyword exec-once). (3) busctl --user list | grep -i polkit is a false-negative diagnostic: on this healthy machine, with the Quickshell polkit plugin loaded (/usr/share/omarchy/shell/plugins/polkit/PolkitAgent.qml, import Quickshell.Services.Polkit), that command matches nothing, so it would tell a user their agent is dead when it is fine. (4) The cause is wrong about mechanism. A NetworkManager *secret agent* (org.freedesktop.NetworkManager.AgentManager) and a *polkit* agent are different things. Omarchy 4 ships the latter but registers no secret agent. Its network panel collects the passphrase itself and hands it to nmcli (see /usr/share/omarchy/shell/plugins/panels/network/Model.js, which builds nmcli connection add ... | nmcli connection edit uuid ... with the password on stdin). Verified as correct and kept: the error strings (Arch wiki NetworkManager: "If you make neither of these available, then authentication will fail with the error no secrets: No agents were available for this request.", and the i3 warning uses the same string), nmcli --ask and nmtui as their own agents, and psk-flags 0 = stored by NetworkManager in cleartext under /etc/NetworkManager/system-connections plus that danger note. Also kept: the polkit rules snippet, which is character-for-character the wiki's 50-org.freedesktop.NetworkManager.rules with subject.isInGroup("network"), the Hyprland wiki listing an Authentication Agent under Must-have with "Starting method: manual (autostart in config)" and hyprpolkitagent's own page giving systemctl --user start hyprpolkitagent in autostart and systemctl --user enable --now hyprpolkitagent.service under uwsm, and the claim that Quattro retires hyprpolkitagent.service, which is true (it heads the retired_user_units list).

The cause above was rewritten on 2026-09-01 to match this note; the fix was corrected by the audit itself.
RISK

psk-flags 0 writes the passphrase in clear text into /etc/NetworkManager/system-connections/<name>.nmconnection, readable by root and by anything that can read that directory. That is the normal Arch default, but do not do it for shared machines or for corporate credentials. The polkit rules file grants every member of network unprompted control over all NetworkManager settings including VPN configuration. Only add users you would give sudo to.

Symptom

Clicking a secured network in the bar does nothing. No password dialog ever opens and the connection silently fails. From the terminal: Error: Connection activation failed: (7) Secrets were required, but not provided. The journal shows no secrets: No agents were available for this request. or Failed to request VPN secrets #1: No agents were available for this request. Anything else that needs elevation (mounting a disk in a file manager, pkexec) also fails without prompting.

Cause

NetworkManager does not prompt for Wi-Fi secrets itself. Unless the passphrase is stored in the profile, it asks a registered *secret agent* in your session for it, and if none has registered it gives up immediately with error 7 and logs no secrets: No agents were available for this request. A full desktop environment's shell provides one. A bare Hyprland session provides neither a secret agent nor a polkit authentication agent unless you start one. Omarchy 4 is a third case, and it is not the same mechanism: it registers **no** NetworkManager secret agent at all. Its network panel (part of the omarchy-shell Quickshell process that also draws the bar) collects the passphrase in its own dialog and passes it straight to nmcli, and a separate Quickshell plugin provides the **polkit** agent for pkexec and friends. Both live in that one process, so if omarchy-shell has crashed or is restart-looping you lose the Wi-Fi dialog and every privilege prompt on the machine together, but you will not see the NetworkManager "no agents" error from clicking the bar, because the bar never asked NetworkManager for secrets in the first place. You get that error from nmcli without --ask, from a VPN plugin, or on a bare Hyprland session with no agent running. Note also that Omarchy 4 retires the standalone hyprpolkitagent.service user unit during the Quattro upgrade, so a stale enabled copy of it is not what is answering.

Fix

Confirm the diagnosis rather than guessing at the password:


journalctl -u NetworkManager -b --no-pager | grep -i 'secret\|agent' | tail -20
pkexec true          # should raise a password dialog; fails silently if no polkit agent

Do not use busctl --user list | grep -i polkit as the test. A working Quickshell or hyprpolkitagent agent owns no name on the user bus, so that matches nothing even on a healthy machine.

**Immediate workaround: no agent needed.** nmcli can be its own agent with --ask, and nmtui prompts in the terminal:


nmcli --ask device wifi connect "<SSID>"
# or
nmtui

**Omarchy 4.** The network panel and the polkit dialog both live in the omarchy-shell Quickshell process. There is no omarchy-shell.service user unit, because Quattro retires that name, so check and restart it this way:


pgrep -af quickshell                              # is the shell alive?
journalctl --user -t omarchy-shell -b | tail -40  # why it died, if it did
omarchy-restart-shell                             # same as: omarchy restart shell

omarchy-restart-shell is deliberately careful about the lock screen. Prefer it over killing the process by hand.

If a leftover pre-Quattro unit is still enabled and fighting it, clear it (this is exactly what the Quattro upgrade's own cleanup does):


systemctl --user disable --now hyprpolkitagent.service 2>/dev/null
rm -f ~/.config/systemd/user/hyprpolkitagent.service
systemctl --user daemon-reload

**Bare Hyprland / plain Arch.** Install and autostart an agent. The Hyprland wiki lists an authentication agent under "must have" with its starting method as manual, via an autostart entry in the config:


sudo pacman -S --needed hyprpolkitagent

Hyprland 0.55+ config is Lua, and there is no exec-once equivalent function. Autostart is an event handler. In ~/.config/hypr/hyprland.lua:


hl.on("hyprland.start", function()
  hl.exec_cmd("systemctl --user start hyprpolkitagent")
end)

If you launch Hyprland through uwsm, enable it as a proper user unit instead and drop the autostart line:


systemctl --user enable --now hyprpolkitagent.service

Note that a polkit agent alone does not make NetworkManager stop reporting "no agents". That error wants a *secret* agent. On a bare Hyprland session, either use nmcli --ask / nmtui, run a front-end that registers one (nm-applet, networkmanager-dmenu), or store the secret as below.

**Make the Wi-Fi password not need an agent at all.** Store it in the connection profile rather than in a keyring, so NetworkManager itself owns it (secret flag 0 = stored by NetworkManager):


nmcli connection modify "<SSID>" 802-11-wireless-security.psk-flags 0
nmcli connection modify "<SSID>" 802-11-wireless-security.psk '<password>'
nmcli connection up "<SSID>"

**If the prompt appears but is refused**, it is polkit authorisation rather than agent absence. Add yourself to network and grant it:


sudo usermod -aG network "$USER"
sudo tee /etc/polkit-1/rules.d/50-org.freedesktop.NetworkManager.rules >/dev/null <<'EOF'
polkit.addRule(function(action, subject) {
  if (action.id.indexOf("org.freedesktop.NetworkManager.") == 0 && subject.isInGroup("network")) {
    return polkit.Result.YES;
  }
});
EOF

Log out and back in for the group change to take effect.

Verify

nmcli device wifi connect "<SSID>" on a network whose password is not yet stored should pop a graphical prompt. busctl --user list | grep -i polkit shows an agent on the bus. pkexec true should prompt rather than fail silently.

Sources

no-secret-agent-wifi-password-prompt-never-appears