OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input medium very-common DISPUTE

Volume, mute and brightness keys do nothing on a bare Hyprland session

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

Core fix verified end to end. Local Binds.md confirms hl.bind flag names locked ("Will also work when an input inhibitor (e.g. a lockscreen) is active") and repeating ("Will repeat when held"), and the wiki's own volume-key example is nearly identical to this record's. hyprlang bindel/bindl letters are correct. basecamp/omarchy/dev/default/hypr/bindings/media.lua exists and does ship these binds with { locked = true }/repeating = true, confirming this bites bare Hyprland not Omarchy. Omarchy 4's user override file ~/.config/hypr/bindings.lua exists in config/hypr. Arch packages wireplumber, brightnessctl, playerctl, wev, swayosd all in extra (swayosd 0.3.2, ships /usr/lib/systemd/system/swayosd-libinput-backend.service). The brightnessctl/logind claim checks out: the Arch PKGBUILD builds and installs with make ENABLE_SYSTEMD=1 only and never passes INSTALL_UDEV_RULES, so no udev rules are shipped and writes go through logind, requiring an active seat session. ONE defect: the swayosd block enables only swayosd-libinput-backend.service, which upstream documents as *optional* (caps/num/scroll-lock notifications). The component that actually draws the OSD is swayosd-server, which must be running in the compositor session. As written, swayosd-client --output-volume raise will silently do nothing.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

Fresh Arch/EndeavourOS/CachyOS + Hyprland install: the laptop's volume up/down, mute, mic-mute, play/pause and screen-brightness keys do absolutely nothing. No OSD, no change. wpctl get-volume @DEFAULT_AUDIO_SINK@ prints the same number before and after pressing the key, and brightnessctl get never moves. Audio itself works fine from pavucontrol and the same keys worked in GNOME/KDE. A variant: the keys work on the desktop but stop working the moment hyprlock is up.

Cause

Hyprland is a bare compositor and ships no default keybinds at all. XF86AudioRaiseVolume, XF86AudioMute, XF86MonBrightnessUp etc. are just keysyms until you bind them yourself, and there is no DE settings daemon (gnome-settings-daemon, powerdevil) listening for them. Two follow-on gotchas: a bind without the repeating flag fires once per press instead of repeating while held, and a bind without the locked flag is swallowed while an input inhibitor (hyprlock) is active, which is why volume keys 'stop working on the lock screen'. Omarchy already ships these binds in default/hypr/bindings/media.lua, so this bites bare Hyprland and DIY installs rather than Omarchy.

Fix

Replace the swayosd paragraph with:


sudo pacman -S --needed swayosd
# OPTIONAL: only for caps-lock / num-lock / scroll-lock OSDs
sudo systemctl enable --now swayosd-libinput-backend.service

The OSD is drawn by swayosd-server, which must be running in your Hyprland session. Without it swayosd-client does nothing. Autostart it:


-- Hyprland 0.55+ (~/.config/hypr/hyprland.lua, or Omarchy 4 ~/.config/hypr/autostart.lua)
hl.exec_once("swayosd-server")

# Hyprland 0.54 and older
exec-once = swayosd-server

Then point the binds at swayosd-client instead of wpctl/brightnessctl, keeping the same flags:


hl.bind("XF86AudioRaiseVolume", hl.dsp.exec_cmd("swayosd-client --output-volume raise"), { repeating = true, locked = true })
hl.bind("XF86AudioMute",        hl.dsp.exec_cmd("swayosd-client --output-volume mute-toggle"), { locked = true })
hl.bind("XF86MonBrightnessUp",  hl.dsp.exec_cmd("swayosd-client --brightness +5"), { repeating = true, locked = true })

Verify with systemctl --user status swayosd-server or pgrep swayosd-server before assuming a bind is broken. (On Omarchy, swayosd-server is already autostarted and omarchy-restart-swayosd restarts it.)

Verify

Run wev, press each key, and confirm the keysym matches what you bound. Then press volume up and check wpctl get-volume @DEFAULT_AUDIO_SINK@ changes. Press brightness up and check brightnessctl get changes. Lock the screen with hyprlock and confirm the volume keys still work. That proves the locked flag took effect.

Sources

media-keys-volume-brightness-not-bound-hyprland