From: Lennart Poettering <mznyfn@0pointer.de>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: If /dev/snd/controlCx EACCES vs. ENODEV mixup
Date: Sun, 25 Nov 2007 22:03:59 +0100 [thread overview]
Message-ID: <20071125210359.GB17108@tango.0pointer.de> (raw)
Hi!
If /dev/snd/controlC0 is not accessible due to a permission problem
(EACCES), then alsa-libs will lie and return ENODEV. This is quite a
bit confusing:
<snip>
$ sudo chmod 000 /dev/snd/controlC0
$ aplay -D hw:0
ALSA lib pcm_hw.c:1207:(_snd_pcm_hw_open) Invalid value for card
aplay: main:546: audio open error: No such device
</snip>
(and strace shows that the actual problem is EACESS, as one would
assume.
I also filed this as bug on the BTS:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3600
BTW, what's the status of the BTS? Takashi asked me to post all my
issues on the ML instead of on the BTS. So why have the BTS at all?
It's even linked on the alsa-project.org front page under "I found a
bug!", which is a bit misleading. If this Mantis thing is not liked at
all, would it be possible to make some replacement available? Maybe
just use the kernel bugzilla on bugzilla.kernel.org? It's very fast,
and certainly more fun to work with than with Mantis.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next reply other threads:[~2007-11-25 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 21:03 Lennart Poettering [this message]
2007-11-25 21:40 ` If /dev/snd/controlCx EACCES vs. ENODEV mixup Jaroslav Kysela
2007-11-25 21:42 ` Jaroslav Kysela
2007-11-25 21:53 ` Lennart Poettering
2007-11-25 22:10 ` Jaroslav Kysela
2007-11-26 6:53 ` Takashi Iwai
2007-11-26 7:47 ` Jaroslav Kysela
2007-11-26 7:59 ` Takashi Iwai
2007-11-26 8:24 ` Jaroslav Kysela
2007-11-26 7:55 ` Takashi Iwai
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=20071125210359.GB17108@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--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.