From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001184]: xmms/beep "couldn't open audio" on song change
Date: Fri, 30 Dec 2005 23:15:57 +0100 [thread overview]
Message-ID: <6ecb34556bc46b07feecf29e0b87323b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1184>
======================================================================
Reported By: Xero
Assigned To: perex
======================================================================
Project: ALSA - lib
Issue ID: 1184
Category: 1_pcm_d - direct PCM plugins (dmix+)
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
======================================================================
Date Submitted: 06-11-2005 21:14 CEST
Last Modified: 12-30-2005 23:15 CET
======================================================================
Summary: xmms/beep "couldn't open audio" on song change
Description:
When playing a song in beep sometimes it'll pop up a "couldn't open audio"
box as if the device is in use. This is using dmix, however, so that
seemed a bit weird. I normally have to close and reopen beep to resolve
this. I believe xmms does the same thing because I've read about people
having the exact same issue with xmms.
This starts showing up when I start pressing play again:
ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
/tmp/alsa-dmix-30443-1118514847-814284: Connection refused
ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
/tmp/alsa-dmix-30443-1118514847-814284: No such file or directory
ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
/tmp/alsa-dmix-30443-1118514847-814284: No such file or directory
ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
/tmp/alsa-dmix-30443-1118514847-814284: No such file or directory
ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
/tmp/alsa-dmix-30443-1118514847-814284: No such file or directory
However one thing which I've never seen mentioned in the previous reports,
is that when trying to use another app through dmix it doesn't work
either. Here's what mplayer says, when trying to play a video:
alsa-init: 1 soundcard found, using: default
ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
/tmp/alsa-dmix-30443-1118514847-814284: No such file or directory
ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
alsa-init: playback open error: No such file or directory
Could not open/initialize audio device -> no sound.
Audio: no sound
so apparently something went wrong with /tmp/alsa-dmix-*. As soon as I
closed beep, all other applications started working properly again, and
when I start it back up again, it works fine again too, until it does this
again. It seems to do it sporadically so it's somewhat hard to test for.
Attached is my asoundrc.
======================================================================
----------------------------------------------------------------------
skandalfo - 09-15-05 21:02
----------------------------------------------------------------------
I fear the fix present in alsa-lib-1.0.10_rc1 (I'm using the Gentoo ebuild)
doesn't fix the problem...
xine bombs out when switching 2.0 to 5.1 audio with somewhat like the
following:
...
audio discontinuity #21, type is 2, disc_off 25854
waiting for in_discontinuity update #21
video discontinuity #21, type is 2, disc_off 25854
ao_close
audio_out: no streams left, closing driver
audio_alsa_out: snd_pcm_open() of surround51 failed: Device or resource
busy
audio_alsa_out: >>> check if another program already uses PCM <<<
audio_out: open failed!
ao_flush (loop running: 1)
...
And then an error dialog pops up.
Removing the dmix thing from NFORCE.conf fixes it again... :(
----------------------------------------------------------------------
rlrevell - 12-30-05 23:15
----------------------------------------------------------------------
Any improvement in later releases?
Issue History
Date Modified Username Field Change
======================================================================
06-11-05 21:14 Xero New Issue
06-11-05 21:14 Xero File Added: asoundrc
06-11-05 21:14 Xero Note Added: 0004994
06-15-05 15:03 tiwai Note Added: 0005030
06-15-05 22:31 Xero Note Added: 0005046
06-15-05 23:55 Xero Note Added: 0005049
06-22-05 18:22 tiwai Note Added: 0005142
06-22-05 19:01 Xero Note Added: 0005144
06-23-05 02:47 Xero Note Added: 0005162
06-26-05 22:08 Xero Note Added: 0005267
06-27-05 16:22 tiwai Note Added: 0005275
06-27-05 22:05 Xero Note Added: 0005288
06-27-05 22:41 Xero Note Added: 0005289
08-01-05 23:43 skandalfo Note Added: 0005597
08-01-05 23:50 Xero Note Added: 0005598
08-15-05 14:59 perex Status new => assigned
08-15-05 14:59 perex Assigned To => perex
08-15-05 15:03 perex Category 0_general => 1_pcm_d -
direct PCM plugins (dmix+)
08-18-05 12:00 perex Note Added: 0005842
08-18-05 13:06 perex Note Added: 0005845
08-18-05 13:10 perex Status assigned => feedback
08-18-05 18:31 Xero Note Added: 0005850
09-15-05 21:02 skandalfo Note Added: 0006222
09-15-05 21:07 skandalfo File Added: xine-bugged-output.txt
12-30-05 23:15 rlrevell Note Added: 0007281
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-30 22:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 22:15 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 9:22 [ALSA - lib 0001184]: xmms/beep "couldn't open audio" on song change bugtrack
2006-01-02 9:21 bugtrack
2006-01-01 12:20 bugtrack
2006-01-01 7:11 bugtrack
2006-01-01 6:15 bugtrack
2005-12-31 20:32 bugtrack
2005-12-31 19:38 bugtrack
2005-09-15 19:02 bugtrack
2005-08-18 16:31 bugtrack
2005-08-18 11:10 bugtrack
2005-08-18 11:06 bugtrack
2005-08-18 10:00 bugtrack
2005-08-15 13:03 bugtrack
2005-08-15 12:59 bugtrack
2005-06-27 20:41 bugtrack
2005-06-27 20:05 bugtrack
2005-06-27 14:22 bugtrack
2005-06-26 20:08 bugtrack
2005-06-23 0:47 bugtrack
2005-06-22 17:01 bugtrack
2005-06-22 16:22 bugtrack
2005-06-15 21:55 bugtrack
2005-06-15 20:31 bugtrack
2005-06-15 13:03 bugtrack
2005-06-11 19:14 bugtrack
2005-06-11 19:14 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=6ecb34556bc46b07feecf29e0b87323b@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