World of Warcraft

World of Warcraft Classic - Goes live August 26th, 2019 - 3:00 PDT for US regions.  Vanilla wow reborn, with some code improvements, but the complete look and feel of WoW Vanilla. Relive the original, and make new friends.  Name reservation is open now, for up to 3 characters, horde or alliance, that were around in vanilla.  No servers will allow horde and alliance on the same account, but you can put horde on one server and alliance on another.  Join the classic movement.

Application Details:

Version: 1.13
License: Retail
Votes: 0
Latest Rating: Platinum
Latest Wine Version Tested: 5.0

Maintainers: About Maintainership

Link World of Warcraft Classic (Vanilla rebooted)

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

- Installing the game using
- Starting the game using
- Logging into the game
- Playing the game
- Changing graphical the settings to maximze the quality

What does not


What was not tested

- Nothing

Hardware tested


  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowDebian GNU/Linux 10.x "Buster" x86_64Jan 30 20205.0N/A Yes NoPlatinumQuinn 
CurrentGentoo Linux x86_64Oct 20 20194.18-stagingYes Yes NoPlatinumnva 
ShowKaliSep 01 20194.15-stagingYes Yes NoPlatinumDave Driesen 
ShowFedora 30 x86_64Aug 14 20194.13-stagingYes Yes NoPlatinumSean Rhone (Espionage724) 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

[SOLUTION] mouse issues with gnome 2
by Corey H on Friday October 2nd 2020, 12:49
Here's a real example:

cd '/media/pop-os/EXTLB/WOW_wineprefix/drive_c/Program Files (x86)/'
export XMODIFIERS=''
export WINEPREFIX=/media/pop-os/EXTLB/WOW_wineprefix
read -p 'press ENTER to play' myv
WINEDEBUG=-all wine 'C:\\Program Files (x86)\\\\ Launcher.exe'
[SOLUTION] mouse issues with gnome
by Corey H on Friday October 2nd 2020, 12:46
export XMODIFIERS=''
#then execute app / World of Warcraft here

#basically you set the environment variable XMODIFIERS to an empty string before running the to launch WoW classic
wine-staging 5.15, WoW Classic crash
by Janne Veteläinen on Sunday August 23rd 2020, 7:32
The game is crashing on exiting, if there are "pending configuration changes". What I mean is, if I changed addon or interface settings and didn't do a /reload before exiting the game, it crashes every time, with this error message:

ERROR #132 (0x85100084) Fatal exception!

Program: C:\Program Files (x86)\World of Warcraft\_classic_\WoWClassic.exe
ProcessID: 1320

The instruction at "0x00007eff1317ccf8" referenced memory at "0x0000000000000018".
The memory could not be "written".

Anyone know the cause or a fix?
Using Arch Linux, wine-staging 5.15, even have all the optional dependencies for wine installed.
Mouse Rotate Solution
by Peter on Friday July 17th 2020, 0:27
I have found a solution which works for me in wine-staging 5.9 with the rotating mouse. In WoW chatbox just type or copy this:

/console rawMouseEnable 1

by Jimy cooper on Wednesday July 1st 2020, 3:00
Like world of warcraft classic expansion, and also spent a lot of time and moeny (mostly buy gold at ) on it, and also looking forward to the next expansion: Shadowlands
5.9 bugged with mouse warp problem for various games
by Steve Ebey on Saturday June 6th 2020, 6:27
Downgrade to 5.8 and you will be fine, if you move your mouse and it jumps around randomly. It is a known bug and should be fixed in the next release.
Click+drag to move camera bugging out
by Simon on Friday June 5th 2020, 23:24
Hi all. After a recent system upgrade, I'm having some issues when using clicking + dragging to move the camera around. It seems that either (1) whenever I release the mouse or (2) after about 2 seconds, the application releases my mouse, but the cursor is not where it started. It's on the right side of my left monitor, whereas I'm running the game on my center monitor. The expected behavior is that the cursor gets released and sent back to the same location that you clicked, but that doesn't seem to be happening anymore.

Wine version: 5.9 staging

Here were the packages that were upgraded if anyone's interested:
[2020-06-03T22:27:21-0700] [ALPM] upgraded amd-ucode (20200421.78c0348-1 -> 20200519.8ba6fa6-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded protobuf (3.11.4-1 -> 3.12.0-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded python-sip (4.19.22-1 -> 4.19.22-2)
[2020-06-03T22:27:21-0700] [ALPM] upgraded arcus (4.5.0-1 -> 4.5.0-2)
[2020-06-03T22:27:21-0700] [ALPM] upgraded libgpg-error (1.37-1 -> 1.38-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded systemd-libs (245.5-2 -> 245.6-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded ca-certificates-mozilla (3.52.1-2 -> 3.53-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded lcms2 (2.9-3 -> 2.10-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded openimageio ( ->
[2020-06-03T22:27:21-0700] [ALPM] upgraded harfbuzz (2.6.6-1 -> 2.6.7-1)
[2020-06-03T22:27:21-0700] [ALPM] upgraded openshadinglanguage (1.10.10-2 -> 1.10.11-1)
[2020-06-03T22:27:22-0700] [ALPM] upgraded device-mapper (2.02.187-2 -> 2.02.187-3)
[2020-06-03T22:27:22-0700] [ALPM] upgraded cryptsetup (2.3.2-2 -> 2.3.3-1)
[2020-06-03T22:27:22-0700] [ALPM] upgraded systemd (245.5-2 -> 245.6-1)
[2020-06-03T22:27:22-0700] [ALPM] upgraded vulkan-icd-loader (1.2.140-1 -> 1.2.141-1)
[2020-06-03T22:27:22-0700] [ALPM] upgraded python-setuptools (1:46.4.0-1 -> 1:47.1.1-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded blender (17:2.82.a-6 -> 17:2.83-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded python-dulwich (0.19.16-1 -> 0.20.2-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded breezy ( ->
[2020-06-03T22:27:23-0700] [ALPM] upgraded nss (3.52.1-2 -> 3.53-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded re2 (1:20200501-1 -> 1:20200601-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded librsvg (2:2.48.4-1 -> 2:2.48.6-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded xkeyboard-config (2.29-1 -> 2.30-1)
[2020-06-03T22:27:23-0700] [ALPM] upgraded glib-networking (2.64.2-1 -> 2.64.3-1)
[2020-06-03T22:27:24-0700] [ALPM] upgraded chromium (83.0.4103.61-1 -> 83.0.4103.97-1)
[2020-06-03T22:27:24-0700] [ALPM] upgraded cmake (3.17.2-2 -> 3.17.3-1)
[2020-06-03T22:27:24-0700] [ALPM] upgraded curaengine (4.5.0-1 -> 4.5.0-2)
[2020-06-03T22:27:24-0700] [ALPM] upgraded faudio (20.05-1 -> 20.06-1)
[2020-06-03T22:27:24-0700] [ALPM] upgraded firefox (76.0.1-1 -> 77.0.1-1)
[2020-06-03T22:27:24-0700] [ALPM] upgraded git (2.26.2-1 -> 2.27.0-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded go (2:1.14.3-1 -> 2:1.14.4-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded netpbm (10.73.31-1 -> 10.73.31-3)
[2020-06-03T22:27:26-0700] [ALPM] upgraded graphviz (2.44.0-2 -> 2.44.0-3)
[2020-06-03T22:27:26-0700] [ALPM] upgraded grpc (1.28.1-1 -> 1.29.1-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded gtksourceview3 (3.24.11-1 -> 3.24.11+28+g73e57b57-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded harfbuzz-icu (2.6.6-1 -> 2.6.7-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded imagemagick ( ->
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-faudio (20.05-1 -> 20.06-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-glib-networking (2.64.2-1 -> 2.64.3-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-harfbuzz (2.6.6-1 -> 2.6.7-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-libnsl (1.2.0-1 -> 1.2.0-2)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-librsvg (2.48.4-1 -> 2.48.6-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-mpg123 (1.25.13-1 -> 1.26.0-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-nss (3.52.1-2 -> 3.53-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lib32-vulkan-icd-loader (1.2.140-1 -> 1.2.141-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libbytesize (2.2-1 -> 2.3-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded lvm2 (2.02.187-2 -> 2.02.187-3)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libblockdev (2.23-4 -> 2.24-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libgphoto2 (2.5.24-1 -> 2.5.25-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libheif (1.6.2-2 -> 1.7.0-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libmagick6 ( ->
[2020-06-03T22:27:26-0700] [ALPM] upgraded libnm (1.24.0-1 -> 1.24.2-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libnumbertext (1.0.5-2 -> 1.0.6-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libqmi (1.24.12-1 -> 1.24.14-1)
[2020-06-03T22:27:26-0700] [ALPM] upgraded libtommath (1.2.0-2 -> 1.2.0-3)
[2020-06-03T22:27:27-0700] [ALPM] upgraded linux (5.6.14.arch1-1 -> 5.6.15.arch1-1)
[2020-06-03T22:27:28-0700] [ALPM] upgraded linux-docs (5.6.14.arch1-1 -> 5.6.15.arch1-1)
[2020-06-03T22:27:29-0700] [ALPM] upgraded linux-firmware (20200421.78c0348-1 -> 20200519.8ba6fa6-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded linux-headers (5.6.14.arch1-1 -> 5.6.15.arch1-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded md4c (0.4.3-1 -> 0.4.4-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-base (5.14.2-3 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-svg (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded mumble (1.3.0-8 -> 1.3.0-9)
[2020-06-03T22:27:31-0700] [ALPM] upgraded murmur (1.3.0-7 -> 1.3.0-8)
[2020-06-03T22:27:31-0700] [ALPM] upgraded networkmanager (1.24.0-1 -> 1.24.2-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded portaudio (1:19.6.0-6 -> 1:19.6.0-7)
[2020-06-03T22:27:31-0700] [ALPM] upgraded python-cffi (1.14.0-2 -> 1.14.0-3)
[2020-06-03T22:27:31-0700] [ALPM] upgraded python-pyqt5-sip (12.7.2-1 -> 12.8.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded python-pyqt5 (5.14.2-1 -> 5.15.0-2)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-declarative (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-graphicaleffects (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-location (5.14.2-2 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-multimedia (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-quickcontrols (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-quickcontrols2 (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-script (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-speech (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-tools (5.14.2-2 -> 5.15.0-2)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-wayland (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:31-0700] [ALPM] upgraded qt5-webchannel (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded qt5-webengine (5.14.2-3 -> 5.15.0-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded qt5-x11extras (5.14.2-1 -> 5.15.0-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded qtcreator (4.12.1-1 -> 4.12.2-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded spandsp (0.0.6-2 -> 0.0.6-3)
[2020-06-03T22:27:32-0700] [ALPM] upgraded subversion (1.13.0-3 -> 1.14.0-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded systemd-sysvcompat (245.5-2 -> 245.6-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded udisks2 (2.8.4-2 -> 2.9.0-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded vlc (3.0.10-1 -> 3.0.10-2)
[2020-06-03T22:27:32-0700] [ALPM] upgraded vte-common (0.60.2-2 -> 0.60.3-1)
[2020-06-03T22:27:32-0700] [ALPM] upgraded vte3 (0.60.2-2 -> 0.60.3-1)

Nothing is popping out to me as a likely cause except the kernel update.

by Jimy cooper on Wednesday May 13th 2020, 3:37
I am currently having an issue where I cannot locate the installation for the classic wow client for the stress test, I have tried many methods from, but still cannot solve the problem, anybody know the solutions? thanks
Unable to start up 3D acceleration
by Jazz on Friday February 21st 2020, 21:08
Hi, I have wine 5.2 with DXVK and when I try to start classic it throws the error "World of Warcraft was unable to start up 3D acceleration." I've tried setting every d3dx with every setting of builtin or native, but nothing I do works. I can provide a DXVK log from the terminal if you'd like, I just can't figure out what's causing this.
RE: Unable to start up 3D acceleration
by Steve Ebey on Saturday February 22nd 2020, 7:50 is the site that creates DXVK. Use the issues to report your problem. Wine does not maintain dxvk. It is a plugin to use vulkan, to run dx11 for wine. You must have vulkan properly setup for it to work. If you have not downloaded a vulkan capable video driver, then dxvk will not work.
RE: Unable to start up 3D acceleration
by Jazz on Saturday February 22nd 2020, 15:06
I know my DXVK installation is fine, literally Classic Wow is the only app that does this. Retail Wow works fine as does all my other Windows programs, I figured I'd ask if anyone else on here had this error to see if there's workarounds.
RE: Unable to start up 3D acceleration
by Steve Ebey on Sunday February 23rd 2020, 8:48
What os? What video driver?
RE: Unable to start up 3D acceleration
by Jazz on Monday February 24th 2020, 18:47
I'm on Ubuntu Mate 19.10 and the driver I'm using is Nvidia-driver-435. Like I said I can provide a log file if you'd like, I just haven't been able to figure out if this is the problem from Wine, or from DXVK.
RE: Unable to start up 3D acceleration
by Steve Ebey on Monday February 24th 2020, 22:22
do you launch from command line, or app? I have had issues with connection, when winecfg is set to windows 10 but I can login just fine, if I set winecfg to windows 7. Might see if that helps. You could copy and paste the gx.log file from the _classic_/Logs folder in your .wine prefix, that might also help. I run Nvidia, Proprietary 440.59. Might consider trying that, lots of vulkan changes since 435.
RE: Unable to start up 3D acceleration
by Jimy cooper on Wednesday May 13th 2020, 3:28
" To install Classic from the Blizzard App, select World of Warcraft and then select World of Warcraft: Classic from the Version selector. If you cannot see the Version selector, try uninstalling and reinstalling the Blizzard App. By the way ,a World of Warcraft license is required." WoW Classic solutions from
Clicking multiple buttons bug
by Morten on Thursday December 5th 2019, 16:54
I have just installed WoW Classic on Ubuntu 18.04, but I'm having trouble with pressing multiple keys. I'm used to playing on Windows 7 and pressing right mouse button and move with the Q/E buttons on my keyboard, using W to move forward at the same time. If I hold down right mouse button and W, it won't react to Q followed by E or E followed by Q. Hard to explain really, I hope I'm making sense.
RE: Clicking multiple buttons bug
by Rinaldus on Sunday December 22nd 2019, 12:16
Try to install Wine 4.18. Wine versions >= 4.19 are broken.
Levels of enemy players not displayed
by Tom on Thursday October 24th 2019, 17:22
When mousing over a player of the enemy faction, the game will display two question marks in place of level, eg:

"Level ?? human warrior (player)"

Is anyone else experiencing this?
RE: Levels of enemy players not displayed
by Steve Ebey on Thursday October 24th 2019, 18:33
That is by design, in the game. Only same faction can see player levels. if you are max level, you might be able to see levels of the other faction players, on normal servers. are you on a pvp server? if so, that might be why you only see ?? on the opposite faction. Are you at max level?
RE: Levels of enemy players not displayed
by stein on Saturday February 1st 2020, 12:11
You can't see levels for enemy players with level greater by 10 levels or more than your character level.
Touchpad doesn't work/is flakey
by algebro on Wednesday October 23rd 2019, 12:11
WoW seems to run fine with a mouse, but if I try to play with my touchpad the pointer will just randomly stop for 10 seconds or so. If I hit escape and bring up the UI options it will move again--it only seems to happen when playing the game outside of options menus.

Has anyone encountered something like this? I'm playing on an XPS with an nvidia GTX 1650 with PRIME render offloading in case it's somehow related to that.
RE: Touchpad doesn't work/is flakey
by algebro on Wednesday October 23rd 2019, 13:33
Update--I just noticed this only seems to happen if I am using the keyboard at the same time as the touchpad. I thought it could be related to but that should've been fixed already (I'm running wine-staging 4.18)
RE: Touchpad doesn't work/is flakey
by algebro on Wednesday October 23rd 2019, 13:50
Sorry for the noise--I figured it out. I had to configure libinput to set "DisableWhileTyping" to "False" on the touchpad device.
Computer locks up
by Scott on Monday September 23rd 2019, 15:46
I've been having an issue where my entire computer locks up until I do a hard restart, when playing wow. I've never had this issue w/my computer before, and it only happens while playing wow. Maybe on average once per every 6 hours of gameplay (rough estimation). Is anyone else seeing this? Do you have any idea what I should be look for? I'm considering seeing if I can get the game client to work while downgrading my nvidia drivers.
RE: Computer locks up
by Steve Ebey on Monday September 23rd 2019, 17:27
I would not downgrade the nvidia drivers, instead make sure you have the latest, and also make sure your vulkan is the latest. What Linux Distro are you running? I have Fedora 30 and can play for over 10 hours at a time (i know, I have no life). I compile wine from the gits and I also compile vkd3d for the dx12 wrapper. Not sure what DX classic uses, because there is no option in the advanced video setting either.
Keystrokes not registering
by ED on Sunday September 15th 2019, 7:27

In 4.15-staging the occational keystroke went unnoticed so movements or spells did not happen when I wanted it to.
In 4.16-staging the same problem has become so big that it makes playing annoying at best and very difficult when in a group where accuracy is needed.

I did some reading and it seems nvidia have this problem with shadowplay which disappears completely when you switch nvidia sharing off. As far as I could gather, shadowplay is not available under linux so this should not be the problem.
I also found several references to people switching off key repeat in Ubuntu, but this had no impact for me.
However, it does seem the issue is somehow related to load, as if I get fps up the issue is less prominent. As I am not on a high-end machine and wine only using one cpu core, my fps is typically around 20-30 regardless of display detail, and seems mostly dependent on cpu load.

Does anyone have any tips as to what this could be about or anything at all?

Ubuntu 19.04
RE: Keystrokes not registering
by Velvus on Monday September 16th 2019, 14:13
I am experiencing the same issues on my desktop with Wine 4.16, also in combination with an nvidia card. It runs pretty bad even though I think theoretically the specs should be more than fine (i5 CPU in combination with GTX970). I have to say, I experience WoW Classic to run smoother on my laptop with crappy Intel onboard graphics chip than on this desktop.

This leads me to conclude this issue is probably related to the nvidia drivers... perhaps switching driver versions could fix it.
RE: Keystrokes not registering
by ED on Monday September 16th 2019, 17:15

Changing drivers was the one thing I didn't try as last time I tried it messed up a lot. I did try it now, and absolutely no change with this issue.

This feels to me as if messages goes missing. My reasoning is that whenever I can generate CPU overhead it almost behaves normal.
It's as if keypress messages goes missing which could probably be due to the difference in the way X and Windows handles messages where X does not require replies where Windows does. For Wine that would, at least as X was some time ago, result in Wine sending messages just assuming X received them. A removal of CPU overhead would most likely create issues in this methodology, which would nicely explain why the problem is directly inverse proportional to CPU load.

To this end I wanted to try out an earlier version of Wine, at the very least 4.15-staging, but when I tried that Wine did not work anymore.
Maybe I uninstall Wine completely and install an earlier version just to see if I can get it working again.
I'm not really sure how far back I can go and still expect WoW Classic to work, though.
RE: Keystrokes not registering
by Tantenonneke on Friday September 20th 2019, 4:15
Experiencing the same problem on a GTX1080/i7-6850K/64GB RAM system. Tried nvidia-416, nvidia-430 (broke my entire system) and nvidia-387. Issue remains.
RE: Keystrokes not registering
by Tantenonneke on Friday September 20th 2019, 4:15
Ubuntu 16.04, FYI
RE: Keystrokes not registering
by ED on Friday September 27th 2019, 10:28
So I used PlayOnLinux to install another version alongside 4.16-staging and manually started the WoW launcher using Wine 4.14-staging.
Result: Problem gone.
I have only tested for some 10 minutes, but so far it hasn't happened once. At worst there has been some minor keypress lag, but seeing as my computer is on the older side and not that fast, that is something I can live with.

However, there is no doubt that 4.14-staging does not have the issues 4.16-staging has and which 4.15 had in a minor degree (if I remember correctly).
RE: Keystrokes not registering
by Tantenonneke on Tuesday October 1st 2019, 6:25
I just updated to 4.17 and it seems to have been resolved!
Ubuntu 16.04/i7/1080GTX
RE: Keystrokes not registering
by Tantenonneke on Tuesday November 19th 2019, 3:52
On Ubuntu 18.04 (Wine 4.19) I still have this problem.
RE: Keystrokes not registering
by ED on Sunday December 15th 2019, 6:24
Wine 5 rc1 installed now (Ubuntu 19.10), and this issue has still not been fixed. It was fixed for a single version, 4.17 or 4.18, and then it came back. I opted to use 4.14 staging after that and have been using that since. Tried version 5 today and the issue is still there. Not a lot, but still annoying enough.
It would be nice to get past this any time soon.
RE: Keystrokes not registering
by ED on Saturday December 21st 2019, 16:32
v5 rc2 has the same issue.
RE: Keystrokes not registering
by ED on Saturday December 28th 2019, 11:57
v5 rc3, problem still there.
RE: Keystrokes not registering
by Steve Ebey on Saturday December 28th 2019, 18:26
not familiar with ubuntu, as i run fedora. I had a similar issue and it turned out that the desktop environment was catching keys before got them. I would see if your desktop environment is doing the same. I also self compile, and use the configure option --with-x to make wine x aware. Hope this helps.
RE: Keystrokes not registering
by ED on Monday December 30th 2019, 15:37
I'm not compiling my own version, but I use PlayOnLinux to install additional versions.

I'm not saying the desktop environment isn't messing things up, but as I am running a box standard Ubuntu 19.10 I'd expect wine to be able to function there.
Version 4.14 does not have this problem, with the option of 4.17 also being functional and maybe one or two more. Most versions after 4.14 have this issue to various degrees as far as I can see.

The issue does however seem to be correlated with system load to such a repeatable degree that I would go far in suspecting stresstests are lacking or completely missing from version release testing.
RE: Keystrokes not registering
by DevTest on Thursday January 2nd 2020, 23:09
I had the same problem with Gnome 3. It seems to be indeed a mutter issue that is taking control over the keyboard and then pass it to wine in a faulty manner.
Managed to solve this issue using XMODIFIERS=''
So your launcher would look like
env XMODIFIERS="" WINEPREFIX="/home/devtest/.wine" wine "C:\Program Files (x86)\\ Launcher.exe"

Tested on both wine 4.21-staging, wine 5 rc2 staging.
Also, to ensure good mouse behaviour you should check winecfg -> Graphics -> Automatically capture the mouse in full-screen windows
RE: Keystrokes not registering
by ED on Friday January 3rd 2020, 11:57
Simply awesome. Problem seem to be gone! Latency is close to gone, and everything seems fast and as it should be. Will do more testing shortly.
Timeout after realm was chosen
by timo on Monday September 9th 2019, 14:54
for two days no, I cannot enter any realm. Before that, everyhting was fine. Anyone else simmilar issues? Launcher and Game starts successfull. Login also works.
But after choosing any realm and trying to enter it, I am getting this "Login to realm" window. After 60 seconds it times out and I am back to the login page.
Doesnt matter which realm I choose.

Previously I used wine staging 4.08 and everything was fine.
But for two days, its not working anymore.
Also tried updating to wine staging 4.15, without success.
And... I just mentioned, retail has the same issue. Works also fine, two days ago.
RE: Timeout after realm was chosen
by Scott on Monday September 9th 2019, 17:53
Hi! A fix was found and documented on the retail version of wine's wineHQ page.

Short version is: up your IPv4 stack's default TTL from 64 to 128 and login works again! Run the following in the command line:

echo 128 | sudo tee /proc/sys/net/ipv4/ip_default_ttl
RE: Timeout after realm was chosen
by timo on Tuesday September 10th 2019, 0:24
perfect, thanks a lot!!
RE: Timeout after realm was chosen
by ED on Monday September 16th 2019, 17:19
I just want to add that I had similar issues where I solved it by allowing IPv6 from in-game.
Doesn't seem to work on Ubuntu.
by Jontom Xire on Saturday August 24th 2019, 12:08
OS: Ubuntu 18.04.2 LTS
GFX: Nvidia GeForce GTX 1080
Wine: wine-4.12.1 (Staging)

After the login I just get a black screen and a notification popup that the game is being downloaded/installed.

The Blizzard page says:

In the App, click on the World of Warcraft tab. Select "WoW Classic” in the Version or Region/Account drop-down menus, and hit the Install button.

I don't see a World of Warcraft tab. The first time I ran it it complained that there were no games in a separate window. I closed that and exited. Was that the wrong thing to do?

Anyway, after the login window I just get a black window and it seems to be installing the current retail version in the background. I do not want to install the current retail version, just the WoW classic.

My run command is:

WINEPREFIX=/wine/WoW_Classic wine "/wine/WoW_Classic/drive_c/Program Files (x86)/ Launcher.exe"

I am not sure this is the right place for this comment. Is there a support thread in a forum somewhere for this game?
RE: Doesn't seem to work on Ubuntu.
by Steve Ebey on Saturday August 24th 2019, 14:59
When I downloaded classic, it said it was taking a large part of the retail game, and just adding the classic files so it was a small download. If you do not have WoW-BFA installed, then your download will be bigger. As to a support forum, you could look on the wow-bfa here in the appdb, as they both use the same setup. Fedora wine is at version 4.14-2, so you might need to update your distro copy of wine. I personally compile wine, and the how-to on the WoW-BFA appdb can give you help about doing that. I also play classic, but will not be live until 3:00 PDT August 26th, for the USA. All you can do now, is reserve character names. You can create up to 3 characters, on different servers, or the same server, and as it was in vanilla, horde and alliance can not exist on the same server. Hope this information helps.
RE: Doesn't seem to work on Ubuntu.
by Jontom Xire on Monday August 26th 2019, 12:55
Thanks for your reply/info.

I had issues upgrading to Wine 4.14 due to some new dependencies, but once I upgraded all is fine (so far - still waiting to be able to actually play of course). So far:

* Launcher displays correctly.
* Game load screen is fine.
* Server select is fine.

I need to get some game time credit (have asked for the offered 3 day free trial) before I can actually create a character and test any further.