Red Hat Bugzilla – Bug 150496
arecord works improperly on 1st run, fails thereafter
Last modified: 2007-11-30 17:11:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
Terminal command line enter: arecord -f dat -d 20 -D hw:0,0 test.wav
outputs a file on first execution of the command.
Playback of that output file with the command, aplay -f dat test.wav
produces lowgrade noise and perhaps 20 lines of text to stdout which
reads roughly along the lines of the following:
underrun!!! (at least .0nn microsec input/output error) where .0nn
is a value ranging from .022 - .045.
Running the arecord command a second time generates the error message -
arecord:pcm_read:1164: read error and an ouput file with no content.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. $ arecord -f dat -d 20 -D hw:0,0 test.wav
2. $ aplay -f dat test.wav
Actual Results: Production of unuseable .wav file is reproducible
Expected Results: Production of a useable .wav file that fairly
reproduces the sound one attempts to record.
Identical or similar problems have been encountered by at least four
individuals, one of whom has since installed FC3 and is now able to
use arecord in that distribution which included alsa-utils-1.0.6-3
instead of 1.0.3-1.
Request FC2 update to alsa 1.0.6-3 or later packages as a fix. The
other sound recording application available, gnome-sound-recorder, is
I run FC3 with alsa 1.0.6 and I can't either record with my AW320
soundcard, so an update of FC2 to version 1.0.6 will most probably not
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Could you check it on FC4?