Stop bt-agent.service restart-looping after the Quattro upgrade
AUDITED Audited against its sources and confirmed accurate.
Symptom
After upgrading to Omarchy Quattro, the journal fills up with hundreds of restarts per hour:
bt-agent.service: Unable to locate executable '/usr/bin/bt-agent': No such file or directory
bt-agent.service: Failed at step EXEC spawning /usr/bin/bt-agent: No such file or directory
bt-agent.service: Main process exited, code=exited, status=203/EXEC
bt-agent.service: Failed with result 'exit-code'.
Bluetooth pairing prompts also stop appearing.
Cause
/usr/bin/bt-agent comes from the bluez-tools package, not bluez-utils. The Quattro migration removes blueberry with pacman -Rns, which cascades and removes gnome-bluetooth and bluez-tools as now-orphaned dependencies, then enables the user unit bt-agent.service. omarchy-settings does not depend on bluez-tools, so nothing keeps the binary installed.
Fix
sudo pacman -S --needed bluez-tools
systemctl --user restart bt-agent.service
systemctl --user status bt-agent.service
If you do not want the agent at all (you pair via bluetoothctl or the panel):
systemctl --user disable --now bt-agent.service
Verify
systemctl --user status bt-agent.service shows active (running) with no restart counter, and journalctl --user -u bt-agent -n 20 no longer shows 203/EXEC.
Sources
bt-agent-service-restart-loop-missing-bluez-tools