slackware-current/source/xap/audacious-plugins/audacious-plugins.alsa.noise.is.not.helpful.diff
Patrick J Volkerding 75a4a592e5 Slackware 13.37
Mon Apr 25 13:37:00 UTC 2011
Slackware 13.37 x86_64 stable is released!

Thanks to everyone who pitched in on this release: the Slackware team,
the folks producing upstream code, and linuxquestions.org for providing
a great forum for collaboration and testing.

The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a
dual-sided
32-bit/64-bit x86/x86_64 DVD.  Please consider supporting the Slackware
project by picking up a copy from store.slackware.com.  We're taking
pre-orders now, and offer a discount if you sign up for a subscription.

As always, thanks to the Slackware community for testing, suggestions,
and feedback.  :-)

Have fun!
2018-05-31 22:45:18 +02:00

25 lines
1.3 KiB
Diff

--- ./src/alsa/alsa.c.orig 2011-02-22 11:29:46.000000000 -0600
+++ ./src/alsa/alsa.c 2011-03-11 15:02:53.340999637 -0600
@@ -207,10 +207,20 @@
static gboolean warned = FALSE;
if (! warned)
{
- fprintf (stderr, "\n** WARNING **\nAudacious has detected that "
+ /* fprintf (stderr, "\n** WARNING **\nAudacious has detected that "
"your ALSA device has a broken timer. A workaround\nis being "
"used to prevent CPU overload. Please report this problem to "
- "your\nLinux distributor or to the ALSA developers.\n\n");
+ "your\nLinux distributor or to the ALSA developers.\n\n"); */
+ /* ^^^ COMMENTED OUT ^^^ */
+
+ /* I'm glad there is a workaround for this, and the reports
+ are that it works, so spamming the console about it seems
+ a little bit extreme. It's not an issue to be solved here
+ by Slackware, and I would be surprised if the ALSA
+ developers did not know by now, given this warning.
+ FWIW, this seems a strange method of communicating with the
+ ALSA developers. Did they report the bug to them? */
+
warned = TRUE;
}