From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
Problem 1: recording doesn't work

Gnome-sound-recorder stops recording about 1 second after I hit the "Record"
button.  If I then hit the "Play" button, it stops after about 1 second.  If try
to save a file I have "recorded", nothing gets written to the disk.  There are
no error/warning dialogs/pop-ups.

If I start gnome-sound-recorder from an xterm, instead of the menu, then I see
this message:
"Audio File Library: could not open file '/tmp/untitled.wav' [error 3]"

Problem 2: playing doesn't work

Gnome-sound-recorder doesn't play sound files I record with another program.  If
I open a pre-recorded file in gnome-sound-recorder  and hit the "Play" button, I
get no sound.  I get these error messages if I run gnome-sound-recorder from an
xterm (no error/warning dialogs/popups if I start from the menu) and try playing
sounds (first message when I open the file, second message when I hit "Play"):
"Audio File Library: warning: opening file for read access: ignoring file setup
with non-raw file format [error 23]"
"Audio File Library: warning: opening file for read access: ignoring file setup
with non-raw file format [error 23]"

This is what "file" says about the file I tried to open and play in
gnome-sound-recorder:
[grover@slick grover]$ file record000.wav
"record000.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit,
stereo 44100 Hz"


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


How reproducible:
Always

Steps to Reproduce:
1. start gnome-sound-recorder
2. press the "Record" button
3. press the "Play" button, try to save, or do anything useful
	

Actual Results:  nada

Expected Results:  Some sounds should get recorded; I should be able to save
those sounds in a file; I should be able to play sounds from a file.

Additional info:

This is not a general sound configuration error or a hardware problem.  I can
record sounds using the kde sound-recording utility and also using "record" from
the command line.

I first noticed this bug under the limbo-2 beta (not sure if it was present in
limbo-1).  It persists under the null (7.3.94) beta.