https://bugs.winehq.org/show_bug.cgi?id=43910
Bug ID: 43910 Summary: Battle.net helper.ex crashes with Win 7 or higher Product: Wine Version: 2.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: hewanci@gmail.com Distribution: ---
Since Blizzard dropped support for Xp, Vista and 2008 games refuse to launch if Win version is anything older than Win 7.
However, with Win 67 or newer, chats, the News tab and the new Social tab in beat are all dysfunctional, causing Battle.net helper.exe crashing repeatedly.
As such you are forced to chose between a working Blizz app (Win Vista/2008) or working games (Win 7+).
No error messages in console.
Arch Linux 64 bit + KDE Wine Staging 2.18; 64 bit prefix Core fonts installed.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #1 from Storm Engineer hewanci@gmail.com --- "with Win 67 or newer, chats, the News tab and the new Social tab in beat" * "with Win 7" & "Social tab in Beta"
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #2 from Storm Engineer hewanci@gmail.com --- Wine crash report: https://pastebin.com/GqMYCkfx
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #3 from Storm Engineer hewanci@gmail.com --- Created attachment 59535 --> https://bugs.winehq.org/attachment.cgi?id=59535 backtrace
https://bugs.winehq.org/show_bug.cgi?id=43910
Giacomo Orlandi gia_@inwind.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gia_@inwind.it
--- Comment #4 from Giacomo Orlandi gia_@inwind.it --- I would have thought this is a duplicate of https://bugs.winehq.org/show_bug.cgi?id=42865 but that's reported working on 2.18 staging.
It was working for me on 2.18 staging, crashing only every after a few hours. Now it crashes using 2.19 staging but I made other changes to my system recently so I don't know yet if the wine upgrade is the real cause.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #5 from Storm Engineer hewanci@gmail.com --- To clarify, it's not the Battle.net app crashing. The app itself works.
But if I try to access chats, Social tab or News tab, the content fails to load and "Battle.net helper.exe" crashes. If I close the crash report dialog, it tries again and crashes again, repeatedly.
https://bugs.winehq.org/show_bug.cgi?id=43910
Storm Engineer hewanci@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Battle.net helper.ex |"Battle.net helper.exe" |crashes with Win 7 or |crashes with Win 7 or |higher |higher
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #6 from Storm Engineer hewanci@gmail.com --- Created attachment 59542 --> https://bugs.winehq.org/attachment.cgi?id=59542 Screenshot
For clarification
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #7 from Storm Engineer hewanci@gmail.com --- UPDATE:
"winetricks dotnet40" + "winetricks --force ie8" fixed it.
I wait a bit to see if it keeps working before I mark it Resolved.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #8 from Storm Engineer hewanci@gmail.com --- UPDATE 2:
It's NOT fixed. :((( Somehow my Wine version got set to XP... I figufred this when I tried to play and SC2 refused to start.
Set it back to Win 7 and it's broken again.
https://bugs.winehq.org/show_bug.cgi?id=43910
PeterG peter.g.anderson@live.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson@live.co.uk
--- Comment #9 from PeterG peter.g.anderson@live.co.uk --- Can you run this in a terminal and report the output please?
<code> pacman -Qs freetype2 </code>
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #10 from PeterG peter.g.anderson@live.co.uk --- (In reply to PeterG from comment #9)
Can you run this in a terminal and report the output please?
pacman -Qs freetype2
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #11 from Storm Engineer hewanci@gmail.com --- (In reply to PeterG from comment #9)
Can you run this in a terminal and report the output please?
<code> pacman -Qs freetype2 </code>
freetype2 2.8.1-1 lib32-freetype2 2.8.1-1
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #12 from PeterG peter.g.anderson@live.co.uk --- Try downgrading to freetype2 2.7.1-2 and lib32-freetype2 2.7.1-2
There is a problem with 2.8 currently. This should fix it after a reboot.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #13 from Nikolay Sivov bunglehead@gmail.com --- Wine 2.18 already has a fix for freetype 2.8.1. Why do you think this libcef crash is related at all?
https://bugs.winehq.org/show_bug.cgi?id=43910
LMnet lmnet89@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lmnet89@gmail.com
--- Comment #14 from LMnet lmnet89@gmail.com --- I have the same issue - Battle.net just crashed after a few moments after the start. Wine 2.19, Kubuntu 16.04.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #15 from Storm Engineer hewanci@gmail.com --- (In reply to LMnet from comment #14)
I have the same issue - Battle.net just crashed after a few moments after the start. Wine 2.19, Kubuntu 16.04.
It's NOT the same issue then. My Battle.net did NOT crash.
"Battle.net helper.exe" did.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #16 from Storm Engineer hewanci@gmail.com --- Downgrading to freetype2 2.7.1-2 and lib32-freetype2 2.7.1-2 did not fix it.
Upgrading Wine to Staging 2.19 did not fix it either.
https://bugs.winehq.org/show_bug.cgi?id=43910
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #17 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to Storm Engineer from comment #16)
Downgrading to freetype2 2.7.1-2 and lib32-freetype2 2.7.1-2 did not fix it.
Upgrading Wine to Staging 2.19 did not fix it either.
As this seems related to libcef, does adding --no-sandbox to the commandline help anything?
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #18 from Storm Engineer hewanci@gmail.com --- (In reply to Louis Lenders from comment #17)
does adding --no-sandbox to the commandline help anything?
Nope. :(
https://bugs.winehq.org/show_bug.cgi?id=43910
Solovej incr2014@yandex.ua changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |incr2014@yandex.ua
--- Comment #19 from Solovej incr2014@yandex.ua --- It seems that I have the same problem as https://bugs.winehq.org/show_bug.cgi?id=43910#c14 here. When the emulated OS version in winecfg is set to "Windows XP" everything works fine, but since Blizzard stopped support for WinXP this is not an option. When set to anything else (Windows 7, 8, 8.1, whatever) the Battle.net window shows for a few seconds and then crashes.
Ubuntu 16.04, 64bit, upgraded to wine-2.20, tried both 32 and 64 bit prefixes but it still crashes.
Should I post a separate bugreport?
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #20 from Storm Engineer hewanci@gmail.com --- My bug is _not_ about Blizzard app crashing. So yes, please post a separate ticket.(In reply to Solovej from comment #19)
It seems that I have the same problem as https://bugs.winehq.org/show_bug.cgi?id=43910#c14 here. [...] Should I post a separate bugreport?
As I have pointed out several times, my issue is _not_ Blizzard app crashing. So please make a separate ticket.
https://bugs.winehq.org/show_bug.cgi?id=43910
Storm Engineer hewanci@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|"Battle.net helper.exe" |"Battle.net helper.exe" |crashes with Win 7 or |[NOT BLIZZARD APP!] crashes |higher |with Win 7 or higher
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #21 from Storm Engineer hewanci@gmail.com --- Sorry, messed up the reply editing a bit.
https://bugs.winehq.org/show_bug.cgi?id=43910
Bloody Iron bloodyiron@lanified.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bloodyiron@lanified.com
--- Comment #22 from Bloody Iron bloodyiron@lanified.com --- I'm having the same issue where no matter what, the Battlenet Helper will crash when Windows is set to 7 or higher. Setting it to XP "fixes" it.
However, this effectively completely blocks Overwatch as it won't let me install or run it, since it sees Windows XP!
This is actually a component of the Battlenet App, so this bug report definitely belongs here. You cannot separate the two components, ergo this is directly Battlenet App related.
https://bugs.winehq.org/show_bug.cgi?id=43910
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=43910
tisi kisi@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kisi@protonmail.com
--- Comment #23 from tisi kisi@protonmail.com --- I got the error from helper to go away by adding new configuration in winecfg for battle.net helper.exe
I set it to xp and could login to battle.net again. also this fixed some games for me.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #24 from Bloody Iron bloodyiron@lanified.com --- Considering that Blizzard is working towards dropping XP completely, this seems very likely to break in the future.
(In reply to tisi from comment #23)
I got the error from helper to go away by adding new configuration in winecfg for battle.net helper.exe
I set it to xp and could login to battle.net again. also this fixed some games for me.
https://bugs.winehq.org/show_bug.cgi?id=43910
lukas.schneiderbauer@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lukas.schneiderbauer@gmail. | |com
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #25 from Storm Engineer hewanci@gmail.com --- (In reply to tisi from comment #23)
I got the error from helper to go away by adding new configuration in winecfg for battle.net helper.exe
I set it to xp and could login to battle.net again. also this fixed some games for me.
Forgive my ignorance but how does one make custom settings for individual executables? I tried Googling this several times and found nothing.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #26 from Storm Engineer hewanci@gmail.com --- Still an issue with Staging 2.21-1
This renders the following features completely broken: - Social tab - Chats - Groups - Store - News - Ability to start voice calls - Gifting
https://bugs.winehq.org/show_bug.cgi?id=43910
Chalupa Jack chalupa.jack@outlook.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chalupa.jack@outlook.com
--- Comment #27 from Chalupa Jack chalupa.jack@outlook.com --- Hey Storm -
I was having this very same issue - decided to do a fresh install of linux and didn't realize Blizzard disabled XP leaving me unable to play these games at all.
What ended up working for me was using PlayOnLinux to set up a fresh wine prefix (you may very well be more skilled than me and be more comfortable without PoL - it's obviously not a requirement). I basically followed the "how-to" on the appdb page using PoL. So I pretty much just installed mscorefonts, changed the wine version to 2.21 staging (not sure how this would vary from 2.21-1 as that wasn't available to me) and set the Windows version to 7 in winecfg. Everything seems to be working as it did before and I'm currently installing Diablo 3 again. I used a 32-bit wine prefix instead of 64 since I've never had any luck with the 64-bit game clients running very well.
I realize you may have gone through all of this, but knowing how frustrating it can be myself, I wanted to share it in the hopes it might help. I also know Arch is an entirely different animal from Linux Mint, so I wish you luck!
Chalupa
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #28 from Chalupa Jack chalupa.jack@outlook.com --- (In reply to Storm Engineer from comment #26)
Still an issue with Staging 2.21-1
This renders the following features completely broken:
- Social tab
- Chats
- Groups
- Store
- News
- Ability to start voice calls
- Gifting
I'm new to this comment system, so in the hopes this generates a notification, I left you a reply in the main thread.
https://bugs.winehq.org/show_bug.cgi?id=43910
lord.airivis@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lord.airivis@gmail.com
--- Comment #29 from lord.airivis@gmail.com --- Created attachment 60232 --> https://bugs.winehq.org/attachment.cgi?id=60232 Battle.net Helper.exe
This bug is still crashing, seems like it might be related to libcef
https://bugs.winehq.org/show_bug.cgi?id=43910
adrussel@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adrussel@hotmail.com
--- Comment #30 from adrussel@hotmail.com --- The workaround of setting Battle.net Helper to Windows XP has stopped working for me. Is this the case for anyone else?
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #31 from LMnet lmnet89@gmail.com --- (In reply to adrussel from comment #30)
The workaround of setting Battle.net Helper to Windows XP has stopped working for me. Is this the case for anyone else?
For me too.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #32 from Storm Engineer hewanci@gmail.com --- (In reply to Chalupa Jack from comment #27)
set the Windows version to 7 in winecfg.
The only difference seems to be that you used 32 bit prefix. Mine is 64 and didn't have an issue before. The rest (PoL, Mint) should not make a difference.
Anyone else who uses 64 bit prefix and has the issue, or uses 32 and doesn't?
https://bugs.winehq.org/show_bug.cgi?id=43910
Storm Engineer hewanci@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major
--- Comment #33 from Storm Engineer hewanci@gmail.com --- The issue just became worse. Apparently Blizz gradually pushes whatever new solution it has to parts of the Blizz app client.
As of today, not even the news displayed on games' launch page work anymore, and now the message about Helper crashing comes up constantly just from running the client.
Literally the ONLY feature that still works is playing games... but for how long?
Before we know, the Play buttons won't load either and we won't be able to play...
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #34 from lord.airivis@gmail.com --- (In reply to Storm Engineer from comment #32)
(In reply to Chalupa Jack from comment #27)
set the Windows version to 7 in winecfg.
The only difference seems to be that you used 32 bit prefix. Mine is 64 and didn't have an issue before. The rest (PoL, Mint) should not make a difference.
Anyone else who uses 64 bit prefix and has the issue, or uses 32 and doesn't?
Just did a clean install on a 64-bit prefix using PoL, no overrides, wine-staging 2.21. Had to change Windows version to XP to get the client installed as it would not complete using Windows 7, but once it was installed I could change the Windows version to Windows 7 and was able to install Hearthstone through the client. All web content in the BNet launcher loads successfully and Battle.net Helper.exe did not crash for me. It seems as though this bug is only affecting installs on 32-bit prefixes.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #35 from Storm Engineer hewanci@gmail.com --- (In reply to lord.airivis from comment #34)
It seems as though this bug is only affecting installs on 32-bit prefixes.
But it affects me on a 64 bit prefix.
I will try to make a fresh 64 bit prefix without PoL and see what happens.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #36 from lord.airivis@gmail.com --- (In reply to Storm Engineer from comment #35)
(In reply to lord.airivis from comment #34)
It seems as though this bug is only affecting installs on 32-bit prefixes.
But it affects me on a 64 bit prefix.
I will try to make a fresh 64 bit prefix without PoL and see what happens.
I must have missed that, sorry. I was able to generate a crash in my install, but interestingly enough only a single instance of it (i.e. bnet helper.exe would crash once each time) when browsing to the SCII tab and the client attempts to load the web content for the page. The content then loads shows an error message with an HTTP 500 error. Scrolling through the crashdump the crash seems to occur with the libcef library, which is the same thing I was seeing in my 32-bit install when bnet helper.exe would crash.
https://bugs.winehq.org/show_bug.cgi?id=43910
krovikan@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |krovikan@gmail.com
--- Comment #37 from krovikan@gmail.com --- Is curious.
I have all well (feed, ettc) but if I click in DIablo 3 section, an error shows me as Battle.net Helper.exe to close by error. Don't load feed in Diablo 3 but the others games have the feed OK, Social OK, Shop OK, News OK.
The error is only in the section of Diablo 3.
In my case, when I run the app crashes Blizzard Survey. :S
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #38 from lord.airivis@gmail.com --- (In reply to krovikan from comment #37)
I have all well (feed, ettc) but if I click in DIablo 3 section, an error shows me as Battle.net Helper.exe to close by error. Don't load feed in Diablo 3 but the others games have the feed OK, Social OK, Shop OK, News OK.
The error is only in the section of Diablo 3.
In my case, when I run the app crashes Blizzard Survey. :S
This is the same behavior I am seeing as well: System Survey crashes on client launch, Diablo 3 tab crashes BNet Helper.exe, and additionally the Overwatch League tab crashes BNet Helper.exe. Otherwise the client works perfectly.
In my previous comment, I mentioned that it was crashing when clicking the SCII tab, but this has resolved on its own and has now resulted in the above described behavior, which leads me to believe that there is some dynamic web content that the BNet Helper.exe is having trouble loading. Are there Flash elements on these pages or something?
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #39 from Storm Engineer hewanci@gmail.com --- For me Bnet helper still crashes everywhere: news feed of every game, Social, league, Shop, Gifts, Groups...
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #40 from Storm Engineer hewanci@gmail.com --- As of today the app stopped working completely.
After login I get this error: https://us.battle.net/support/en/article/12706
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #41 from Storm Engineer hewanci@gmail.com --- UPDATE!
After downgrading nvidia drivers solved my graphics error, I have noticed that most things in Battle.net work now.
I assume this is the side effect of my creating a clean prefix while trying to solve said graphics error.
The only things that still crash Battle.net Helper.exe: - Overwatch League tab - News for these games: Diablo 3, HotS, Overwatch.*
*News for everything else, including the News tab itself do work, curiously.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #42 from Storm Engineer hewanci@gmail.com ---
From today, the News tab for Overwatch doesn't crash the Helper anymore, while
News for HotS and Dio3 as well as the OW League tab still do.
This leads me to hypothesize that whatever is crashing is an older technology and Blizzard is gradually upgrading the News reels for games to the newer tech that does work. If that is the case, then hopefully with time this issue will be gone.
But this is just a theory.
https://bugs.winehq.org/show_bug.cgi?id=43910
mephisto123@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mephisto123@gmail.com
--- Comment #43 from mephisto123@gmail.com --- As a workaround, set Client.HardwareAcceleration to false in the Users%username%\Application Data\Battle.net\Battle.net.config file. If there is no such option, just create it.
Example: { "Client": { "HardwareAcceleration": "false" } }
Helped me to launch the client for the first time (since there is no access to the settings menu if you launch it for the first time I had to figure out how to adapt the workaround mentioned on the app winehq page to editing the config manually).
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #44 from Storm Engineer hewanci@gmail.com --- (In reply to mephisto123 from comment #43)
As a workaround, set Client.HardwareAcceleration to false
Please read the title of the bug before commenting.
For the hundredth time, this bug is _NOT_ about Blizzard app crashing...
It's about the helper.exe crash which is unrelated. This does NOT stop Blizz app from launching and disabling hw acceleration does NOT fix it.
P.s.: Issue still present as of today.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #45 from Storm Engineer hewanci@gmail.com --- (In reply to Storm Engineer from comment #42)
From today, the News tab for Overwatch doesn't crash the Helper anymore, while News for HotS and Dio3 as well as the OW League tab still do.
This leads me to hypothesize that whatever is crashing is an older technology and Blizzard is gradually upgrading the News reels for games to the newer tech that does work. If that is the case, then hopefully with time this issue will be gone.
But this is just a theory.
And now Overwatch tab crashes again, so my theory was false.
https://bugs.winehq.org/show_bug.cgi?id=43910
Maciej Stanczew maciej.stanczew+b@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com
--- Comment #46 from Maciej Stanczew maciej.stanczew+b@gmail.com --- The crashes seem random, but they are definitely dependent on news items that are being displayed for the game. For example, right now for me news for HS and SC1 are working, but D3, SC2, HotS and WoW crash. Yesterday WoW also worked; and a couple of days earlier D3 worked, but HS crashed.
The error given in all cases is "BLZBNTBNA000001F4 (503)", which is explained on support page [1] as "Battle.net desktop app's internal web browser crashed". The crashdump is also different than before (I have attached the current one).
Another thing that started happening after one of the latest Battle.net upgrades is that after the crash, the background behind news items will permanently become white, even after switching to a different (non-crashing) game page. I attached 3 screenshots that describe the issue.
Good thing is that Social, Shop and News tabs are not crashing (Overwatch League however is), and playing the games is still possible.
[1] https://battle.net/support/en/article/BLZBNTBNA000001F4
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #47 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61578 --> https://bugs.winehq.org/attachment.cgi?id=61578 Backtrace for game page crash
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #48 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61579 --> https://bugs.winehq.org/attachment.cgi?id=61579 White background #1 - before the crash
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #49 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61580 --> https://bugs.winehq.org/attachment.cgi?id=61580 White background #2 - the crash itself
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #50 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61581 --> https://bugs.winehq.org/attachment.cgi?id=61581 White background #3 - after the crash
https://bugs.winehq.org/show_bug.cgi?id=43910
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #51 from Storm Engineer hewanci@gmail.com --- (In reply to Maciej Stanczew from comment #46)
[...]
Just confirming that I experience the same.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #52 from PeterG peter.g.anderson@live.co.uk --- There is a workaround for this.
Modify your shortcut to launch
...../drive_c/Program Files (x86)/Battle.net/Battle.net.exe
rather than
...../drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe
This stops the Battle.net Helper.exe crashes from occuring.
Using wine-staging-pba-git-3.10 on Arch
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #53 from PeterG peter.g.anderson@live.co.uk --- Here is the full line from my shortcup to launch Ballt.net as a reference. The path will differ fir everyone else of course.
Exec=env WINEPREFIX="/wow" __GL_SHADER_DISK_CACHE_PATH="/wow/drive_c/wow/GLCache" __GL_THREADED_OPTIMIZATIONS=0 STAGING_SHARED_MEMORY=1 WINEDEBUG=-all /usr/bin/wine "/wow/drive_c/Program Files (x86)/Battle.net/Battle.net.exe"
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #54 from krovikan@gmail.com --- Works as a charm. Only "SystemSurvey.exe" crash.
I try login and click in all games and the error with "Battle.net helper.exe" it has disappeared.
My line for run Battle.net is:
__GL_THREADED_OPTIMIZATIONS=0 __GL_YIELD=NOTHING wine '/mnt/juegos/wine/drive_c/Program Files (x86)/Battle.net/Battle.net.exe'
My version of wine is:
Wine-staging 3.10 base (without pba or dxvk).
Thanks Peter!
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #55 from lord.airivis@gmail.com --- (In reply to krovikan from comment #54)
Works as a charm. Only "SystemSurvey.exe" crash.
I try login and click in all games and the error with "Battle.net helper.exe" it has disappeared.
My line for run Battle.net is:
__GL_THREADED_OPTIMIZATIONS=0 __GL_YIELD=NOTHING wine '/mnt/juegos/wine/drive_c/Program Files (x86)/Battle.net/Battle.net.exe'
My version of wine is:
Wine-staging 3.10 base (without pba or dxvk).
Thanks Peter!
Still receiving Battle.net Helper.exe crashes with this method on wine-staging 3.11. After killing all Battle.net-related processes, I relaunched the client using a shortcut to Battle.net.exe rather than Battle.net Launcher.exe and as of right now I'm still getting Battle.net Helper.exe crashes when I try to switch to the Starcraft II pane in the launcher. It's related to the client trying to load web content.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #56 from Maciej Stanczew maciej.stanczew+b@gmail.com --- (In reply to PeterG from comment #52)
There is a workaround for this. Modify your shortcut to launch ...../drive_c/Program Files (x86)/Battle.net/Battle.net.exe rather than ...../drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe This stops the Battle.net Helper.exe crashes from occuring.
It sounded too good to be true, but now I can confirm that it does indeed stop the crashes. Does anyone have any idea why this could be? According to an official response, we should be using Launcher.exe: https://us.battle.net/forums/en/bnet/topic/12673099800
(In reply to lord.airivis from comment #55)
Still receiving Battle.net Helper.exe crashes with this method on wine-staging 3.11. After killing all Battle.net-related processes, I relaunched the client using a shortcut to Battle.net.exe rather than Battle.net Launcher.exe and as of right now I'm still getting Battle.net Helper.exe crashes when I try to switch to the Starcraft II pane in the launcher. It's related to the client trying to load web content.
Yes, but this is a separate crash -- it gives a different backtrace (attached), and it only happens (right now) in Starcraft II. If you use Launcher.exe, the crash occurs in almost every game page.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #57 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Created attachment 61690 --> https://bugs.winehq.org/attachment.cgi?id=61690 Backtrace for SC2-specific crash
The crash is mostly stopped when "Battle.net.exe" is used instead of "Battle.net Launcher.exe", but for SC2 a different crash appears then. The SC2 page tries to display a Twitch video before the crash occurs.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #58 from Storm Engineer hewanci@gmail.com --- (In reply to PeterG from comment #52)
There is a workaround for this.
Modify your shortcut to launch
...../drive_c/Program Files (x86)/Battle.net/Battle.net.exe
DAMN! Amazingly this really works. Makes me wonder then what is supposed to be the purpose of the "launcher.exe" then, if it's not even needed?
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #59 from Storm Engineer hewanci@gmail.com --- (In reply to Maciej Stanczew from comment #57)
SC2 page tries to display a Twitch video before the crash occurs.
I doN1t have the crash for the SC 2 page but it doesn't seem to have thw Twitch video anymore - however, going to the Overwatch League tab the crash will happen when the Twitch video on that tab tries to load.
So it seems confirmed this crash is specifically triggered by Twitch videos.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #60 from Storm Engineer hewanci@gmail.com --- Oh, and running the non-launcher exe also fixed a tiny little annoyance I had: When battle net updates, clicking "restart Battle.net now" used to just close it and not restart, but now the restart works too.
A friend of mine guess the launcher's purpose might be to make updating possible on Windows by requesting admin permissions - which is not needed for Wine obviously.
https://bugs.winehq.org/show_bug.cgi?id=43910
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com
--- Comment #61 from Jacek Caban jacek@codeweavers.com --- The patch from bug 41573 fixes this bug as well. Please test with that patch.
https://bugs.winehq.org/show_bug.cgi?id=43910
--- Comment #62 from Maciej Stanczew maciej.stanczew+b@gmail.com --- (In reply to Jacek Caban from comment #61)
The patch from bug 41573 fixes this bug as well. Please test with that patch.
Can confirm it works when applied to Wine Staging 3.13 -- both SystemSurvey and the original case of Battle.net Helper don't crash anymore.
However Battle.net Helper still crashes when trying to load Twitch videos, but I guess this should be submitted as a separate bug.
https://bugs.winehq.org/show_bug.cgi?id=43910
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |STAGED CC| |leslie_alistair@hotmail.com Staged patchset| |https://github.com/wine-sta | |ging/wine-staging/tree/mast | |er/patches/kernel32-AttachC | |onsole Ever confirmed|0 |1
https://bugs.winehq.org/show_bug.cgi?id=43910
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|STAGED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #63 from Gijs Vermeulen gijsvrm@gmail.com --- Since the patch fixes both this bug and bug 41573, I'm marking this one as a duplicate.
*** This bug has been marked as a duplicate of bug 41573 ***
https://bugs.winehq.org/show_bug.cgi?id=43910
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #64 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Duplicate
-
wine-bugs＠winehq.org