From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001046]: after some time, the alsa system is not accessible
Date: Tue, 12 Apr 2005 16:05:18 +0200 [thread overview]
Message-ID: <bde5b2598eecff9db99308e21b66f6ab@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1046>
======================================================================
Reported By: wilsotc
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1046
Category: PCI - cs46xx
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: gentoo
Kernel Version: 2.6.11-r5
======================================================================
Date Submitted: 04-12-2005 16:05 CEST
Last Modified: 04-12-2005 16:05 CEST
======================================================================
Summary: after some time, the alsa system is not accessible
Description:
If I remote SSH an aplay command, the problem can occur.
This command:
ssh USERNAME@host.com 'aplay /usr/kde/3.3/share/sounds/KDE_Notify.wav'
from a remote system can cause the problem to occur. The command will
produce audio for weeks, then subsequent commands will cause an error that
looks like this:
ALSA lib confmisc.c:550:(snd_determine_driver) could not open control for
card 0
ALSA lib conf.c:3463:(_snd_config_evaluate) function snd_func_card_driver
returned error: Permission denied
ALSA lib confmisc.c:387:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3463:(_snd_config_evaluate) function snd_func_concat
returned error: Permission denied
ALSA lib confmisc.c:945:(snd_func_refer) error evaluating name
ALSA lib conf.c:3463:(_snd_config_evaluate) function snd_func_refer
returned error: Permission denied
ALSA lib conf.c:3932:(snd_config_expand) Evaluate error: Permission
denied
ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM default
the user is a member of the audio group as evidenced by the many
successful audio commands prior to the error.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
04-12-05 16:05 wilsotc New Issue
04-12-05 16:05 wilsotc Distribution => gentoo
04-12-05 16:05 wilsotc Kernel Version => 2.6.11-r5
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-04-12 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 14:05 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 14:25 [ALSA - driver 0001046]: after some time, the alsa system is not accessible bugtrack
2005-12-30 23:16 bugtrack
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=bde5b2598eecff9db99308e21b66f6ab@bugtrack.alsa-project.org \
--to=bugtrack@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox