Bug in sound driver (audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Resource busy or not available.)

My Sound Car is:
Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)

Thanks for taking the time to report this bug and helping to make Ubuntu better. With which version of Ubuntu and kernel did you notice this issue? Thanks in advance.

I have this problem also, well its somewhat different, i have audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: couldn't open source to write error message, not really sure if it"s a bug or a config problem. I'm using an Audigy 2 soundcard with the on-board soundcard disabled
version of ubuntu is feisty and using kernel 2.6.20-13-generic

Hello
I have definetly the same problem

audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample !
gconfaudiosink profile=chat: Could not open resource for writing.

And the Debugging Idea did not help.
Regards

I also have the same issue. This is both with a emu10k1 based Creative Audigy PCI card and with my integrated Intel ICH5 sound (Realtek chip).

When trying to run any of the tests in gnome-sound-propeties, I get this error:
http://zenwhen.com/webdav/sound-error.png

I cannot use skype because it says the sound configuration is incorrect.

I do have sound. The modules are loaded. However, I cannot use a MIC. Let me know if there is any kind of data I can provide to help make sure Feisty does not ship out like this.

I would also like to add that on a clean install of Feisty, a sound blaster Audigy will not work. The error message given is "Resource could not be opened for writing.".

I was able to completely solve this issue by reinstalling with a NEW user. Apparently using my old home directory was causing the issue. I've used this /home for years.

The only file I can think of in the home file is ~/.asoundrc Maybe deleting that specific file can be of use to you.

I think I7m suffering the same or a similar bug.

I can not get any sound at all, no matter what I do, despite the card seemingly being identified and ALSA driver's loaded.

I have a fresh install of Feisty. I have an external USB audio device by Kenwood. In alsamixer it is shown to be unmuted.

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: Device [Kenwood Audio Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
$ asoundconf list
Names of available sound cards:
Device

The only error output I get is when I go to Preferences->Sound, and select to test "Sound PLayback* with Alsa selected from the drop down menu. Then I get this error:
audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Could not open resource for writing.

If I select to test USB audio, or Autodetect, I get a dialog box that says sound is playing, but I get no sound through my device.

This must be a bug somewhere, as I can:t find any other way of determining what is wrong, and I feel like I've been through every sound trouble shooting web page on the net.

I even thought my Kenwood might be broken, but I just confirmed it is running by hooking it up to a Windows laptop which played without any trouble.

I'm eager for a solution, or even a workaround.

Thank you for your time and effort. If I can provide any more information or assistance to get this working, please let me know.

I have exactly the same problem. But when I tried to open a movie with Totem, there was sound. The same is true with vlc media player. I get an error message from Amarok though, which uses xine:

xine was unable to initialize any audio drivers

This is my soundcard:

C-Media PCI CMI8738 MC6 (Alsa Mixer)

I've just upgraded to feisty from edgy.

I had the same problem under Feisty and deleting the .asoundrc file worked for me. Thanks to Andrew Ash.

Hi,

I have the same problem - started happening since the latest kernel update. I can't find the .asoundrc file (definitely isn't in the home directory). It has happened to a new user, too. Occasionally a reboot solves it, but not very often.

Not an alsa-driver bug.