From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugtrack@alsa-project.org Subject: [ALSA - lib 0001184]: xmms/beep "couldn't open audio" on song change Date: Mon, 27 Jun 2005 22:05:22 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from bugtrack.alsa-project.org (gate.perex.cz [82.113.61.162]) by alsa.jcu.cz (ALSA's E-mail Delivery System) with ESMTP id 732D01EF for ; Mon, 27 Jun 2005 22:05:22 +0200 (MEST) Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org A NOTE has been added to this issue. ====================================================================== ====================================================================== Reported By: Xero Assigned To: ====================================================================== Project: ALSA - lib Issue ID: 1184 Category: 0_general Reproducibility: always Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 06-11-2005 21:14 CEST Last Modified: 06-27-2005 22:05 CEST ====================================================================== 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. ====================================================================== ---------------------------------------------------------------------- tiwai - 06-27-05 16:22 ---------------------------------------------------------------------- The noises of dmix on a heavy CPU load is considerable, but this should have nothing to do with the busy-state of socket. The confliction of socket means a different thing, e.g. the root takes the socket and sets it as the permission 0600. No certain clue yet, though. ---------------------------------------------------------------------- Xero - 06-27-05 22:05 ---------------------------------------------------------------------- no, the socket remains the proper permission and owned by my user as well, usually. I don't really ever run anything as root, especially audio stuff, so I have no idea how that'd even happen. Let me wait for it to happen again and I'll post a ls -l of the socket. All I have to do is wait for it to happen a few times and there will be quite the collection of dead sockts in there... 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 ====================================================================== ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click