Conversation
… requirement The shipped herdr config had no `[ui.sound]` section, so agent alerts were off and nothing explained why. Herdr embeds no audio decoder: it shells out to an external mp3 player, trying `paplay`, `pw-play`, `ffplay`, `mpg123` and `mpv` in that order, and fails silently when none of them exists. This enables the alerts and documents both traps that make them look broken: - the external mp3 player dependency (with one install hint per platform family) - the by-design rule that sound only fires for agents in a *background* workspace, which is the usual reason a correctly configured setup stays silent It also records the manual test (`herdr notification show --sound done`) and the log line to look for (`WARN herdr::sound`) so the next person can diagnose it without reading Herdr's source. Verified with herdr 0.9.0: `herdr config check` reports `config: ok` for this file, and the alert fires on a real agent state change in a background workspace.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
herdr/config.tomlships no[ui.sound]section, so agent alerts are off out of the box — and nothing tells you why when you turn them on and hear nothing.The silence has two independent causes, and both hit anyone installing from this repo:
paplay → pw-play → ffplay → mpg123 → mpvin that order. With none of the five installed, playback fails silently: the only trace isWARN herdr::sound: sound playback failed ... no mp3-capable audio player availablein~/.config/herdr/herdr-client.log.What changed
One file,
herdr/config.toml:[ui.sound]withenabled = true;pulseaudio-utilsforpaplay, ormpg123);herdr notification show "test" --sound done) and which log line to grep when it stays silent.Comments only, besides the new
enabled = true. No keybindings, theme, or existing setting is touched.Evidence
herdr config checkagainst this exact fileconfig: okherdr notification show ... --sound doneThe version in the note is Herdr 0.9.0. On 0.8.2 the player dependency is the same, but state-change sounds reported by agent integrations did not fire — upgrading is part of the fix, which is why the comment points at the log line rather than promising the config alone is enough.