You haven't given any explanation as to why you're closing this bug report, you don't know whether it is truly a bug or what's actually going on, and I don't know what info to give more to troubleshoot this issue I'm having. Please reopen the bug, and let others help by properly troubleshooting my issue or give a better explanation why you closed this bug report. Don't go ahead and close bugs just because you "feel" they're solved. Actually you haven't even given me a resolution to begin with.
I'm not using a mailer, I'm sending those messages right from my mail client so there's nothing to check. And I repeat in case you forgot: I'm NOT using Pulse Audio, all that you saw when I listed the installed packages with "pulse" in their names are simply *DUMMY packages* to prevent programs from requiring Pulse Audio, and prevent things like SDL compiling against it. There's nothing to set up in Pulse, only in ALSA. Also if I were to follow your logic, it would mean that the minute I play something through this soundcard, it should shoot a jet of errors the like I gave earlier in this bug report, but that doesn't happen. I'll remind you (once) again: Sound WORKS fine for an undetermined period of time (ranges from 5 minutes of playing music to 2 hours so far), right after which this error pops up in multiple rows, I hear repetitively the last sample played, and the whole OS/PC becomes UNRESPONSIVE. By how many times this has happened by now I'd also appreciate a way to shutdown ALSA so I could use the PC again. I tried both $ alsa force unload and $ sudo invoke-rc.d alsa-utils stop Both which show the ALSA has stopped, but the annoying repetitive sounds don't stop and the system is still struggling with 100% CPU load.