Since the Mageia 4 upgrade, all ALSA-using programs (including but NOT limited to everything run in wine) are broken and their sound is horribly distorted and this spams on the console. ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred It worked fine in Mageia 3. Killing pulseaudio doesn't help, restarting the laptop doesn't help - so far I haven't found any solution to fix this. All pulseaudio-native programs work perfectly fine. A pulseaudio program playing at the very same time as an ALSA-using program plays will have perfect clear sound while the ALSA program is mixed in with the usual distortions. I haven't found a single non-affected ALSA program, this includes alsaplayer and audacity with ALSA backend. I tested with the onboard intel audio (00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) ), and an external Micronas UAC3556B USB audio device (Nubert nuPro A-20 speakers) - both devices worked fine before, and both devices are now broken on Mageia 4 for all ALSA programs.
Actually I now found a single program which plays a song which partially works. When it launches it still starts with distortion for around 5 seconds which appears to "eat up" half of the song as if ALSA thought it was one minute into the future: and then it plays from the middle of the song to the end normally. However, audacity and alsaplayer and most other stuff simply doesn't seem to catch up with whatever warped sense of time ALSA has at launch, and they play distorted forever (or at least as long as I bothered to test).
I was told on IRC that this output might be helpful: root@Cyberman#4: rpm -qa | grep pulseaudio libpulseaudio0-5.0-0.20131220.1.mga4 pulseaudio-module-jack-5.0-0.20131220.1.mga4 lib64pulseaudio0-5.0-0.20131220.1.mga4 pulseaudio-module-gconf-5.0-0.20131220.1.mga4 lib64pulseaudio-devel-5.0-0.20131220.1.mga4 pulseaudio-module-x11-5.0-0.20131220.1.mga4 pulseaudio-5.0-0.20131220.1.mga4 pulseaudio-client-config-5.0-0.20131220.1.mga4 pulseaudio-module-zeroconf-5.0-0.20131220.1.mga4 lib64alsa-plugins-pulseaudio-1.0.27-3.mga4 libalsa-plugins-pulseaudio-1.0.27-3.mga4 pulseaudio-utils-5.0-0.20131220.1.mga4 task-pulseaudio-2011.0-4.mga4 pulseaudio-module-bluetooth-5.0-0.20131220.1.mga4 root@Cyberman#4: rpm -qa | grep alsa lib64alsa2-1.0.27.2-3.mga4 libalsa2-devel-1.0.27.2-3.mga4 lib64alsa-oss0-1.0.25-4.mga4 lib64alsa2-devel-1.0.27.2-3.mga4 libalsa2-1.0.27.2-3.mga4 lib64alsa-plugins-1.0.27-3.mga4 libalsa-data-1.0.27.2-3.mga4 alsa-utils-1.0.27.2-2.mga4 alsaplayer-0.99.81-3.mga3 alsaplayer-plugin-ui-gtk-0.99.81-3.mga3 alsa-plugins-pulse-config-1.0.27-3.mga4 lib64alsa-plugins-pulseaudio-1.0.27-3.mga4 libalsa-plugins-pulseaudio-1.0.27-3.mga4 alsa-tools-1.0.27-2.mga4 libalsa-plugins-1.0.27-3.mga4
CC: (none) => mageia, mageia
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD