http://bugs.winehq.org/show_bug.cgi?id=20673
Ian Savoy ian@thesavoys.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ian@thesavoys.net
--- Comment #18 from Ian Savoy ian@thesavoys.net 2010-11-29 03:50:55 CST --- So, I've had very similar errors with WoW as well. I'll say in advance that there's been a lot of abuse done to my wow installation. I've had a few patches were i had to do funky things to get the updater to go past certain steps. That being said, I think that this issue is neither a wine issue, nor necessarily a WoW issue. The root cause of all the problems i've had seem to stem from the updater or the game crashing once.
To be more direct, the issue that mikahbot is experiencing is probably due to a corrupt installation. It is my belief that WoW does not have a good mechanism for handling game and updater crashes. blizz's resolve is almost always "delete Cache, WTF, and Interface. If that doesn't work run the repair tool, if that doesn't work, reinstall."
I haven't done a full digi download for 4.x, but in past releases, the updater was extremely flaky. The best workaround (imho) was to install the game in a windows VM, reset the file permissions on the game's directory, tar it up, and copy it to the linux host. Create my wine environment, copy the tarball to the .wine environment, as well as a hefty collection of patches to go from 3.0.2, to 3.3.5, and manually patch until the 4.x downloader can "do its thing." This will lay down a nice foundation to be patched and abused by blizzard. Since 3.3.something (3.3.3, iirc), you can't copy LichKing.MPQ, unless you reset the NTFS file permissions.
In 4.0, I've had two specific issues. One is WoW consuming too much memory, the other is mikahbot's. As far as the memory consumption, I've found the best thing to do is just exit the game, make sure that there are no lingering WoW/Wine or any other Windows-related processes running, if there are kill them, and restart the game. This happens after long periods of playing...5-6 hours. I think of it as blizz's way of telling me it's time to go AFK.
With Mikahbot's issue, I've found that 2 things ensure it works when i run my startup script. The latter is, of course, rebooting the machine. I'm not sure what this fixes necessarily; my first instinct was file locks, but that's not it. Whatever it is, it's a mechanism of the OS, and/or ext4. Before rebooting, run this snippet:
find $WINEPREFIX/drive_c/Program\ Files/World\ of\ Warcraft -iname "*.lock"|xargs rm
It will ensure that the lock files, which blizz fails to cleanup when the game crashes, do not prevent the game from starting up after your reboot.
I'm not saying that you're not seriously f***ing your install everytime the game crashes and you do this. However, it does keep it going a bit longer, until you have the time to reinstall.