Hearthstone

DON'T follow the instruction made by puargs.
Especially this line is bad "rm -r ~/.wine" You will lost all Windows applications that you have already installed via wine. Don't do it. It is not necessary.

Here is the right instruction.
1. Install the newest wine:
sudo dpkg --add-architecture i386
sudo add-apt-repository 'dl.winehq.org/wine-builds/ubuntu/'
sudo wget dl.winehq.org/wine-builds/Release.key && sudo apt-key add Release.key
sudo rm -f Release.key
sudo apt update
sudo apt install --install-recommends wine-staging
2. download installation file from playhearthstone.com.
3. go to the folder with your instalation file.
4. install Heartstone to a separate folder like .wine-heartstone:
env WINEPREFIX=~/.wine32-heartstone WINEARCH=win32 /opt/wine-staging/bin/wine Hearthstone-Setup.exe
5. open winecfg for wine32-heartstone:
env WINEPREFIX=~/.wine32-heartstone WINEARCH=win32 /opt/wine-staging/bin/winecfg.
6. in libaries tab add:
d2d11 and change to disabled,
locationapi and change to disabled.
7. in staging tab enable all options besides the last one.
8. run it and enjoy.

There is a mistake in point 6.
It should be:

d3d11 and change to disabled,

In 4.9.63-1-MANJARO

I installed lib32-libldap lib32-gnutls samba

To install battle.net
wine-2.20 (Staging), staging is important
winetricks corefonts

To pass the game intro
winetricks vcrun2015

Here's what it took to install on Ubuntu 17.04 x64 with an Intel graphics chipset on 2017-11-13:

Be careful following these steps - they are intended for brand new installations only. If you already have wine, don't delete your whole .wine folder as in the steps below.

1) install wine staging (wiki.winehq.org/Ubuntu)
2) download winetricks (wiki.winehq.org/Winetricks)
3) run from terminal:
rm -r ~/.wine
env WINEARCH=win32 winecfg

4) (we are now inside winecfg)
set windows version to windows xp
go to graphics tab, uncheck "allow the window manager to decorate the windows"
go to libraries tab, add "d3d11" and edit it to "DISABLED".

5) install battle.net "wine Battle.net-Setup.exe"

6) run from terminal:
winetricks corefonts vcrun2015 forcemono
winecfg
(change windows version to windows 7 and close)

7) make sure wine isn't running - run from terminal (you can skip step 7 if you're not comfortable - just reboot your computer instead, then proceed from step 8):
sudo ps -aux | grep wine
sudo kill 1234 1235 1236 1237

(replace 1234 1235 1236 1237 with the process numbers of any running wine processes found above)

8) FINALLY, open battle.net application and hearthstone and it should run fine.

Wine 2.19:
Fireside gatherings work, but my location is wrong. I managed to log into one from home, and get Nemsy Necrofizzle.

The feature crashes my game. Verification, needed.

This is very new (1 June) so I'm not surprised that there are problems.
A recent patch from 13 June shows this:
* Fixed issues that could prevent Deck Importing from functioning on mobile devices.
* Fixed an issue that could cause a player to get stuck in their Collection Manager after copying a deck.

It's possible there are still more bugs or maybe you checked before this patch.
Personally, I did a simple test (with windows set to xp, 7 and 10) copying and then creating a deck, even edited the clipboard and it all worked.

So, I hit the black screen in game, as well as several other performance issues on wine-stating-2.9. I hunted around the internet a bit and it turns out just like WoW, hearthstone supports a CLI option to force a specific d3d API
us.battle.net/forums/en/hearthstone/topic/20742385137
as expected, -force-d3d9 resolved the issues. Temporary workaround until the d3d11 support gets better

Since the update introducing the fireside gathering Hearthstone launches, establishes connections to servers then shuts down. I am pretty sure it's due to the network configuration detection. See the wineconsole output before it shuts down:
...
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:wininet:InternetSetOptionW Option 77 STUB
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!

I had a similar problem and solved it.
My problem was a crash only when connecting to the server (Europe) where I used "fireside gathering"; the game worked fine when connecting to the other servers.
This problem might be the same as bugs.winehq.org/show_bug.cgi?id=42845 but I used a different solution than suggested there.

Solution:
winetricks forcemono

This sets:
mscoree native
mscorsvw.exe disabled

same issue, seems fixed when i switch to low graphics quality in game options.

I read that elsewhere too but it did not work for me.

Just tried this without any luck - same problem, game remains completely unplayable.

nvidia gpu + driver, arch linux, wine 2.8-staging

The latest patch from yesterday breaks the game for me. When ever an animation or a popup appears the whole game goes black. Can anyone confirm this behaviour? I tried different settings but nothing seems to work. See i.imgur.com/5I2R8Y6.png

Can confirm. Tested tonight on 2.8-staging in a 32 bit prefix with wine configured as both XP and Win7 and behaviour was reproduced. Strangely it only came up after the end of the first full game I played but I think the update came in during the game and kicked me. Once I reconnected the problem popped up at the end of the game.

I can confirm this happens to me as well. A small workaround I found to make the game 'playable' is to change graphic settings to low.

Also easy to reproduce by hovering over the played card history, which is now completely black before it would just darken/desaturate the board.

Experiencing the same. on this patch version. Ubuntu 17.04 w/nvidia 630M (driver v.375.66). I've attempted switching wine versions between v1.9.18 - 2.9 along with various DLL overrides without success.

Same here, looks like the patch is causing hearthstone to use directx11. Tested with with 2.7.

I also tested with 2.9 and installing dirextx11 via winetricks. I was able to get a game to work, but every time since, I still just get the black screen.

The same issue. Nvidia 381.22, Wine 2.9.
Someone with AMD GPU with the issue?

When the screen goes black the following gets logged to console:

fixme:d3d11:d3d11_immediate_context_ResolveSubresource iface 0x14ba2c, dst_resource 0x11937968, dst_subresource_idx 0, src_resource 0x8a36cb0, src_subresource_idx 0, format DXGI_FORMAT_R8G8B8A8_UNORM stub!

created a bug report:
bugs.winehq.org/show_bug.cgi?id=43126

I just found a workaround for this issue: In wine config > Libraries, add: "d3d11" and then, deactivate it. This will make the game work again without any issues.

Can confirm that this works w/ Wine 2.7 in a 32-bit prefix: Game works as it did prior to the patch.

Yeah, sorry, I forgot to say I'm using wine 2.9 staging in a 32bit prefix.

That is so weird because that was the first I tested because of the DirectX11 errors and after the patch it did not work. Now it works!?

I can also confirm that this works for my config as well.

Ubuntu Mate 17.04, Wine v2.7, nVidia 630M GPU w/ driver v375.66.

If you've already installed 'd3d11' and other things and then cleaned up all those tested configs add it back in and set it to 'disabled'.

The only things remaining in my Wine Configuration -> Libraries -> Existing Overrides are:
-- mscoree - Native
-- d3d11 - disabled
-- dbghelp - disabled

can also confirm, just added d3d11 - disabled to my config

deb jessie x64, amd r9 285 with amdgpu

If you have any issues on Opensuse, please email me. Can't respond here for some reason

You probably disabled your mail, because I gave you clear reasoning and
contacted you before deleting your comment.

Just mentioning again: you seem to not understand difference between
Hearthstone and Blizzard App, Wine and Wine Staging.

You suggest overrides and settings that are not needed and/or required
to get Blizzard App working.

You seem to ignore fact that Hearthstone works without any of these
as long as you can hit Play button in Blizzard App.

And lastly you ignore that there is a page on AppDB for Blizzard App
and it has clear instructions that are actually tested to be EXACTLY
what is REQUIRED to get it working and therefore be able to launch
Hearthstone from it.

Again, Hearthstone GAME does not REQUIRE any of these to work.
It's Blizzard App that needs EXACTLY what is stated on
appdb.winehq.org/objectManager.php?sClass=version&iId=28855#viewHowTo
and nothing more.

You can read whole conversation and deletion reason below:

>>> Subject: How to get Hearthstone working for Wine 2.6
>>>
>>> After installing Hearthstone and Battlenet, input the following libraries
>>> in Wine Config and it should work (make sure you have winetricks corefonts
>>> and vcrun2015 as well).
>>>
>>> battlenet.net - native, builtin
>>> dbghelp - disabled
>>> msvcp100 - native, builtin
>>> msvcp140 - native, builtin
>>> msvcr100 - native, builtin
>>> wininet - native, builtin
>>>
>>> Would recommend turning off any staging settings, other than that please
>>> comment if it helped :)

>> Not sure where you got that information, but manual overrides and turning
>> off Wine Staging settings are not needed to get game itself or Blizzard App
>> to work.
>>
>> Also you specified steps in wrong order as you can't install Hearthstone
>> without using Blizzard App (former Battle.net). In turn Blizzard App
>> does not install games without vcrun2015. And corefonts only needed for
>> regular Wine to display buttons, Wine Staging works without.
>>
>> This page says at the top:
>>
>> Game itself
>>
>> For installer help and issues see Blizzard App entry
>>
>> appdb.winehq.org/objectManager.php?sClass=version&iId=28855#viewHowTo
>>
>> I'm assuming you missed that, happens.

> It worked for me, just passing what I learned along

Comment for Hearthstone Game deleted

Reasons given
Deleting incorrect information.

Submitter didn't respond to concerns over accuracy, but confirmed them.

I did receive those messages, again I was posting how I got Hearthstone to work after it had been installed previously. My information can't be "incorrect" if it fixed my problem with the software. The instructions I was giving were on how to fix Hearthstone presuming it and Battlenet had been working prior to the recent update. I will admit perhaps there is some redundancy, but that was not intentional. Regardless, how about we just let whomever is reading the conversation test it out and see what works for them? There's no harm in that is there?