World Of Warcraft Legion
Following recent events in the Broken Isles, a link has been created between Azeroth and Kil'jaeden's homeworld of Argus, bringing the Burning Legion closer than ever to destroying Azeroth. In order to stop them once and for all, Illidan and Velen are taking the war directly to the surface of Argus, where they hope to join forces with Alleria, Turalyon, and the Army of the Light to launch an all-out assault on the Legion's primary base of operations.
What does not
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Fedora 28 x86_64||Jul 08 2018||3.11-staging||Yes||Yes||Yes||Gold||Sean Rhone (Espionage724)|
|Show||antiX-17 "Heather Heyer" Core||May 28 2018||3.9-staging||Yes||Yes||Yes||Gold||spaceman|
|Show||antiX-17 "Heather Heyer" Core||Mar 08 2018||3.3||Yes||Yes||Yes||Gold||spaceman|
|Show||Arch Linux x86_64||Jan 18 2018||3.0-staging||Yes||Yes||Yes||Gold||d3rrial|
|Show||KDE Neon 5.11.4||Jan 05 2018||2.21-staging||Yes||Yes||Yes||Gold||Jay Greenfield|
|Bug #||Description||Status||Resolution||Other apps affected|
|11674||Dual-core unsupported in WoW and SC2||STAGED||View|
|29168||Multiple games and applications need realtime updates to KSYSTEM_TIME members in KUSER_SHARED_DATA (Star Wars: The Old Republic game client, Blizzard games: 32-bit Diablo III, 32-bit WoW, Overwatch, GO 1.4+ runtime)||STAGED||View|
|35461||Synergy server causes mouseover events to fail in World of Warcraft||NEW||View|
|37942||World of Warcraft (7.x.x) hangs: 100% CPU usage||UNCONFIRMED||View|
|40868||World of Warcraft 7 (Legion expansion beta realm version) client causes a lot of seh:RtlCaptureStackBackTrace stub noise in console||STAGED||View|
|41167||HLSL shader parsing failed||REOPENED||View|
|42065||WOW 7.1 spams fixme:d3d_draw:draw_primitive_arrays Start instance (VALUE) not supported.||UNCONFIRMED||View|
|42805||World of Warcrafft 64 bit client freezes or glitches after some time||UNCONFIRMED||View|
|43417||World of Warcraft leaks memory in both 64 and 32 bit modes.||UNCONFIRMED||View|
|43656||32-bit World of Warcraft client reports 'Game Initialization Failed!' or crashes on startup with stack overflow||RESOLVED||ABANDONED||View|
|43768||WOW crash game||UNCONFIRMED||View|
|43857||WoW PTR 7.3.2 crashes on startup||UNCONFIRMED||View|
|44650||Multiple Blizzard games need dxgi and d3d11 dlls mapped without hole between two LOAD segments (Diablo III v2. 6. 1. 49286+, World of Warcraft, Overwatch)||STAGED||View|
|45101||Mouse cursor not displaying correctly in Hearthstone||UNCONFIRMED||View|
I would recommend putting this in a directory of its own, such as wine-dirs or some other similar name, so that if needed, a simple rm -fr wine-dirs would eliminate everything, if you need to free up the space on your drive. These steps work on my Fedora 28 distro. I use the latest gcc from the Fedora repositries, and I have installed all the dependencies that wine needs. if you are running the fedora distro of wine, you can sudo dnf builddep wine to download the dependencies, then do sudo dnf remove wine, so that when you compile, you do not cross versions and have to troubleshoot. copy and paste the text shown here, to a script file, and run it. Go get some coffee, or watch tv, as dependent on your internet speed, the git repos may take time to download.
rm -fr wine
rm -fr wine-staging
rm -fr wine-pba-rebased
git clone git://source.winehq.org/git/wine.git
./patches/patchinstall.sh DESTDIR="../wine" --all
git apply ../wine-pba-rebased/patches/*.patch -skip this step, if you plan to use DXVK
echo this is the end, if no errors were presented, beyond the whitespace warnings, then compile and enjoy
if you get problems with firewall, then most likely, you do not have gnu-tls installed. simply install that and rerun the script.
Compiling for a WoW64 Shared Build per the Wine Wiki
These instructions assume all the build dependencies for 32 and 64 bit are properly installed. If not, you must take the time to get them. Explaining that here would be beyond the scope of this example. Shown here is the compile script I use after running the download and patch in the other How-to shown on this site. Make sure to change bdver2 to native so that it detects your processor properly. also change the make -j6 to a different number, as per the number of cores you have. This does speed up compiling.
echo Clean Start
rm -fr wine64-build
rm -fr wine32-build
echo Make Build Directories
../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --enable-win64 --without-gtk3 --with-x
PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --with-wine64=../wine64-build --without-gtk3 --with-x
If the compile is successful then the script shown below will uninstall any previous compiled version, and install the newest build.
sudo make uninstall
sudo make uninstall
sudo make install
sudo make install
Go forth and enjoy the WoW 8.0 Battle for Azeroth. You may also run Battle.net desktop app.
As a reminder - this error has been popping up since the 7.3 patch.
There is a github repo with a "clean" Windows-version Cache-file set
There's a forum thread here at WineHQ about the error:
and there are existing forum threads on both EU and US official WoW forums:
As far as we can tell - some (not all) characters generate
unusable/unstable files in the Cache folder when playing under Wine on
Linux that result in the error/disconnect. Some players have reported
being able to play normally after just adding the Windows-version Cache
files (without first clearing the folder) but since 8.0 that hasn't been
the case for me - the error and disconnects persist unless I delete ALL
existing files in my Cache prior to extracting the .zip contents into
the folder. Also, subsequent clearing of the Cache folder (because of
conflicts with other patches/addons etc) has required once again
reloading the Windows-version Cache files or the error and disconnects
resume. This is just a workaround - the bug is obviously not fixed, but
it does allow you to resume play without the disconnects. Until Blizzard
corrects the actual file-creation problem I'll try to pop in here more
frequently to update and respond.