## Summary

On Omarchy 4.0.3-1, WirePlumber crashed immediately after returning from
S3 suspend while the Omarchy-shipped Bluetooth auto-connect configuration
was installed.

The service restarted automatically, but Bluetooth audio was unavailable
after resume.

## Environment

- Omarchy: 4.0.3-1
- Kernel: 7.2.3-arch1-3
- PipeWire / pipewire-audio: 1.6.8-1
- WirePlumber: 0.5.17-1
- BlueZ: 5.87-2
- Architecture: x86_64
- Bluetooth device: Rockerz 335

## Timeline

- 00:18:24: system entered suspend
- 11:30:02: Bluetooth audio endpoints were unregistered during resume
- 11:30:03: WirePlumber crashed with SIGSEGV
- 11:30:04: WirePlumber restarted and Bluetooth endpoints registered again

The paired Bluetooth device subsequently reported a failed connection:
`Host is down (112)`.

## Symbolized backtrace

The crash occurred in the PipeWire Bluetooth SPA plugin:

```text
device_set_update_asha()
pipewire/spa/plugins/bluez5/bluez5-device.c:1010

if (!(s->device->connected_profiles & SPA_BT_PROFILE_ASHA_SINK))
```

Call chain:

```text
device_set_update_asha
device_set_update
device_set_get_info
build_profile
impl_enum_params
wp_spa_device_enum_params_sync
spa_device_iterate_params
WirePlumber Lua scripting
```

GDB showed that `s->device` contained an invalid/corrupted pointer while
the function was rebuilding Bluetooth profile state.

## Omarchy configuration

The installed configuration is the Omarchy Bluetooth configuration:

```ini
monitor.bluez.rules = [
  {
    matches = [
      { device.name = "~bluez_card.*" }
    ]
    actions = {
      update-props = {
        bluez5.auto-connect = [ a2dp_sink a2dp_source ]
      }
    }
  }
]
```

This configuration is shipped by `omarchy-settings`.

## Expected behavior

WirePlumber should survive suspend/resume and reconnect Bluetooth audio,
or recover cleanly if Bluetooth state is temporarily unavailable.

## Actual behavior

WirePlumber terminated with SIGSEGV during Bluetooth profile enumeration.
Systemd restarted it, but the Bluetooth audio device was not restored.

## Assessment

The immediate memory-safety fault is in PipeWire's `libspa-bluez5.so`.
However, the failure occurs in an Omarchy-shipped Bluetooth configuration and
during the Omarchy desktop's suspend/resume workflow.

Please investigate whether the shipped auto-connect configuration needs to be
adjusted, or whether Omarchy should add a resume-time audio recovery path.
The upstream PipeWire crash should also likely be reported to PipeWire.

Filed by gpt-5.6-luna via pi.