Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34811 - [alsa-utils] arecord hangs with SIGTERM or SIGINT
Attached to Project:
Arch Linux
Opened by miskoala (miskoala) - Tuesday, 16 April 2013, 15:05 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 17 April 2013, 10:59 GMT
Opened by miskoala (miskoala) - Tuesday, 16 April 2013, 15:05 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 17 April 2013, 10:59 GMT
|
Detailspacman -Q alsa-utils
alsa-utils 1.0.27-3 I try to record input in my soundcard with: arecord -D hw:0,0 -t wav -c2 -f S32_LE -r 44100 -V stereo sideA.wav Then kill it when record is done with SIGTERM or SIGINT but this don't work, trying these methods to end recording causes the process use 100%cpu and create thousands of small files (with size of 44 bytes each) in the directory when arecord was started like sideA-10000.wav, sideA-999999.wav etc. must kill it with killall -9 arecord I can only end recording cleanly with SIGABRT, then recording is aborted fine and I have my sideA.wav without thousands of small wavs SIGTERM and SIGINT works fine with alsa-utils 1.0.26-1 |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 17 April 2013, 10:59 GMT
Reason for closing: Fixed
Additional comments about closing: 1.0.27-4
Wednesday, 17 April 2013, 10:59 GMT
Reason for closing: Fixed
Additional comments about closing: 1.0.27-4

Please confirm fix in 1.0.27-4

works fine in 1.0.27-4