Bug 427043

Summary:	module-alsa-sink.c: Error opening PCM device hw:0: Device or resource busy
Product:	[Fedora] Fedora	Reporter:	udo <udovdh>
Component:	pulseaudio	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8	CC:	lkundrak, pierre-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-28 18:24:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description udo 2007-12-30 16:48:42 UTC

Description of problem:

module-alsa-sink.c: Error opening PCM device hw:0: Device or resource busy
occurs in the log after a while;

Version-Release number of selected component (if applicable):

Current Fedora 8. 0.9.7

How reproducible:


Steps to Reproduce:
Run the system for a while. After some time (might be days) sounds stop wkroing,
software hangs when sounds need to be played (Thunderbird when new mail arrives,
xine when reconfiguring and mail arrives, xmms when playing music and mail
arrives, etc)
  
Actual results:
Some sounds stop working, sometimes errors are logged.

Expected results:
100% perfect working audio. Why can't I just play *ALL* sound via alsa when I
don't need pulseaudio?

Additional info:

Comment 1 udo 2007-12-30 16:50:53 UTC

http://www.redhat.com/archives/fedora-devel-list/2007-October/msg02212.html

Comment 2 udo 2008-01-06 18:57:44 UTC

Just happened again:

MP3 playing in xmms.
Mail arrives. Thunderbird cannot play the sound.
So Thunderbird is hanging and cannot be brought into the foreground.
xmms is using alsa.
Thunderbird uses whatever it is configured with by Redhat. (I cannot choose a
specific API or device in Thunderbird via normal means)
How can I fix this error message and the system's behaviour that comes with it?
I would think that it is either a simple to fix error on my side or a very big
issue but where are the other bug entries?

Comment 3 Lennart Poettering 2008-02-15 16:46:05 UTC

Some other app seems to be blocking access to your audio device, so that PA
cannot access it. Use fuser -v /dev/snd/* to find out which one.

Comment 4 udo 2008-02-15 17:56:24 UTC

Installing PA support for a few apps has made the error go away, as it appears.

Comment 5 Lubomir Kundrak 2008-02-28 18:24:16 UTC

Furthermore noone forces you to use PA. you can uninstall it, or at least the
alsa plugin. Better solution is to use it and avoid broken sound apps.