OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services low occasional DISPUTE

Restore audio tweaks that stopped working after the WirePlumber 0.5 config change

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

Pinned the version claim, which is the whole record. Installed here is wireplumber 0.5.15-1 with pipewire 1:1.6.8-1 on omarchy 4.0.2-1. Checked upstream's own docs at tag 0.5.15 rather than a forum post: docs/rst/daemon/configuration/conf_file.rst states "the Lua configuration files are no longer supported" and adds the nuance the record omitted, that Lua remains the scripting language and is only gone for configuration. That holds, and 72 .lua files still ship per pacman -Ql wireplumber. All three worked examples verify against upstream's own shipped examples in /usr/share/doc/wireplumber/examples/wireplumber.conf.d/: alsa.conf carries session.suspend-timeout-seconds annotated "0 disables suspend" in the node rules block, device.disabled in the device rules block and node.description in the node block, and bluetooth.conf carries bluetooth.autoswitch-to-headset-profile under wireplumber.settings. wpctl settings on this machine lists that key and wpctl settings --help documents -s, --save, so the settings-versus-config split is confirmed live. The shadowing claim I nearly marked wrong and did not, which is worth recording: upstream's docs/rst/daemon/locations.rst says fragments load from all locations and merge, which reads as a contradiction, but the implementation in lib/wp/base-dirs.c at 0.5.15 removes a same-named entry already collected from a lower priority directory under the comment "so that lower priority files can be shadowed". The record and the Arch wiki are right and upstream's prose is the misleading part, so that text and its danger clause are kept. Alphanumeric ordering is also confirmed, via conffile_iterator_item_compare on filename. Four defects. (1) The central framing was stale by fourteen point releases. NEWS.rst for 0.5.1 records "Added a check that prints a verbose warning when old-style 0.4.x Lua configuration files are found in the system. (#611)", and src/main.c at 0.5.15 has warn_about_deprecated_config() emitting wp_notice("Old configuration file detected: %s") per file then wp_warning("Lua configuration files are NOT supported in WirePlumber 0.5..."). Both strings are in the installed binaries, confirmed here with strings /usr/bin/wireplumber and strings /usr/lib/libwireplumber-0.5.so.0.515.0. So "ignored without any warning" and "There is no error" are false on every version anyone runs today, and the record was withholding the one journal line that identifies the problem. Rewrote cause and symptom around it. (2) The cleanup step removed main.lua.d and bluetooth.lua.d but not policy.lua.d, which warn_about_deprecated_config also scans, so the warning would have persisted. (3) The danger's first sentence was wrong and contradicted the record's own cited source. lib/wp/conf.c catches a fragment that fails to load with wp_warning_object then continue, so the daemon starts and only that fragment is skipped. bbs 305957, cited on the record, shows exactly that: the user's fragment failed to load and they still had a working graph. The quoted string section '...' has no value is genuine, confirmed in lib/wp/conf.c, so it is kept. Only a broken main wireplumber.conf is fatal. (4) Omarchy content was missing and it matters here, because Omarchy already ships a fragment into the exact directory the record tells the reader to create. ~/.config/wireplumber/wireplumber.conf.d/bluetooth-a2dp-autoconnect.conf exists on this machine, is byte identical to /usr/share/omarchy/config/wireplumber/wireplumber.conf.d/bluetooth-a2dp-autoconnect.conf per diff, and pacman -Qo reports no package owns it. On ASUS hardware /usr/share/omarchy/install/user/hardware/asus/fix-audio-mixer.sh copies alsa-soft-mixer.conf there too. Given the shadowing rule the record correctly documents, those two names must not be reused and must not be deleted, and nothing would restore them. Also confirmed /etc/wireplumber/ does not exist here, so the old sudo rm -rf /etc/wireplumber/main.lua.d was a blind recursive root delete of a normally absent path, which the first auditor flagged in audit_note and nobody acted on. Replaced with a guarded listing. Set corrected_frequency to occasional. common dated from the April 2024 transition, but Omarchy 4 has shipped 0.5.x from the start, so no fresh Omarchy install can reach this state and only someone carrying an old dotfiles or /etc audio config onto the machine hits it. severity low left alone, the consequence is reverted tweaks rather than lost audio. Sources all four resolve with HTTP 200 and each supports what it is cited for, so nothing removed. bbs 294454 is the verbatim origin of the suspend-timeout example and, being dated 2024-04-01 against 0.5.0, is also where the stale no-warning claim came from. NOT exercised: I did not create any fragment, did not restart wireplumber, did not run wpctl settings --save, and could not make the deprecation warning appear because there are no *.lua.d directories on this machine. The warning's existence and wording come from the installed binaries and the 0.5.15 source, not from observing it fire.

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

A .conf fragment that fails to parse is not fatal. WirePlumber logs failed to open '<path>': section '...' has no value and skips that one file, so the daemon still starts and you still have audio. The failure mode is that your tweak silently does not apply, which looks exactly like the problem you were fixing, so read the journal after every change rather than trusting that audio still works. Only a broken main wireplumber.conf stops WirePlumber from starting, and following this record you write fragments, not that file.

Add one fragment at a time and restart WirePlumber after each. Reusing the exact filename of a fragment that already exists in a lower priority directory drops that file rather than merging with it, which silently removes the stock rules it contained and can disable device handling you still need. On Omarchy the two names to avoid are bluetooth-a2dp-autoconnect.conf and alsa-soft-mixer.conf in ~/.config/wireplumber/wireplumber.conf.d/, which Omarchy installs itself and which no package owns, so nothing will put them back.

Symptom

Custom audio behaviour silently reverted after an update: devices suspend again after a few seconds of silence, a disabled HDMI output is back, a renamed device shows its original name, or a headset auto-switch tweak stopped applying. Audio otherwise works and systemctl --user status wireplumber is active, so nothing looks broken. ~/.config/wireplumber/main.lua.d/ still contains the .lua files that used to do it.

The journal is where it shows up. WirePlumber 0.5.1 and later log one line per stale file plus a summary, so check there first:


journalctl --user -u wireplumber -b --no-pager | grep -iE "old configuration|NOT supported"

Old configuration file detected: /home/you/.config/wireplumber/main.lua.d/51-disable-suspension.lua
Lua configuration files are NOT supported in WirePlumber 0.5. You need to port them to the new format if you want to use them.

If those lines are absent and a tweak still is not applying, the cause is something else and this record does not apply.

Cause

WirePlumber 0.5 dropped Lua as a configuration language. Fragments in main.lua.d/, policy.lua.d/ and bluetooth.lua.d/ (under ~/.config/wireplumber/, /etc/wireplumber/ or /usr/share/wireplumber/) are no longer read, so every tweak you had reverts to stock behaviour. Configuration is now SPA-JSON files in a wireplumber.conf.d/ directory. Lua is still WirePlumber's scripting language and 72 .lua scripts ship in /usr/share/wireplumber/scripts/, so the presence of Lua on the system is not the issue. Only Lua *configuration* is gone.

The change is not silent on any currently shipping version. 0.5.0 ignored the old files with no message, and 0.5.1 added a check that walks those three directories and logs Old configuration file detected: <path> per file followed by Lua configuration files are NOT supported in WirePlumber 0.5. Anything from 0.5.1 onwards tells you, in the journal, if you look. Omarchy 4 ships wireplumber 0.5.15-1, so the warning is always present there.

Fix

Confirm the version and find the stale files:


wireplumber --version
ls -d ~/.config/wireplumber/*.lua.d /etc/wireplumber/*.lua.d 2>/dev/null
journalctl --user -u wireplumber -b --no-pager | grep -iE "old configuration|NOT supported"

Rewrite each tweak as SPA-JSON under wireplumber.conf.d/. On Omarchy that directory already exists and already holds a file Omarchy put there, so list it before you add anything:


ls -l ~/.config/wireplumber/wireplumber.conf.d/
mkdir -p ~/.config/wireplumber/wireplumber.conf.d

Old 51-disable-suspension.lua becomes:


# ~/.config/wireplumber/wireplumber.conf.d/51-disable-suspension.conf
monitor.alsa.rules = [
  {
    matches = [
      { node.name = "~alsa_input.*" }
      { node.name = "~alsa_output.*" }
    ]
    actions = {
      update-props = {
        session.suspend-timeout-seconds = 0
      }
    }
  }
]

Disabling a device (for example GPU HDMI audio). Find the stable identifier first:


wpctl status
wpctl inspect <ID>        # use device.name or node.name, never device.id

# ~/.config/wireplumber/wireplumber.conf.d/50-alsa-disable.conf
monitor.alsa.rules = [
  {
    matches = [
      { device.name = "alsa_card.pci-0000_08_00.4" }
    ]
    actions = {
      update-props = {
        device.disabled = true
      }
    }
  }
]

Match a device property and you set device.disabled. Match a node property and you set node.disabled instead.

Renaming a device:


# ~/.config/wireplumber/wireplumber.conf.d/50-rename.conf
monitor.alsa.rules = [
  {
    matches = [
      { node.name = "alsa_output.pci-0000_00_1f.3.analog-stereo" }
    ]
    actions = {
      update-props = {
        node.description = "Laptop speakers"
      }
    }
  }
]

Things that used to be Lua *settings* are now runtime settings. Set them with wpctl rather than a config file. wpctl settings with no argument lists every settable key with its description:


wpctl settings
wpctl settings --save bluetooth.autoswitch-to-headset-profile false

Apply and check:


systemctl --user restart wireplumber.service
journalctl --user -u wireplumber -b --no-pager | tail -20
wpctl status

Then remove the dead Lua fragments so the warning stops and they stop confusing you later. There are three directories, not two, and policy.lua.d is the one usually forgotten:


rm -rf ~/.config/wireplumber/main.lua.d \
       ~/.config/wireplumber/policy.lua.d \
       ~/.config/wireplumber/bluetooth.lua.d

/etc/wireplumber/ does not exist on a stock Omarchy 4 install, so there is normally nothing to clean up system-wide. Check before reaching for rm -rf as root, and look at what is in there rather than deleting the directory blind:


ls -R /etc/wireplumber/ 2>/dev/null || echo "no /etc/wireplumber, nothing to do"

Two file layout rules matter. Within each wireplumber.conf.d/ directory files load in alphanumeric order, and across directories the fragments are collected lowest priority first (/usr/share/wireplumber, then /etc/wireplumber, then ~/.config/wireplumber). A fragment whose *filename* already exists in a higher priority directory is dropped in favour of the higher priority one rather than merged with it, so ~/.config/wireplumber/wireplumber.conf.d/50-alsa-config.conf replaces /usr/share/wireplumber/wireplumber.conf.d/50-alsa-config.conf entirely. Give your own files distinct names.

On Omarchy that rule has two live names to avoid. Omarchy copies bluetooth-a2dp-autoconnect.conf from /usr/share/omarchy/config/wireplumber/wireplumber.conf.d/ into ~/.config/wireplumber/wireplumber.conf.d/, and on ASUS hardware /usr/share/omarchy/install/user/hardware/asus/fix-audio-mixer.sh copies alsa-soft-mixer.conf there too. Neither is owned by a package. Do not reuse either name and do not delete them while cleaning up, or you drop Omarchy's A2DP auto-connect rule or its ALSA soft-mixer rule.

Verify

journalctl --user -u wireplumber -b shows no config parse errors, wpctl inspect <ID> reflects your changed property, and the behaviour you wanted (no suspend, device hidden, new name) is back after a reboot.

Sources

wireplumber-lua-config-ignored-after-0-5