Arch Linux

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!
Tasklist

FS#30701 - [alsa-lib] produces random noise when amixer set mute!

Attached to Project: Arch Linux
Opened by ChengZai Jin (bku111) - Monday, 16 July 2012, 10:31 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 12 October 2012, 13:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
This bug is only occured when alsa dmix is on. The random noise sounds like "KaKa".
The bug is resolved and related file is attached. Modified code is noted by "Note: modified by xxx".
The reason is that some audio streams are skipped when set silence.

Additional info:
* package version(s): alsa-lib-1.0.25
* config and/or log files etc.
The PCM DMA streams printed out from kernel, includes some chars not 0, but the others are all 0 when amixer set mute.

Steps to reproduce:
1.config on dmix;
2.mplayer one music;
3.amixer cset numid="video" 0.
   pcm.c (240.4 KiB)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 12 October 2012, 13:34 GMT
Reason for closing:  No response
Comment by Paul Bredbury (brebs) - Tuesday, 17 July 2012, 09:03 GMT
Here is a proper patch, produced using: diff -u --ignore-space-change
Comment by Jelle van der Waa (jelly) - Friday, 27 July 2012, 10:10 GMT
Is this bug reported upstream and the patch accepted there?
Comment by ChengZai Jin (bku111) - Saturday, 04 August 2012, 04:10 GMT
This bug is reported downstream and the patch is the same as my description. but there are some unexpected bugs accured,
e.g. switching play/stop audio is unnormal, and so on, lots of these bugs are unacceptable.
I'm sure the bug mentioned above is a problem indeed after testing and should be solved sooner or later.
please some suggestions and confirmations for help, thanks!
Comment by Tobias Powalowski (tpowa) - Friday, 07 September 2012, 20:07 GMT
Status on 1.0.26?

Loading...