From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: amixer: amixer.c:1706: sevents: Assertion `res >= 0` failed.
Date: Wed, 29 Apr 2026 11:50:01 +0200 (CEST) [thread overview]
Message-ID: <18aacafefdad9900-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18aacafefd7ab900-webhooks-bot@alsa-project.org>
alsa-project/alsa-utils issue #327 was opened from mgedmin:
I'm seeing this assertion error if I run `amixer sevents` very soon after pipewire daemon startup:
$ amixer sevents
Ready to listen...
Poll ok: 0
amixer: amixer.c:1706: sevents: Assertion `res >= 0` failed.
Aborted (core dump)
Background: I'm trying to mute the speaker during an automated Ubuntu 26.04 LTS desktop installation process. I don't know what the best approach is, but what I settled on is to write a curting early-command that creates a /home/ubuntu/.config/systemd/user/mute-sound.service that runs a little shell script during GUI sesison startup, with an After=pipewire.socket, so that amixer can talk to the default sound card (which is 'pipewire'). This happens a bit too early (amixer prints `amixer: Unable to find simple control 'Master',0`), so I've added a wait loop that looks like this:
stdbuf -oL amixer sevents | while IFS= read -r line; do case "$line" in "event add: 'Master',0") amixer set Master mute; exit;; esac; done
and, well, this one gets me the above-mentioned assertion error.
Adding a `sleep 1` before I invoke `amixer sevents` makes the assertion go away and then the muting works (but the exit doesn't terminate the bash pipeline and leaves amixer sevents running forever, or until the end of the autoinstall session, which is not a problem for me).
I'm testing all of this inside a Hyper-V virtual machine, for reasons.
Issue URL : https://github.com/alsa-project/alsa-utils/issues/327
Repository URL: https://github.com/alsa-project/alsa-utils
parent reply other threads:[~2026-04-29 9:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18aacafefd7ab900-webhooks-bot@alsa-project.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18aacafefdad9900-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.