http://bugs.winehq.org/show_bug.cgi?id=16113
--- Comment #4 from Reece Dunn msclrhd@gmail.com 2008-11-20 01:06:21 --- (In reply to comment #3)
- Run "sudo alsactl init" - you may need to run alsamixer or another volume
control program to increase the volume of the audio afterwards.
Is this a typo? sudo alsactl init gets me "alsactl: Unknown command 'init'..."
No. If you run "alsactl --help" you ahould see: init <card #> initialize driver to a default state in the "Available commands:" section.
If not you could try "sudo apt-get install alsa-utils"; other than that I don't know where the 'init' command comes from.
- Run "sudo alsa reset", then follow (2).
I must be using a different type of alsa then you are familiar with. "Usage: /sbin/alsa {unload|reload|force-unload|force-reload|suspend|resume}"
No, I mean't 'reload'.
If not, it could be bug 15559 (winealsa sound regression: scratchiness/stutter in multip...) and the related bug 16015 (Cepstral SwiftTalker hangs when rendering text to audio).
I will check these bugs. Thanks for your help so far. No dice yet.
I have found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246800/comments/22 (no sound in intrepid) which I tried on my Intrepid (Gnome) install which worked. However, note that for me I had wider sound issues.
Since this issue appears to be restricted to Wine, then it may be another regression from the code change found in bug 15559. If you can, could you try WoW on Wine 1.1.5 (should be good) and 1.1.6 (should have the issue you are facing).
You can run a http://wiki.winehq.org/RegressionTesting to be sure. The regression test will help Wine developers know exactly what caused the regression.