Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-958GitHub issuePublicDecided· Out of scope

Stock install does not expose AirPlay / HomePod speakers

Reported by ruttydm · filed Sep 4, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Stock install does not expose AirPlay / HomePod speakersrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Intel i7-1185G7, Intel Iris Xe, Omarchy 4.0.2-1

What's wrong?

Stock install does not expose AirPlay / HomePod speakers

Component: defaults / PipeWire
Severity: minor (local speakers and Bluetooth work; AirPlay speakers on the LAN never appear)

Summary

On a stock Omarchy install, HomePods and other AirPlay receivers on the same Wi-Fi never show up as audio outputs. Avahi is already installed and the speakers are advertising _raop._tcp / _airplay._tcp, but PipeWire cannot talk to them.

Two pieces are missing:

  1. pipewire-zeroconf is not in the default package set. On Arch this is a split package that contains libpipewire-module-raop-discover and libpipewire-module-raop-sink. Omarchy already installs pipewire, pipewire-alsa, pipewire-jack, and pipewire-pulse in install/omarchy-other.packages, but not this one.
  2. PipeWire already ships /usr/share/pipewire/pipewire.conf.avail/50-raop.conf to load that module. Nothing in Omarchy enables it.

Omarchy already auto-connects Bluetooth A2DP so speakers appear without a manual PipeWire recovery. AirPlay is the same class of gap: the rest of the stack (PipeWire, Avahi, mDNS) is present, and the RAOP module is one package plus one drop-in away.

Expected

HomePods / AirPlay speakers on the LAN appear in the audio output list, the same way Bluetooth speakers do.

Actual

wpctl status only lists the built-in speaker and HDMI sinks. pactl list modules has no libpipewire-module-raop-discover. pacman -Q pipewire-zeroconf is not installed.

Meanwhile the speakers are visible on the network:

avahi-browse -rtk _raop._tcp
# HomePod mini (AudioAccessory5,1) advertised as Office / Office (2)

Reproduction

  1. Fresh Omarchy install on a LAN that has a HomePod (or any AirPlay speaker).
  2. Confirm Avahi is running and the speaker is advertised: avahi-browse -rtk _raop._tcp.
  3. Open the audio output list / wpctl status.
  4. The HomePod is not there.

Workaround

omarchy pkg add pipewire-zeroconf
mkdir -p ~/.config/pipewire/pipewire.conf.d
cp /usr/share/pipewire/pipewire.conf.avail/50-raop.conf \
   ~/.config/pipewire/pipewire.conf.d/50-raop.conf
systemctl --user restart wireplumber pipewire pipewire-pulse

After that, the HomePods appear as PipeWire sinks (here: Office and Office (2)). PipeWire 1.6.8 on this machine discovered them immediately.

Suggested fix

  • Add pipewire-zeroconf next to the other PipeWire packages in install/omarchy-other.packages.
  • Enable the stock drop-in (50-raop.conf) so libpipewire-module-raop-discover actually loads.

Tradeoff worth knowing: RAOP discovery will also list nearby Macs and Apple TVs as sinks, not only HomePods. That can be turned off with module.raop = false if someone wants it gone. Fedora has been enabling this by default; PipeWire 1.4.8 specifically improved HomePod mini compatibility.

View raw text
### System details

Intel i7-1185G7, Intel Iris Xe, Omarchy 4.0.2-1

### What's wrong?

# Stock install does not expose AirPlay / HomePod speakers

**Component:** defaults / PipeWire  
**Severity:** minor (local speakers and Bluetooth work; AirPlay speakers on the LAN never appear)

## Summary

On a stock Omarchy install, HomePods and other AirPlay receivers on the same Wi-Fi never show up as audio outputs. Avahi is already installed and the speakers are advertising `_raop._tcp` / `_airplay._tcp`, but PipeWire cannot talk to them.

Two pieces are missing:

1. `pipewire-zeroconf` is not in the default package set. On Arch this is a split package that contains `libpipewire-module-raop-discover` and `libpipewire-module-raop-sink`. Omarchy already installs `pipewire`, `pipewire-alsa`, `pipewire-jack`, and `pipewire-pulse` in `install/omarchy-other.packages`, but not this one.
2. PipeWire already ships `/usr/share/pipewire/pipewire.conf.avail/50-raop.conf` to load that module. Nothing in Omarchy enables it.

Omarchy already auto-connects Bluetooth A2DP so speakers appear without a manual PipeWire recovery. AirPlay is the same class of gap: the rest of the stack (PipeWire, Avahi, mDNS) is present, and the RAOP module is one package plus one drop-in away.

## Expected

HomePods / AirPlay speakers on the LAN appear in the audio output list, the same way Bluetooth speakers do.

## Actual

`wpctl status` only lists the built-in speaker and HDMI sinks. `pactl list modules` has no `libpipewire-module-raop-discover`. `pacman -Q pipewire-zeroconf` is not installed.

Meanwhile the speakers are visible on the network:

```
avahi-browse -rtk _raop._tcp
# HomePod mini (AudioAccessory5,1) advertised as Office / Office (2)
```

## Reproduction

1. Fresh Omarchy install on a LAN that has a HomePod (or any AirPlay speaker).
2. Confirm Avahi is running and the speaker is advertised: `avahi-browse -rtk _raop._tcp`.
3. Open the audio output list / `wpctl status`.
4. The HomePod is not there.

## Workaround

```sh
omarchy pkg add pipewire-zeroconf
mkdir -p ~/.config/pipewire/pipewire.conf.d
cp /usr/share/pipewire/pipewire.conf.avail/50-raop.conf \
   ~/.config/pipewire/pipewire.conf.d/50-raop.conf
systemctl --user restart wireplumber pipewire pipewire-pulse
```

After that, the HomePods appear as PipeWire sinks (here: `Office` and `Office (2)`). PipeWire 1.6.8 on this machine discovered them immediately.

## Suggested fix

- Add `pipewire-zeroconf` next to the other PipeWire packages in `install/omarchy-other.packages`.
- Enable the stock drop-in (`50-raop.conf`) so `libpipewire-module-raop-discover` actually loads.

Tradeoff worth knowing: RAOP discovery will also list nearby Macs and Apple TVs as sinks, not only HomePods. That can be turned off with `module.raop = false` if someone wants it gone. Fedora has been enabling this by default; PipeWire 1.4.8 specifically improved HomePod mini compatibility.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 10:48 UTC