http://bugs.winehq.org/show_bug.cgi?id=20643
--- Comment #8 from Erik erikmm@xs4all.nl 2009-11-13 05:16:06 --- (In reply to comment #7)
Here is a dirty workaround that allows me to run the game through the Launcher for now.
Start the Launcher with this bash script:
#!/bin/bash
nohup env WINEPREFIX="/home/sean/.wine" wine "C:\Games\World of Warcraft\Launcher.exe" & sleep 1 chmod 770 -v ~/.wine/drive_c/Games/World\ of\ Warcraft echo "Exiting" exit 0
You need to change the directory names to match your own, but this should set the proper permissions to your WoW folder 1 second after starting the Launcher(you may have increase this if you have a slow computer), and then exit the script. This should make the game launchable through the Launcher, and hopefully allow the installation of future patches through the launcher(hopefully the future patches fix this)
Thank you..! I had reached an almost similar solution but yours is definitely more elegant..:-) Blizzard has announced they found a bug in the launcher and will fix it in the next update/patch. A remaining question is: at which point in the launcher's lifecycle are the permissions changed? If it is at the end it's no problem but if it's at the start it will make patching the normal way impossible and must be done by hand...At least I'm happy it's not a Wine bug...:-)
Best regards, Erik