Quote Originally Posted by sirtoast View Post
I also just started getting the error 132 today after I updated Wine. Now, admittedly, I haven't played it in a week, but wow has been playing fine under ubuntu for the last 2 months, and so I'm keen to blame the wine update that I applied today.
It definitely is a problem caused by the latest 1.5.20 update.
Check my findings: http://ubuntuforums.org/showthread.p...9#post12428159

Does anybody know how to revert to version 1.5.19 for now?