[Bug 57727] New: Battle.net fails to update World of Warcraft
https://bugs.winehq.org/show_bug.cgi?id=57727 Bug ID: 57727 Summary: Battle.net fails to update World of Warcraft Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: smoerrebroed(a)souls-of-midgard.de Distribution: --- Starting last week, there seem to be some issues with properly finishing a game update in Battle.net, namely World of Warcraft. Many users around the world seem to experience an issue where Battle.net stops at ~ 400 MB downloaded and gives an internal error message: https://eu.forums.blizzard.com/en/wow/t/blzbntagt00000840-something-went-wro... On proper Windows, there is no such error with the current update. Moreover, also some older versions of Proton seem to not have this issue, so it looks like there is something in Wine that's causing this. Tested with Wine 10.0 as well as with 9.22 and 9.17 - no difference -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://eu.forums.blizzard. | |com/en/wow/t/blzbntagt00000 | |840-something-went-wrong-wi | |th-a-file/557445 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Please attach the console output. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 lyon(a)pvfree.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lyon(a)pvfree.net --- Comment #2 from lyon(a)pvfree.net --- Created attachment 77931 --> https://bugs.winehq.org/attachment.cgi?id=77931 console output Same issue with wine-staging 10.0.0~bookworm-1 (Debian 12, amd64 arch). Any game fails to install or update with Battle.net error BLZBNTAGT00000840. Apparently this is only happening with updater Agent.8988 as following workaround works if you happen to have an older Agent version still available: https://www.reddit.com/r/linux_gaming/comments/1i316by/guide_to_fix_bnet_age... Console output attached with Agent.8988 version used (no debug tracing enabled). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 --- Comment #3 from lyon(a)pvfree.net --- Interestingly, the Proton changelog from Jan 17 states: "update wine to bleeding-edge (fixes battle.net broken updates)" https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton9-... Not sure what this "bleeding edge" is but it looks like Valve's fork which Proton uses. The relevant Proton commit is this one https://github.com/GloriousEggroll/proton-ge-custom/commit/3367b11bb49c086ec... This leads to a few crypt32 related commits that seem to have been backported to vanilla Wine on Jan 22: https://gitlab.winehq.org/wine/wine/-/merge_requests/7117/commits This make sense as I've seen at least one forum post related to a BLZBNTAGT00000840 error versus certificate issue from a Windows 11 user and the crypt32 module changes seem to be certificate related. As I can't do a Wine rebuild right now I'll wait for the next official build that I believe will fix this bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 --- Comment #4 from lyon(a)pvfree.net --- Also forgot to mention this bug is likely related to https://bugs.winehq.org/show_bug.cgi?id=56559. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 kolAflash <kolAflash(a)kolahilft.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kolAflash(a)kolahilft.de --- Comment #5 from kolAflash <kolAflash(a)kolahilft.de> --- Compiled current Wine master (1f23d8934), including the mentioned commits. https://gitlab.winehq.org/wine/wine/-/merge_requests/7117/commits Thanks for those! Basically they seem to fix the issue. But it seems a clean Wine prefix or additionally fiddling is needed. What happened: 1. The problem persisted on an existing Wine prefix. 2. I successfully used the workaround and updated StarCraft-II (one Battle.net game). (emptied "Agent.8988" directory and "chattr +i" it, so the older "Agent.8868" is being used) 3. I removed the workaround. ("chattr -i" and restored a backup of the "Agent.8868" directory) 4. Successfully updated Diablo-II (another Battle.net game) Seems like something had to happen in the background before the mentioned commits successfully fix the issue. I guess it would have worked without the workaround after restarting Wine one more time, or also on a clean Wine prefix. P.S. Some more affected users. https://us.forums.blizzard.com/en/blizzard/t/unable-to-update-games-with-err... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57727 --- Comment #6 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- Hmmh, while my installation worked on Monday, I started Battle.net again today and it told me to update WoW once more. This time around I received the blzbntagt00000840 error again. After reinstalling Battle.net everything works. Any ideas? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla