FS#16094 - [alsa-lib] No audio with more than one application at the same time

Attached to Project: Arch Linux
Opened by Luca Gambetta (ziabice) - Tuesday, 08 September 2009, 10:35 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 10 September 2009, 10:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

With the last upgrade of alsa libs is impossible for more than one application at a time to use audio. The first application that you launch will get an exclusive use of the audio device.
For example while listening to music you can't hear audio notifications from your IM software.

Additional info:

Here's the log from my pacman.log

[2009-09-07 12:59] synchronizing package lists
[2009-09-07 13:00] starting full system upgrade
[2009-09-07 13:01] removed system-config-printer (1.1.7-3)
[2009-09-07 13:01] upgraded alsa-lib (1.0.20-1 -> 1.0.21-1)
[2009-09-07 13:01] upgraded alsa-utils (1.0.20-2 -> 1.0.21-1)
[2009-09-07 13:01] upgraded gnome-commander (1.2.8-1 -> 1.2.8.1-1)
[2009-09-07 13:01] upgraded hdparm (9.21-1 -> 9.26-1)
[2009-09-07 13:01] upgraded murrine-themes-collection (20090804-1 -> 20090906-1)
[2009-09-07 13:01] installed pysmbc (1.0.6-3)
[2009-09-07 13:01] installed system-config-printer-common (1.1.12-5)
[2009-09-07 13:01] upgraded usbutils (0.84-1 -> 0.86-2)


Here's what audacious2 tells me in console:

ERROR: ALSA: alsa-core.c:324 (alsaplug_open_audio): snd_pcm_open: Dispositivo o risorsa occupata

"Dispositivo o risorsa occupata" is italian for "Device or resource busy"

My audio card is (from lspci):

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller

In alsamixer is:

Card: HDA Intel
Chip: Realtek ALC1200


Also I noticed that volume regulation doesn't work as expected: Kmix, audacious2 all fail to ste volume.
In alsamixer I should move the "front" slider instead of the usual "PCM"


Steps to reproduce:

Start playing a video from youtube and then start a song with audacious2
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 10 September 2009, 10:40 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Tuesday, 08 September 2009, 19:47 GMT
Here still working with amarok and other kde apps.
Comment by Luca Gambetta (ziabice) - Tuesday, 08 September 2009, 20:36 GMT
I'm doing now these simple experiments:

a)
Launch audacious2 and start playing music (it plays)
Launch Quod Libet (other audio player) and start play music -> application locks, no play

b)
While audacious2 is still playing I started a video on youtube: no music from flash

I have a lot of messages in my .xsession-errors like this:

ALSA lib conf.c:4626:(snd_config_expand) Expand error (walk): Il file esiste

"Il file esiste" is italian for "file exists"

I forgot to mention that I'm on a x86_64 arch linux


Comment by Luca Gambetta (ziabice) - Wednesday, 09 September 2009, 07:39 GMT
This morning I compiled alsa-lib and alsa-utils 1.0.20, and everything worked like a charm.

I haven't uninstalled alsa-lib-1.0.21 and alsa-utils-1.0.21 packages (to keep pacman dependences), but overwrited them, with:

./configure
make uninstall
make install

So this (on this machine at least) is a library problem. What driver version do you have on your machine?
Comment by Tobias Powalowski (tpowa) - Wednesday, 09 September 2009, 07:43 GMT
Also how do you load your sound modules have you run alsaconfig or somthing like that?
It could happen that old configs make trouble too.
Comment by b4283 (b4283) - Wednesday, 09 September 2009, 08:07 GMT
I can confirm this with a HDA-INTEL builtin chip.

check out this article: http://article.gmane.org/gmane.linux.alsa.devel/66413
Comment by Luca Gambetta (ziabice) - Wednesday, 09 September 2009, 08:09 GMT
I let everything autoload via MOD_AUTOLOAD="yes" in rc.conf.
Comment by Luca Gambetta (ziabice) - Wednesday, 09 September 2009, 08:15 GMT
So 2 people with HDA-Intel with the same problem, maybe we found the guilty... ;)
Comment by Tobias Powalowski (tpowa) - Wednesday, 09 September 2009, 08:19 GMT
Hrm folks i also have a snd-hda-intel, those are quite common, intersting would be the backend part of your snd-hda-intel.
Comment by Luca Gambetta (ziabice) - Wednesday, 09 September 2009, 08:35 GMT
This is from "lsmod":

snd_seq_dummy 3540 0
snd_seq_oss 36224 0
snd_seq_midi_event 8592 1 snd_seq_oss
snd_seq 64640 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 8324 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 47328 0
snd_hda_codec_realtek 278132 1
snd_mixer_oss 20976 1 snd_pcm_oss
snd_hda_codec_atihdmi 4784 1
snd_hda_intel 31208 9
snd_hda_codec 82128 3 snd_hda_codec_atihdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 9976 1 snd_hda_codec
snd_pcm 90872 5 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer 25344 4 snd_seq,snd_pcm
snd 76744 25 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 8576 1 snd
snd_page_alloc 10784 2 snd_hda_intel,snd_pcm
Comment by Tobias Powalowski (tpowa) - Wednesday, 09 September 2009, 11:03 GMT
ziabice you use realtek codec, one on the mailinglist also uses realtek codec,
My system uses intel codec, this runs fine.
Comment by b4283 (b4283) - Wednesday, 09 September 2009, 11:43 GMT
Mine is a realtek codec too, the guilt is that without doubt !!
Comment by Tobias Powalowski (tpowa) - Wednesday, 09 September 2009, 12:17 GMT
Does it help to remove /etc/asound.state ?
Comment by b4283 (b4283) - Wednesday, 09 September 2009, 13:13 GMT
Removed several times, still have the same error.
I have also stopped /etc/rc.d/alsa and re-run a alsaconf, though no change in /etc/modprobe.d/sound (the same modprobe configuration as before).
Comment by Tri Le (tri1976) - Wednesday, 09 September 2009, 23:25 GMT
I have the same "no sound" problem after upgrading to the new alsa-lib. I delete the existing /etc/asound.state and /etc/modprobe.d/sound, then run alsaconf (when it ask if you want to edit /etc/modprobe.d/sound or something similar...make sure you say OK). I reboot the computer and everything appears to be working normally now.
Comment by Tobias Powalowski (tpowa) - Thursday, 10 September 2009, 07:16 GMT
Should be fixed with new 1.0.21.a version.
Comment by Luca Gambetta (ziabice) - Thursday, 10 September 2009, 10:33 GMT
Just upgraded to 1.0.21.a everything on my system works perfectly!!!

I installed alsa-lib and then run alsaconf.

For me this task can be closed.

Thanks tpowa! :D

Loading...