[Bug 53697] New: Battle.net Agent.8009/Agent.exe not working (installing Battle.net client and updating games) (2022-09-17)
https://bugs.winehq.org/show_bug.cgi?id=53697 Bug ID: 53697 Summary: Battle.net Agent.8009/Agent.exe not working (installing Battle.net client and updating games) (2022-09-17) Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- Created attachment 73102 --> https://bugs.winehq.org/attachment.cgi?id=73102 STDOUT/STDERR log (Battle.net client installation) At about 2022-09-17 Blizzard released a new Agent.8009\Agent.exe (5.346.640 bytes) replacing the previous Agent.7984\Agent.exe (5.549.912 bytes) It's is usually placed in one of these folders: WINE C: ProgramData/Battle.net/Agent/ WINE C: users/Public/Application Data/Battle.net/Agent/ Note: This is NOT about the other file named "Agent.exe" (about 595.792 bytes) in the "Agent" folder above. DETAILS With the new Agent.8009/Agent.exe the Battle.net client isn't able to install. wine-7.17 and wine-staging-7.17: And an already installed Battle.net isn't able to update games. The progress is just stuck at 0%. It looks like Agent.exe is continuously crashing and being restarted in background. wine-7.17: When installing Battle.net with you get an hard error "BLZBNTAGT000008FC". wine-staging-7.17: The progress is just stuck at 0%. (similar to when updating games) REPRODUCTION OS: Debian-11 1. Download Battle.net client setup. https://eu.battle.net/download/getInstaller?os=win&installer=Battle.net-Setu... https://www.battle.net/download/getInstallerForGame?os=win&gameProgram=BATTL... Currently: 4.838.352 bytes 2. Run Battle.net-Setup.exe in a new Wine prefix and click trough the update process. 3. wine-7.17: You get the error "BLZBNTAGT000008FC". wine-staging-7.17: The installation process is stuck at "Installing Battle.net... (0%)". WORKAROUNDS Updating games: Replace Agent.exe in "Agent.8009\" folder with old "Agent.7984\Agent.exe". Installing Battle.net with wine-staging-7.17: Just replace the file while the installing process is being stuck. Afterwards the installation should automatically continue. Installing Battle.net with wine-7.17: DIFFICULT -> try to use wine-staging-7.17 instead! Run Battle.net-Setup.exe once until you get the "BLZBNTAGT000008FC" error. Then close the setup and place Agent.exe version 7984 in that folder an protect it from being overwritten. sudo chattr +i /path/to/Agent.8009/ (may only work on ext4 filesystems) Important: Use "chattr" on the folder "Agent.8009", not on the "Agent.exe" file. The run the Battle.net setup again. You won't be able to delete the "Agent.8009" folder until you run the reverse command sudo chattr -i /path/to/Agent.8009/ SEE ALSO https://www.reddit.com/r/linux_gaming/comments/xgb5fx/problems_with_battlene... https://us.forums.blizzard.com/en/blizzard/t/last-update-completely-breaks-w... -- 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=53697 --- Comment #1 from kolAflash <kolAflash(a)kolahilft.de> --- Someone posted the old Agent.7984/Agent.exe for download at Reddit. (for WORKAROUND) https://www.reddit.com/r/linux_gaming/comments/xgb5fx/problems_with_battlene... -- 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=53697 Daniel <danieL(a)m2.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danieL(a)m2.nz -- 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=53697 johannes(a)the.homestead.dk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannes(a)the.homestead.dk --- Comment #2 from johannes(a)the.homestead.dk --- I built the nightlies with https://github.com/Frogging-Family/wine-tkg-git and it doesn't have the problem. -- 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=53697 jhu543369(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhu543369(a)gmail.com --- Comment #3 from jhu543369(a)gmail.com --- Can you check the ProgramData/Battle.net/Agent/Agent.8009/Errors folder and see if you are still getting errors reported? -- 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=53697 agurenko(a)protonmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agurenko(a)protonmail.com -- 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=53697 Jens N <jens.n(a)godlike.biz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jens.n(a)godlike.biz --- Comment #4 from Jens N <jens.n(a)godlike.biz> --- (In reply to kolAflash from comment #0)
WORKAROUNDS
Updating games: Replace Agent.exe in "Agent.8009\" folder with old "Agent.7984\Agent.exe".
Installing Battle.net with wine-staging-7.17: Just replace the file while the installing process is being stuck. Afterwards the installation should automatically continue.
Installing Battle.net with wine-7.17: DIFFICULT -> try to use wine-staging-7.17 instead! Run Battle.net-Setup.exe once until you get the "BLZBNTAGT000008FC" error. Then close the setup and place Agent.exe version 7984 in that folder an protect it from being overwritten. sudo chattr +i /path/to/Agent.8009/ (may only work on ext4 filesystems) Important: Use "chattr" on the folder "Agent.8009", not on the "Agent.exe" file. The run the Battle.net setup again. You won't be able to delete the "Agent.8009" folder until you run the reverse command sudo chattr -i /path/to/Agent.8009/
SEE ALSO https://www.reddit.com/r/linux_gaming/comments/xgb5fx/ problems_with_battlenet_today/ https://us.forums.blizzard.com/en/blizzard/t/last-update-completely-breaks- wine-compatibility/33122/11
I've made a script to simplify the workaround, but unfortunally I'm not having any success with it. Did they break that as well? I'll try to attach the shell script I made for that. -- 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=53697 --- Comment #5 from Jens N <jens.n(a)godlike.biz> --- Created attachment 73117 --> https://bugs.winehq.org/attachment.cgi?id=73117 Shell Script I'm using as a workaround Has to be executed with sudo for the write-protection to work (according to the workaround description that should only be needed for fresh installs) and includes a md5 check of the source file to ensure no sketchy exe files are injected for those who download it. - If you have not installed your battlenet wine-prefix under "~/Games/battlenet" you need to adjust line 3 accordingly. - If you don't have the 7984 Version of the Agent.exe in the default location you need to adjust line 5 as well. -- 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=53697 --- Comment #6 from Jens N <jens.n(a)godlike.biz> --- Comment on attachment 73102 --> https://bugs.winehq.org/attachment.cgi?id=73102 STDOUT/STDERR log (Battle.net client installation) Has to be executed with sudo for the write-protection to work (according to the workaround description that should only be needed for fresh installs) and includes a md5 check of the source file to ensure no sketchy exe files are injected for those who download it. - If you have not installed your battlenet wine-prefix under "~/Games/battlenet" you need to adjust line 3 accordingly. - If you don't have the 7984 Version of the Agent.exe in the default location you need to adjust line 5 as well. -- 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=53697 Maarten ter Huurne <maarten(a)treewalker.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maarten(a)treewalker.org --- Comment #7 from Maarten ter Huurne <maarten(a)treewalker.org> --- Created attachment 73118 --> https://bugs.winehq.org/attachment.cgi?id=73118 Crash info file from Battle.net Agent.8009 I'm running into the same issue using wine-7.17 on openSUSE. Lots of people on Reddit are reporting the issue as well; it seems to be very wide-spread. The problems started with the release of Agent version 8009; the previous version 7984 worked fine on the same version of wine with the same configuration. The workaround of replacing Agent.8009/Agent.exe with Agent.7984/Agent.exe and making it immutable worked for me yesterday, but I can't get it to work today. There are many crash logs in ~/.wine/drive_c/ProgramData/Battle.net/Agent/Agent.8009/Errors/. I'll attach a text log; there is a dump file as well, but I don't know what kind of sensitive information that might contain, so I'd rather not post it on a public forum. -- 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=53697 --- Comment #8 from Jens N <jens.n(a)godlike.biz> --- Created attachment 73119 --> https://bugs.winehq.org/attachment.cgi?id=73119 Agent.8009 Crash-Report -- 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=53697 --- Comment #9 from Maarten ter Huurne <maarten(a)treewalker.org> --- (In reply to Tellus from comment #2)
I built the nightlies with https://github.com/Frogging-Family/wine-tkg-git and it doesn't have the problem.
Which configuration are you using? I built "default-tkg" but Agent.8009 still crashes. -- 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=53697 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.com -- 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=53697 --- Comment #10 from Tellus <johannes(a)the.homestead.dk> --- (In reply to Maarten ter Huurne from comment #9)
(In reply to Tellus from comment #2)
I built the nightlies with https://github.com/Frogging-Family/wine-tkg-git and it doesn't have the problem.
Which configuration are you using? I built "default-tkg" but Agent.8009 still crashes.
All defaults, apart from these (which I *think* should be non-consequential):
_nomakepkg_dep_resolution_distro="archlinux" (default is empty) _warframelauncher_fix="false" _win10_default="true"
It seems to be having wake-up issues again today, so maybe the nightly didn't make much of a difference. Turning off automatic updates seems to make it start up and run without issues, though. -- 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=53697 nerzhul <loic.blot(a)unix-experience.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loic.blot(a)unix-experience.f | |r --- Comment #11 from nerzhul <loic.blot(a)unix-experience.fr> --- They just release Agent.8012 it seems but it doesn't work from installation. cat "./Agent.8012/Errors/2022-09-19 20.24.59/Crash-832.txt" An application encountered a critical error: Program: C:/ProgramData/Battle.net/Agent/Agent.8012/Agent.exe Exception: 0xc0000005 (ACCESS_VIOLATION) at 0023:0x29dc The instruction at "0x000029DC" referenced memory at "0x000029DC". The memory could not be executed. <Application>Agent <BlizzardError.ProjectId>1001 <BlizzardError.Module>Agent <BlizzardError.BuildNumber>Agent 2.29.2.8012 <BlizzardError.Platform>All PC <BlizzardError.DesktopOS>Win <BlizzardError.IssueType>Exception <BlizzardError.Priority>None I attach the crash here -- 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=53697 --- Comment #12 from nerzhul <loic.blot(a)unix-experience.fr> --- Created attachment 73125 --> https://bugs.winehq.org/attachment.cgi?id=73125 agent.8012 crash -- 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=53697 josef.schabasser(a)gmx.at changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josef.schabasser(a)gmx.at --- Comment #13 from josef.schabasser(a)gmx.at --- The workaround for v8009 stopped working on v8012. Now the launcher is completely useless, cannot update games or itself - a digital paperweight. It now shows the same behaviour as v8009, even with exe v7984. Cannot install or update anything because another update is in progress. The workaround was: kill bnet, replace Agent.exe with v7984, run `sudo chattr +i Agent.exe`, start bnet. It was slow to a crawl, but installing and updating games worked. It now creates dozens of log files in C:\ProgramData\Battle.net\Agent\Agent.8012\Logs. The most interesting file is AgentErrors-${DATETIME}.log, filled with ``` [E 2022-09-19 20:39:00.0333] Win32Permissions: Win32 SetNamedSecurityInfo(5) - 'C:/ProgramData/Battle.net/Agent/Agent.8012/Agent.exe' [E 2022-09-19 20:39:06.0153] Failed to download url "http://eu.patch.battle.net:1119/osi/bgdl?nocache=2250790220" ``` It's like Blizzard is forcefully driving players away from Linux. -- 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=53697 --- Comment #14 from Mr_nUUb <josef.schabasser(a)gmx.at> --- Forgot to mention tried wine v7.16 (Manjaro package) and lutris-7.2-2, lutris-7.2 and lutris-7.2-fshack. -- 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=53697 --- Comment #15 from kolAflash <kolAflash(a)kolahilft.de> --- Looks like Blizzard today changed something about their server certificates. The workaround for the Battle.net client installation seems still fine. But games aren't downloading any more with the workaround. See: Agent.8012/Logs/AgentNGDP-*.log Log says: [W 2022-09-19 21:26:23.0965] - OCSP Verification Failure: Unsuccessful response status [E 2022-09-19 21:26:23.0966] - Cannot verify the certificate '782a8a710b950421127250a3e91b751ca356e202' So maybe Agent >= 8009 is needed to work with the new certificates :-/ Maybe that upcoming certificate change was the reason Blizzard just updated Agent.exe. Sounds like a standard procedure. But surely the reason also could be, that Blizzard is going to be bought by a company which loves Linux... https://arstechnica.com/gaming/2022/01/microsoft-set-to-purchase-activision-... https://youtu.be/54hHr8ye2kE?t=38 ... ???? I just remembered this: https://www.winehq.org/announce/7.5 What's new in this release: - Initial support for the OCSP protocol. But NO, using Wine-7.4 doesn't workaround that issue. I guess Battle.net brings it's own TLS/SSL implementation. (smart Blizzard, not trusting software they didn't compile themself... one day they may even become one of these Open Source fanatics ????) P.S. More people, same problem: https://forums.lutris.net/t/cant-install-retail-wow-or-wow-classic/16239 -- 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=53697 Yulian Kuncheff <yulian(a)kuncheff.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yulian(a)kuncheff.com --- Comment #16 from Yulian Kuncheff <yulian(a)kuncheff.com> --- Ok, I encourage everyone to minimize non-technical speculation and focus on the technical problem. I agree that they did something with certificates. And there might need to be a Wine patch eventually. For now it seems a new workaround is working after the latest update to 8012. This post on the official forums has instructions: https://us.forums.blizzard.com/en/blizzard/t/last-update-completely-breaks-w... It seems if you change a few settings in the config file, it will still patch and download, but it a lot of errors and take longer. So we should look into (for those that are capable of doing so) what syscalls or dlls the agent is trying to use during those moments. I have little experience debugging Wine, so I don't know if I'll be much help. -- 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=53697 --- Comment #17 from jhu543369(a)gmail.com --- Could some of the issues with 8012 be related to Wrath of the Lich King classic going live this morning and the servers getting overloaded (went live just over 3 hours ago from this comment)? I ask, because I am running 8012 Agent.exe and after around 20 minutes of waiting now, it has started doing the update that I need to run WotLK. I do not have errors with the Agent.exe running but I did update the battle.net.config file enabling the Streaming option. I was able to check if the streaming option was needed in a different bnet install, I was able to update SC2 in that prefix with it enabled, but not WotLK. I have a fresh bottles install of Battle.net I will try next without the streaming option. Either way, 8012 is enabling downloads and only error it threw was when I logged into Battle.net forums (so user error not agent.exe error) -- 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=53697 --- Comment #18 from jhu543369(a)gmail.com --- Starting to think there is a Blizzard problem on the updates. Downloads probably an issue because of global launch of WotLK today, everyone trying to download this and some other content that also dropped. But underneath everything, I noticed that WoW updates fail with a consistent problem: https://us.forums.blizzard.com/en/blizzard/en/blizzard/t/last-update-complet... I have tested this evening these runners: lutris-5.7, lutris-7.2-2, lutris-7.2-fshack, wine-7.17-staging-tkg, wine-5.20, wine-6.23, wine-7.0, Wine-7.2, wine-7.17 (system), wineHQ-7.17 (staging) and lutris-GE-Proton7-29. Looking at just vanilla 7.17 vs 7.17 Staging, vanilla 7.17 goes into an immediate agent.exe crash loop when the client is launched. With staging, agent.exe launches and it is possible to initiate a new download. What isn't working is updating WoW. I have reported the error to Blizzard as it also happened with WotLK when it 99% downloading. https://us.forums.blizzard.com/en/blizzard/en/blizzard/t/agentexe-8012-crash... -- 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=53697 --- Comment #19 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to jhu543369 from comment #18)
Starting to think there is a Blizzard problem on the updates. Downloads probably an issue because of global launch of WotLK today, everyone trying to download this and some other content that also dropped. But underneath everything, I noticed that WoW updates fail with a consistent problem:
https://us.forums.blizzard.com/en/blizzard/en/blizzard/t/last-update- completely-breaks-wine-compatibility/33122/151
I have tested this evening these runners: lutris-5.7, lutris-7.2-2, lutris-7.2-fshack, wine-7.17-staging-tkg, wine-5.20, wine-6.23, wine-7.0, Wine-7.2, wine-7.17 (system), wineHQ-7.17 (staging) and lutris-GE-Proton7-29.
Looking at just vanilla 7.17 vs 7.17 Staging, vanilla 7.17 goes into an immediate agent.exe crash loop when the client is launched. With staging, agent.exe launches and it is possible to initiate a new download. What isn't working is updating WoW. I have reported the error to Blizzard as it also happened with WotLK when it 99% downloading.
https://us.forums.blizzard.com/en/blizzard/en/blizzard/t/agentexe-8012- crashes-trying-to-update-wow-games/33267
You keep mentioning the global launch happened but it hasn't. Launch isn't until next week, Sept. 26. It is Sept 20 right now. And the prepatch has been out for over a week now. This is unrelated to any launches. Also I believe the 404 or connectivity issues are related to be certificates. If it can't setup the certificates properly, it can't make connections to the servers that expect those certificates to exist. Or if it can't verify the certificates, it doesn't trust them and will cause issues. I believe the original errors related to bmime and ocsp are probably the main issue, and the rest is just a side effect of that. If I have time today, I will try to run wine with all the logging set to maximum verbosity and see if I notice anything in the deluge of 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=53697 --- Comment #20 from Mr_nUUb <josef.schabasser(a)gmx.at> --- So I scrolled through https://us.forums.blizzard.com/en/blizzard/t/last-update-completely-breaks-w... and tried * setting `"StreamingEnabled": "true"` in "C:/users/$USERNAME/Application Data/Battle.net/Battle.net.config". It didn't change anything, still crashing with ``` The instruction at "0x00000371" referenced memory at "0x00000371". The memory could not be executed. ``` * using wine lutris-5.7-11. This immediately worked. I can start the launcher again, without it complaining about "another update is in progress", "battle.net agent is inactive" or "oops, something went wrong" or similar. I can't update games (tried Hearthstone and Diablo Immortal), agent crashes again with different messages: ``` The instruction at "0x006F1C1E" referenced memory at "0x006F0072". The memory could not be written. --- The instruction at "0x001200B0" referenced memory at "0x001200B0". The memory could not be executed. --- The instruction at "0x006F1C1E" referenced memory at "0x636F6CC6". The memory could not be read. ``` Updating a game causes the same update loop as with wine 7.2 and 7.16. I didn't test other versions. Using lutris wine is a no-no for me, because it always crashes during gameplay, on loading screens and in the launcher. It also takes the whole environment down (if game crashes, launcher and all wine processes die, too) - everything just freezes. Therefore I prefer distribution packages. -- 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=53697 --- Comment #21 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Yulian Kuncheff from comment #19)
If I have time today, I will try to run wine with all the logging set to maximum verbosity and see if I notice anything in the deluge of output.
If you suspect it's related to OCSP a +cryptnet,+crypt,+cryptasn,+cert,+chain log would be appropriate. -- 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=53697 --- Comment #22 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to Hans Leidekker from comment #21)
(In reply to Yulian Kuncheff from comment #19)
If I have time today, I will try to run wine with all the logging set to maximum verbosity and see if I notice anything in the deluge of output.
If you suspect it's related to OCSP a +cryptnet,+crypt,+cryptasn,+cert,+chain log would be appropriate.
Thank you for those. I had to add `warn` infront of all of those to not be bombarded with traces. I also decided to play around with the Wine Debugger and see what I could get. I do think it something to do with certs based on what I found. Firstly, when launching the Battle.net it complains about an Unsupported Decoder and something not being asserted for a CA. Secondly, when doing the debugger on the agent, I managed to attach to one before it crashed, and the stack trace errors on SHA hashing. I have attached both pieces of log information. I haven't been able to get any wine log output for the Agent.exe file, i think the log output I am providing is from the Battle.net exe file on boot. They might be related, but might not be (hunch: battle.net fails to load a cert/ca, Agent can not validate certs or gets bad SHA data, blows up). I need to figure out why I can no get log output from the Agent.exe of any kind, not even trace. My setup: Fedora 36 Bottles Flatpak WineGE 7-29 Dependencies Installed from winetricks/bottles: d3dx9, msls31, arial32, times32, corie32, d3dcompiler_43, d3dcompile_47 -- 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=53697 --- Comment #23 from Yulian Kuncheff <yulian(a)kuncheff.com> --- Created attachment 73133 --> https://bugs.winehq.org/attachment.cgi?id=73133 WINEDEBUG output for just crypt stuff -- 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=53697 --- Comment #24 from Yulian Kuncheff <yulian(a)kuncheff.com> --- Created attachment 73134 --> https://bugs.winehq.org/attachment.cgi?id=73134 Wine Debugger backtrace/stackdump from Agent.exe crash -- 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=53697 Gerald Tan <woefulwabbit(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |woefulwabbit(a)gmail.com --- Comment #25 from Gerald Tan <woefulwabbit(a)gmail.com> --- I noticed the asn1 objectid 1.3.6.1.4.1.311.2.1.4 being mentioned in the logs. Searching around, I came across https://zakird.com/2012/12/09/microsoft-oids which mentions that Microsoft's OIDs are missing from OpenSSL, and provides code to add them into OpenSSL during initialization. Not sure if this will help. -- 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=53697 --- Comment #26 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to Gerald Tan from comment #25)
I noticed the asn1 objectid 1.3.6.1.4.1.311.2.1.4 being mentioned in the logs.
Searching around, I came across https://zakird.com/2012/12/09/microsoft-oids which mentions that Microsoft's OIDs are missing from OpenSSL, and provides code to add them into OpenSSL during initialization.
Not sure if this will help.
That could be a good lead, but doing a search, I also notice this error show up in January for Battle.net client, and in other games many years ago. I think it might be a red herring? We should still consider it, but it might not be the real issue. Also it comes from Battle.net app, not the Agent. Could just be used for the login step. the SHAFinal might be more accurate. currently working, so don't have much time to dig on that call. -- 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=53697 --- Comment #27 from Yulian Kuncheff <yulian(a)kuncheff.com> --- So I googled A_SHAFinal, and it seems to be a function in wincrypt (https://learn.microsoft.com/en-us/windows/win32/seccrypto/a-shafinal) And it seems this specific function bypasses parts of the crypto stack. There is a Wine version of the header file here: https://github.com/wine-mirror/wine/blob/master/include/wincrypt.h and I noticed in this file there are a bunch of OID things, but the OID listed above is missing from the file. The thing is, when I searched for `A_SHAFinal` in the wine codebase, there was no such function. Maybe its provided by a different file, or its installed as part of a different package, like vs runtimes. Not sure, but it could be a lead to debugging it. -- 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=53697 --- Comment #28 from Zeb Figura <z.figura12(a)gmail.com> --- A_SHAFinal in backtraces is rarely if ever relevant. Note the large offset; that's a consequence of broken or missing debug symbols. -- 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=53697 --- Comment #29 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to Zeb Figura from comment #28)
A_SHAFinal in backtraces is rarely if ever relevant. Note the large offset; that's a consequence of broken or missing debug symbols.
Ah, ok, well I am not sure where to go from here. I don't have enough experience dealing with Wine internals or Windows internals at this level. Im a developer, but i mostly deal with higher level languages and systems like Go and have minimal exposure this kind of stuff in my day to day. -- 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=53697 --- Comment #30 from Gerald Tan <woefulwabbit(a)gmail.com> --- Digging around for the certificate 782a8a710b950421127250a3e91b751ca356e202 I've found a ocsp-782a8a710b950421127250a3e91b751ca356e202-0.bmime file in Agent/data/cache which contains a MIME encoded ocsp cached response. Decoding with openssl ocsp gives: ---- OCSP Response Data: OCSP Response Status: successful (0x0) Response Type: Basic OCSP Response Version: 1 (0x0) Responder Id: B76BA2EAA8AA848C79EAB4DA0F98B2C59576B9F4 Produced At: Sep 13 05:43:11 2022 GMT Responses: Certificate ID: Hash Algorithm: sha1 Issuer Name Hash: E4E395A229D3D4C1C31FF0980C0B4EC0098AABD8 Issuer Key Hash: B76BA2EAA8AA848C79EAB4DA0F98B2C59576B9F4 Serial Number: 0FDFE3B64118DA84F609F78D6DF3EA09 Cert Status: good This Update: Sep 13 05:27:02 2022 GMT Next Update: Sep 20 04:42:02 2022 GMT Signature Algorithm: sha256WithRSAEncryption 09:87:4b:c3:ef:9d:9b:e3:00:98:e9:e4:65:fa:0f:60:ea:59: c1:3d:f6:21:1d:f9:a2:d1:8a:1c:12:d9:db:70:b7:74:32:3e: e7:15:97:92:b6:5f:af:00:7e:9c:42:ab:a0:a2:18:6c:0b:b8: e9:98:05:00:01:dc:1f:85:94:a4:26:21:e0:60:49:31:be:3e: 85:1f:9f:9f:9a:5d:7e:da:39:29:bc:af:dc:7d:54:a4:58:34: e5:82:0b:98:c5:fa:57:d0:5a:30:44:14:7b:75:c6:5f:74:97: 33:0a:f5:1b:a3:bd:0d:3b:c8:cf:fb:47:6e:a7:1e:d0:2f:bc: c3:9c:b5:2a:6e:8f:42:c4:a5:91:72:78:c6:9b:69:05:c1:82: 8b:ae:7c:c8:b9:39:8f:e9:8b:59:06:b9:04:93:81:33:8c:1c: fd:b3:04:7e:80:1f:60:c6:89:f9:59:f2:28:da:4e:0d:4d:7a: ab:96:05:b1:da:89:0e:fe:51:9e:02:ae:16:7a:6d:d5:7b:0e: a7:21:45:b7:dd:d9:9f:cf:b6:bb:7a:9a:bf:97:86:23:92:6f: e5:a8:f0:f6:9a:0e:9f:27:96:f9:d1:74:d4:8b:8e:d4:d1:2e: 32:f6:63:58:3c:7c:c8:54:dd:75:ac:fc:dc:9b:1e:8f:0c:0e: ff:dc:52:17 ---- Which shows that OCSP requests were previously successful. The actual certificate is in cert-782a8a710b950421127250a3e91b751ca356e202-0.bmime Which can be verified to be still valid until 31 Jan 2023. Submitting the certificate to https://decoder.link/ocsp results in a successful ocsp response. Wine has successfully verified the certificate with OCSP previously, back in 13 Sep for my case. So why does it fail now with the latest client? It might not actually be a problem with Wine... -- 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=53697 --- Comment #31 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to Gerald Tan from comment #30)
Digging around for the certificate 782a8a710b950421127250a3e91b751ca356e202
I've found a ocsp-782a8a710b950421127250a3e91b751ca356e202-0.bmime file in Agent/data/cache which contains a MIME encoded ocsp cached response. Decoding with openssl ocsp gives:
---- OCSP Response Data: OCSP Response Status: successful (0x0) Response Type: Basic OCSP Response Version: 1 (0x0) Responder Id: B76BA2EAA8AA848C79EAB4DA0F98B2C59576B9F4 Produced At: Sep 13 05:43:11 2022 GMT Responses: Certificate ID: Hash Algorithm: sha1 Issuer Name Hash: E4E395A229D3D4C1C31FF0980C0B4EC0098AABD8 Issuer Key Hash: B76BA2EAA8AA848C79EAB4DA0F98B2C59576B9F4 Serial Number: 0FDFE3B64118DA84F609F78D6DF3EA09 Cert Status: good This Update: Sep 13 05:27:02 2022 GMT Next Update: Sep 20 04:42:02 2022 GMT
Signature Algorithm: sha256WithRSAEncryption 09:87:4b:c3:ef:9d:9b:e3:00:98:e9:e4:65:fa:0f:60:ea:59: c1:3d:f6:21:1d:f9:a2:d1:8a:1c:12:d9:db:70:b7:74:32:3e: e7:15:97:92:b6:5f:af:00:7e:9c:42:ab:a0:a2:18:6c:0b:b8: e9:98:05:00:01:dc:1f:85:94:a4:26:21:e0:60:49:31:be:3e: 85:1f:9f:9f:9a:5d:7e:da:39:29:bc:af:dc:7d:54:a4:58:34: e5:82:0b:98:c5:fa:57:d0:5a:30:44:14:7b:75:c6:5f:74:97: 33:0a:f5:1b:a3:bd:0d:3b:c8:cf:fb:47:6e:a7:1e:d0:2f:bc: c3:9c:b5:2a:6e:8f:42:c4:a5:91:72:78:c6:9b:69:05:c1:82: 8b:ae:7c:c8:b9:39:8f:e9:8b:59:06:b9:04:93:81:33:8c:1c: fd:b3:04:7e:80:1f:60:c6:89:f9:59:f2:28:da:4e:0d:4d:7a: ab:96:05:b1:da:89:0e:fe:51:9e:02:ae:16:7a:6d:d5:7b:0e: a7:21:45:b7:dd:d9:9f:cf:b6:bb:7a:9a:bf:97:86:23:92:6f: e5:a8:f0:f6:9a:0e:9f:27:96:f9:d1:74:d4:8b:8e:d4:d1:2e: 32:f6:63:58:3c:7c:c8:54:dd:75:ac:fc:dc:9b:1e:8f:0c:0e: ff:dc:52:17 ----
Which shows that OCSP requests were previously successful.
The actual certificate is in cert-782a8a710b950421127250a3e91b751ca356e202-0.bmime
Which can be verified to be still valid until 31 Jan 2023.
Submitting the certificate to https://decoder.link/ocsp results in a successful ocsp response.
Wine has successfully verified the certificate with OCSP previously, back in 13 Sep for my case. So why does it fail now with the latest client? It might not actually be a problem with Wine...
Interestingly, currently that file gets created and deleted immediately in my install and I still occasionally get error logs saying it failed to write the bmime files as an IO Error. Also we should also consider it is not a wine issue. There is a new stickied thread on the official forums with Windows users starting to exhibit similar issues: https://us.forums.blizzard.com/en/blizzard/t/main-thread-agent-went-to-sleep... Wine might be exacerbating a bug that is infrequent on Windows but getting worse -- 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=53697 --- Comment #32 from Gerald Tan <woefulwabbit(a)gmail.com> --- 2022-09-20T21:43:06 {2c4} [DEBUG] - >> Start to download 'v1/certs/782a8a710b950421127250a3e91b751ca356e202' 2022-09-20T21:43:06 {2c4} [DEBUG] - >> Downloaded BMIME(2855 bytes) 2022-09-20T21:43:06 {2c4} [DEBUG] - Failed to find file 'C:/ProgramData/Battle.net/Agent/data/cache/cert-b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4-0.bmime' 2022-09-20T21:43:06 {2c4} [DEBUG] - Failed to load BMIME at C:/ProgramData/Battle.net/Agent/data/cache/cert-b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4-0.bmime: BMIME_E_IO_ERROR Race condition sounds plausible. Based on these logs from the bnet forum, it looks like both the b76ba2eaa8aa848c79eab4da0f98b2c59576b9f4 (DigiCert CA) and 782a8a710b950421127250a3e91b751ca356e202 (Blizzard) certs may be downloading at the same time. Blizzard's cert completes downloading first, and the app fails to open DigiCert's cert to verify Blizzard's cert -- 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=53697 --- Comment #33 from jhu543369(a)gmail.com --- If you delete the ProgramData/Battle.net folder on a windows 10 install, the file ocsp-782a8a710b950421127250a3e91b751ca356e202-0.bmime is generated/copied when battle.net launches and then a whole bunch of other .bmime files associated with various games are generated along with 2 cert***.bmime files. On Linux, the oscp file is not generated/copied and if you watch the cache directory, the 2 cert files are created and deleted multiple times. If you copy over the ocsp bmime file from a working Win 10 Battle.net, on launch all the other bmime game files and the 2 certs are created and remain in the directory. If you then attempt to download a game, it is fine right up when it needs to do the final update. At this point the battle.net.exe hard crashes (logs are found in users/youruser/AppData/local/Battle.net/Errors) as well Agent.exe starts crashing again. -- 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=53697 --- Comment #34 from jhu543369(a)gmail.com --- Created attachment 73138 --> https://bugs.winehq.org/attachment.cgi?id=73138 Battle.net.exe crash file -- 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=53697 --- Comment #35 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to jhu543369 from comment #34)
Created attachment 73138 [details] Battle.net.exe crash file
That libcef.dll error is something that Windows users already hit occasionally also. There is a few threads with the libcef error on the official forums. -- 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=53697 --- Comment #36 from jhu543369(a)gmail.com --- I was just able to replicate the certificate error (ocsp file not present and the cert files being created and deleted in a loop) on a Windows 10 installation that hadn't been updated since April. I did not observe the agent,exe file (which updated to 8012) crashing. -- 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=53697 --- Comment #37 from jhu543369(a)gmail.com --- I updated Windows, deleted the ProgramData\battle.net folder and the launched Battle.net again in my Win 10 drive (not a VM), and the certificate files continued to flash in the data\cache folder. In battle.net, I was able to download and apply updates for PTR, WoW Classic, WoW WotLK and WoW Shadowlands (all quite of date, WotLK I added from a download from last weeked needing an update) all while switching the battle.net launcher to beta mode. While it was not the quickest, and took ages to process, all tasks completed successfully while the cert files flashed. I don't think it is the cert/ospc files causing the problem. It still seems that a call made by agent.exe is not being handled in Wine, and I don't have the tools to see what is being called. -- 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=53697 Pavel <pavel1r(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel1r(a)gmail.com --- Comment #38 from Pavel <pavel1r(a)gmail.com> --- (In reply to jhu543369 from comment #36)
I was just able to replicate the certificate error (ocsp file not present and the cert files being created and deleted in a loop) on a Windows 10 installation that hadn't been updated since April. I did not observe the agent,exe file (which updated to 8012) crashing.
It looks like Blizzard updated Agent.exe to 8012. For me it doesn't crash anymore, but still does not download anything. -- 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=53697 --- Comment #39 from jhu543369(a)gmail.com --- I reported the issue with the ocsp***,bmime file absent to Blizzard last night, and 12 hours later it seems fixed. Also seems that the 8012 is sort of working... This is where it gets really interesting. If there is an update showing as available, the agent will start the download. For World of Warcraft, there was an update of 2.2GB available. This was successfully downloaded and installed but after completing, it would then start another update with initializing for a few moments, move onto reclaiming space on the launcher, the agent would crash and then we would be in a loop of waiting for update, initializing - reclaiming. Other times when there really was an update to process and download, it would complete successfully, then go into the loop described above. In all cases, we are back to the same thing in the error, a call to something "" that is not present resulting in the agent crashing and looping. If a game had an update button from having it added to the launcher rather than downloaded, pressing the update button would progress things (real update or not) to a point where the launcher would say it was playable. Pausing all downloads would stop the agent crash loop. -- 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=53697 Stratos Panagiotidis <stratospanathe1337(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stratospanathe1337(a)gmail.co | |m --- Comment #40 from Stratos Panagiotidis <stratospanathe1337(a)gmail.com> --- This fix worked for me, you have to run the old Agent which I did via duplicating my default Lutris config and pointing it to the old agent, running it then running the original bnet entry. 1. Download that Agent.exe in another comment (edit: here https://cdn.discordapp.com/attachments/538903130704838656/102076352163140410...) 2. Rename/backup old Agent8009/Agent.exe and paste the new one there (ignore the new Agent8012 and make sure you're not running the launcher) 3. In Lutris, right click your bnet entry and Duplicate it 4. Right-click on the duplicate entry, configure and point to the new Agent8009/Agent.exe you downloaded. 5. Run the duplicate Bnet entry in Lutris to load the old Agent 6. Then run your original Bnet entry to load the launcher and it should now update. Tested with WotLK Classic. -- 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=53697 Sjoer van der Ploeg <sfjuocekr(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sfjuocekr(a)gmail.com --- Comment #41 from Sjoer van der Ploeg <sfjuocekr(a)gmail.com> --- When I try 5.7 the Agent won't even start, throws an exception on: ntoskrnl.exe.RtlPcToFileHeader -- 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=53697 --- Comment #42 from jhu543369(a)gmail.com --- (In reply to Stratos Panagiotidis from comment #40)
This fix worked for me, you have to run the old Agent which I did via duplicating my default Lutris config and pointing it to the old agent, running it then running the original bnet entry.
1. Download that Agent.exe in another comment (edit: here https://cdn.discordapp.com/attachments/538903130704838656/ 1020763521631404103/Agent_7984.zip)
2. Rename/backup old Agent8009/Agent.exe and paste the new one there (ignore the new Agent8012 and make sure you're not running the launcher)
3. In Lutris, right click your bnet entry and Duplicate it
4. Right-click on the duplicate entry, configure and point to the new Agent8009/Agent.exe you downloaded.
5. Run the duplicate Bnet entry in Lutris to load the old Agent
6. Then run your original Bnet entry to load the launcher and it should now update. Tested with WotLK Classic.
Have you tried simply removing the data/cache folder, copy the old agent.exe file into the Agent.8012 folder and then restart Battle.net? -- 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=53697 Cliff Hill <winehq(a)darkhelm.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq(a)darkhelm.org --- Comment #43 from Cliff Hill <winehq(a)darkhelm.org> --- So, for those interested, I got everything working again. The process was 3 steps: 1. nvidia drivers for i386 are apparently hard to find now (for Ubuntu 22.04). However they are found in the following ppa: sudo add-apt-repository ppa:oem-solutions-group/nvidia-driver-staging. This made it possible to install Battle.net. 2. I changed the file drive_c/users/<myname>/Application Data/Battle.net/Battle.net.config to be: { "Client": { "GameLaunchWindowBehavior": "2", "HardwareAcceleration": "true", "Sound": { "Enabled": "false" }, "Streaming": { "StreamingEnabled": "true" } } }. This stopped Battle.net.exe from freezing. 3. I grabbed the Agent.exe file from here: https://www.reddit.com/r/linux_gaming/comments/xgb5fx/comment/ioujf9e/ 7 This allowed me to be able to actually install games again. All 3 of those steps were needed in order to be able to make everything work. Hope this helps others. 4. Oh, for WoW randomly freezing, you need to disable fsync, apparently in Lutris. -- 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=53697 --- Comment #44 from Mr_nUUb <josef.schabasser(a)gmx.at> --- * Restoring old Agent.exe: immediately updates and enters crash loop * Restoring old Agent.exe + `chattr -i`: everything slow as hell, not able to install/update, regular error message that something went wrong. * Enabling StreamingEnabled: doesn't change anything * Old wine version: allows anget to start, but not to install or update * Agent v8012: crash loop again All of the workarounds and "it's working again" reports are garbage and momentarily at best. -- 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=53697 --- Comment #45 from Sjoer van der Ploeg <sfjuocekr(a)gmail.com> --- The Agent also spews a lot of threads in its error log: Thread 0x000003f8 DBG-ADDR<7BC0C47C>("ntdll.dll") 7BC5D413 ntdll.dll RtlSleepConditionVariableSRW+147 (sync.c,827) 7B07B6E1 kernelbase.dll SleepConditionVariableSRW+76 (sync.c,57) DBG-ADDR<00667AED>("Agent.exe") DBG-ADDR<005FB8EB>("Agent.exe") DBG-ADDR<005FBAEF>("Agent.exe") DBG-ADDR<0066768E>("Agent.exe") DBG-ADDR<0070D6A4>("Agent.exe") DBG-ADDR<7B62A320>("kernel32.dll") DBG-ADDR<7BC5D497>("ntdll.dll") 7BC5DB70 ntdll.dll RtlCreateUserThread+0 (thread.c,261) Thread 0x000003fc DBG-ADDR<7BC0C4AC>("ntdll.dll") 7B07978D kernelbase.dll WaitForSingleObjectEx+56 (sync.c,334) 6D78FB75 ws2_32.dll select+1557 (socket.c,2737) DBG-ADDR<0063FA53>("Agent.exe") DBG-ADDR<00628C5A>("Agent.exe") DBG-ADDR<00629755>("Agent.exe") DBG-ADDR<0066768E>("Agent.exe") DBG-ADDR<0070D6A4>("Agent.exe") DBG-ADDR<7B62A320>("kernel32.dll") DBG-ADDR<7BC5D497>("ntdll.dll") 7BC5DB70 ntdll.dll RtlCreateUserThread+0 (thread.c,261) It just keeps on looping over scanning game files, I'm 100% sure all the updates are there because when I copied everything over to Windows it didn't change anything. -- 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=53697 --- Comment #46 from jhu543369(a)gmail.com --- (In reply to Mr_nUUb from comment #44)
* Restoring old Agent.exe: immediately updates and enters crash loop * Restoring old Agent.exe + `chattr -i`: everything slow as hell, not able to install/update, regular error message that something went wrong. * Enabling StreamingEnabled: doesn't change anything * Old wine version: allows anget to start, but not to install or update * Agent v8012: crash loop again All of the workarounds and "it's working again" reports are garbage and momentarily at best.
Before you write them off, try one last test: Rename the existing ProgramData/Battle.net folder to something else (make sure Agent.exe and Battle.net.exe processes are not running in the background). Select Wine 7.17 or Wine 7.17-staging as your runner. Confirm what version of Battle.net is installed by looking in the Program Files (x86) folder and noting the highest number Battle.net.xxxxx folder present. If xxxx is 13747, you have the latest version installed. If it is lower than this, disable esync and fsync in Lutris. Run the launcher while monitoring the processes running and the folders in the new ProgramData/Battle.net/Agent folder create. If this has been successful, you will have no games in the launcher, 2 folders under data/cache (b9 and cb), and Agent.8012 with an Agent.exe file of ~5.3mb in size. To see if you have any issues with this, in the launcher select to download World of Warcraft Wrath of the Lich King or Starcraft II (or any free to play game you see, these are the smallest I saw). If you have nothing else going on, these should happily start downloading. If this is the case, you can use locate games to add your existing games. Make sure you change the auto updates to disabled under Settings->Downloads in the launcher. Most games will not let you play, they will show update. Pick one game and press Update. Again, if there are no other issues with your system, this should progress for a while and then change to Play BEFORE entering into the update loop and throwing agent.exe errors. If these tests above were successful, you should be able see that the 8012 Agent sort of works and this is where we need some help from Wine experts to work out what is missing (some call to something is failing and not being recorded in the log file). At this point once you have exited the launcher and confirmed all other Agent.exe and Battle.net.exe processes are killed, you can then replace the Agent.exe file in Agent.8012 with the 7984 version. This is only a temp work around until the next Agent update or someone can figure out what DLL or dependency we need to add to our prefix to stop the 8012 version crashing. -- 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=53697 --- Comment #47 from Yulian Kuncheff <yulian(a)kuncheff.com> --- So, I was determined to get mine to work on a recent version of WineGE. But in frustration I tried the lutris-fshack-5.7-11, and it almost worked, but would get stuck downloading the manifest during initializing. Seeing this, on whim I decided to try the lutris-fshack-7.2, this is on a fresh install of battle.net. It initialized, patched my stuff, and then would get stuck on reclaiming space. But I got a play button. Pressing the play button would launch the game. But I got a black screen doing that. But that's fine, because using my direct launch duplicate in Lutris using the latest WineGE, worked great and I could login and play, meaning my files were in fact updated. This is on my SteamDeck. This definitely points to a regression in Wine somewhere. -- 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=53697 --- Comment #48 from Yulian Kuncheff <yulian(a)kuncheff.com> --- Forgot to add, I turned off ESync, FSync, FSR, runtimes, and each stuff. Only thing turned on was DXVK and such. -- 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=53697 --- Comment #49 from jhu543369(a)gmail.com --- Created attachment 73145 --> https://bugs.winehq.org/attachment.cgi?id=73145 Linux vs Win 10 Agent 8012 download Comparison of the DLL's used during an active download on Linux with agent 8012 and Win 10 also using agent 8012. -- 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=53697 --- Comment #50 from jhu543369(a)gmail.com --- Created attachment 73146 --> https://bugs.winehq.org/attachment.cgi?id=73146 Linux 8012 vs Win 10 7984 Download This image is the Win 10 using the older 7984 dropped into the Agent.8012 folder. If anyone notices anything in these, let me know. Have not been able to get a screenshot of an 8012 Update crashing yet, if I can I will post it as well. -- 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=53697 iddno+winehq(a)pm.me changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iddno+winehq(a)pm.me --- Comment #51 from iddno+winehq(a)pm.me --- Blizzard games like WoW, WoW Beta, WoW classic, WoW PTR etc. work 100% if you start them directly from their .exe file via Lutris and/or Bottles. With almost every wine version there is, like GE-wine for example, or just wine-staging. It is only the Battle.net Launcher and its Agent.exe that is causing problems. You can update the game on a Windows install (VM or real) and copy it over to Linux system, and those games work 100% without the BN Launcher. I write this, so people know, if they don't already know. At least it is a workaround to get the games running until the BN stuff is fixed somehow. -- 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=53697 thomas(a)edb-konsulenterne.dk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas(a)edb-konsulenterne.dk -- 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=53697 Maciej Stanczew <maciej.stanczew+b(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b(a)gmail.com -- 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=53697 --- Comment #52 from nerzhul <loic.blot(a)unix-experience.fr> --- retail is now dead until a launcher bugfix. They update and mark retail as incompatible today. -- 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=53697 --- Comment #53 from Mr_nUUb <josef.schabasser(a)gmx.at> --- I renamed `C:\ProgramData\Battle.net` and `C:\ProgramData\Blizzard Entertainment` and switched to wine lutris-fshack-7.2 (esync and fsync disabled). Bnet Launcher starts up and Agent crashed twice with good old `The memory could not be executed.` crash dumps. I could add my local installations of WoW, HS, D:I and D2R. I tried to scan & repair WoWs files, but it loops and I cancelled its 3rd attempt. Now it needs a ~28GB update. No further crashes, will report after download has finished. -- 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=53697 --- Comment #54 from Mr_nUUb <josef.schabasser(a)gmx.at> --- PS: It's Launcher v13747 and Agent v8012. -- 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=53697 --- Comment #55 from MrNo <iddno+winehq(a)pm.me> --- (In reply to nerzhul from comment #52)
retail is now dead until a launcher bugfix. They update and mark retail as incompatible today.
They don't "mark" it. WoW got an update, therfor your client version is incompatible with the server version. That is why it says "incompatible". As I already said before. Just install a Windows 10 VM and install BN/WoW there and update the game then transfer it over to your Linux system with FTP. Or... if you have a real Windows install somewhere, do it there and copy over the WoW folder after update. Then start the game WITHOUT the BN launcher. It works 100%, I do it every day, I just did it 2 minutes ago with the latest update, too. -- 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=53697 --- Comment #56 from nerzhul <loic.blot(a)unix-experience.fr> --- i say mark because the communication protocol is marked incompatible. And no using windows as a workaround is not a solution, it's just a workaround. I have develop skill, but not wine ones then i cannot troubleshoot it myself -- 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=53697 --- Comment #57 from MrNo <iddno+winehq(a)pm.me> --- (In reply to nerzhul from comment #56)
i say mark because the communication protocol is marked incompatible. And no using windows as a workaround is not a solution, it's just a workaround. I have develop skill, but not wine ones then i cannot troubleshoot it myself
No, you said retail is dead. Which is not true. It works. Your statement was just false. The BN launcher just doesn't work. Your statement has nothing to do with the "communication" protocol. It was and is because the game client had a recent new patch. Patch it, then it works again. How is that so hard to comprehend? Not sure why you insist on it being a "solution" nobody said that here. If you only wanna have solutions, should delete almost all comments here. ALl these "solutions" and PITA with changing Agent.exe and all that nonsense. These are just "workarounds" too. Nothing else. A solution is a proper patched BattleNet launcher that works without doing anything as an enduser. So I would suggest to choose your words more carefully... And nobody said you should "use" Windows... it takes 5 minutes to install a Windows VM and another 15 minutes to install BN + WoW. But I get it, you rather keep moaning about WoW retail being dead until "XYZ" and cry about it. Or waste time with some of the other weird "workarounds". Also, I never claimed that it was a solution, I literally said: "I write this, so people know, if they don't already know. At least it is a workaround to get the games running until the BN stuff is fixed somehow." So don't try to gaslight me here dude. -- 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=53697 --- Comment #58 from nerzhul <loic.blot(a)unix-experience.fr> --- let's be constructive here and battle. I don't know if there are wine developers in the thread who can ask us some debug things or not, we'll be glad to help. I think as only linux is impacted, blizzard won't release something for us, and the change they did on the launch may need a fix fixing things for other games -- 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=53697 piot(a)hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |piot(a)hotmail.com --- Comment #59 from piot(a)hotmail.com --- (In reply to nerzhul from comment #58)
let's be constructive here and battle. I don't know if there are wine developers in the thread who can ask us some debug things or not, we'll be glad to help. I think as only linux is impacted, blizzard won't release something for us, and the change they did on the launch may need a fix fixing things for other games
I agree with nerzhul, and I am happy to help if I can. I know nothing about how Wine works internally, but know my way around a debugger. -- 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=53697 --- Comment #60 from Mr_nUUb <josef.schabasser(a)gmx.at> --- My WoW:SL download was disrupted by a crash and Agent v8020 right now. Let's see what this brings. The new version didn't crash at least. -- 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=53697 --- Comment #61 from nerzhul <loic.blot(a)unix-experience.fr> --- it works again for me now. They should have fixed something server side, it seems i'm on Agent.8012 (not the 8020), the game repair works properly and the game update too -- 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=53697 --- Comment #62 from Mr_nUUb <josef.schabasser(a)gmx.at> --- I don't think a memory errpr on client side is caused by the server. Anyways, with Agent v8020 the following things work again: * continue download after agent crash * pause/unpause download * free space after update * update games * install games * uninstall games * scan and repair * add/remove language Tested with wine 7.16 (Manjaro) and lutris-fshack-7.2. No more errors, loops and crashdumps. -- 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=53697 --- Comment #63 from nerzhul <loic.blot(a)unix-experience.fr> --- same works on wine-staging 5.17 + latest proton GE -- 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=53697 --- Comment #64 from Yulian Kuncheff <yulian(a)kuncheff.com> --- Can also confirm the new 8020 agent works. Seems it was on Blizz side. Confirmed working in Bottles, Lutris, latest protonGE, lutris-fshack-7.2, on both Desktop and Steam Deck. Everything loads, patches, cleans up and logs me into the game. -- 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=53697 nerzhul <loic.blot(a)unix-experience.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|loic.blot(a)unix-experience.f | |r | -- 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=53697 Acridwax <acridwax(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acridwax(a)gmail.com --- Comment #65 from Acridwax <acridwax(a)gmail.com> --- Do we have any confirmation of Agent 8020 permitting the installation of the Battle.net launcher/client without hanging/crashing? -- 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=53697 --- Comment #66 from jhu543369(a)gmail.com --- (In reply to Acridwax from comment #65)
Do we have any confirmation of Agent 8020 permitting the installation of the Battle.net launcher/client without hanging/crashing?
I have tried the World of Warcraft installer on Lutris, and it installed with no issues. -- 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=53697 --- Comment #67 from piot(a)hotmail.com --- Confirmed to be working with agent 8020, without any changes to lutris/wine or my system. So it seems very likely that this was Blizzards fault. Manjaro 22.0.0, Kernel 5.15.65-1-MANJARO Lutris 7.2.2 (esync and fsync disabled) -- 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=53697 Lars Eriksen <fuddboyapa(a)netscape.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fuddboyapa(a)netscape.net --- Comment #68 from Lars Eriksen <fuddboyapa(a)netscape.net> --- With Agent 8020 it works on Ubuntu, Mageia and Steam Deck for me. Both with regular wine, wine staging and proton. Looks like Blizzard fixed the 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=53697 --- Comment #69 from Jens N <jens.n(a)godlike.biz> --- As someone playing mainly WoW-Classic the following works: - For Battle.net (updating/installing games) lutris-7.2.2 - esync and fsync disabled - still very (very) slow on Updates - crashes with WoW-Classic a lot on me, so no good choice for actually playing - For actually playin WoW-Classic lutris-GE-Proton7-16 - esync and fsync disabled - doesn't really work with Battle.net update/installs - runs WoW-Classic a lot better (just execute the WoWClassic.exe manually) It's a bit of a pain to switch between the versions, but at least it works. I'll probably create a seperate WoW-Classic entry withing Lutris to simplify things a bit. I just hope the issues can be ironed out soon for the GE-Releases. (or generally newer ones?) -- 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=53697 --- Comment #70 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to Jens N from comment #69)
As someone playing mainly WoW-Classic the following works: - For Battle.net (updating/installing games) lutris-7.2.2 - esync and fsync disabled - still very (very) slow on Updates - crashes with WoW-Classic a lot on me, so no good choice for actually playing - For actually playin WoW-Classic lutris-GE-Proton7-16 - esync and fsync disabled - doesn't really work with Battle.net update/installs - runs WoW-Classic a lot better (just execute the WoWClassic.exe manually)
It's a bit of a pain to switch between the versions, but at least it works. I'll probably create a seperate WoW-Classic entry withing Lutris to simplify things a bit.
I just hope the issues can be ironed out soon for the GE-Releases. (or generally newer ones?)
Hey Jens, just so you know the latest Agent update fixed all of that. It was an issue on Blizzard's side it seems.make sure you have Agent 8020. You might have to clear out your Battle.net folder and maybe Blizzard Entertainment folder in ProgramData. You can just use the latest GE or preferred wine version, and it will work like it always has. -- 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=53697 --- Comment #71 from Jens N <jens.n(a)godlike.biz> --- (In reply to Yulian Kuncheff from comment #70)
(In reply to Jens N from comment #69)
As someone playing mainly WoW-Classic the following works: - For Battle.net (updating/installing games) lutris-7.2.2 - esync and fsync disabled - still very (very) slow on Updates - crashes with WoW-Classic a lot on me, so no good choice for actually playing - For actually playin WoW-Classic lutris-GE-Proton7-16 - esync and fsync disabled - doesn't really work with Battle.net update/installs - runs WoW-Classic a lot better (just execute the WoWClassic.exe manually)
It's a bit of a pain to switch between the versions, but at least it works. I'll probably create a seperate WoW-Classic entry withing Lutris to simplify things a bit.
I just hope the issues can be ironed out soon for the GE-Releases. (or generally newer ones?)
Hey Jens, just so you know the latest Agent update fixed all of that. It was an issue on Blizzard's side it seems.make sure you have Agent 8020. You might have to clear out your Battle.net folder and maybe Blizzard Entertainment folder in ProgramData.
You can just use the latest GE or preferred wine version, and it will work like it always has.
Deleting the "Battle.net" folder in ProgramData did the trick, now it also works with the GE-Version, thx. -- 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=53697 --- Comment #72 from jhu543369(a)gmail.com --- esync/fsync disabled was for removing a variable from the testing during the issues with 8009/8012. Some people, including myself, have noticed that Battle.net won't start first time or will start and be unresponsive at the login screen. Sometimes wineserver will core dump, other times not. This is related to having esync and/or fsync enabled for Battle.net (kernel and wine version did not seem to matter). It does not affect any of the games. If it is an issue, point to the game directly and only use battle.net for updates. If your battle.net always starts 100% I would love to know your config so I can try it here. -- 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=53697 --- Comment #73 from Yulian Kuncheff <yulian(a)kuncheff.com> --- (In reply to jhu543369 from comment #72)
esync/fsync disabled was for removing a variable from the testing during the issues with 8009/8012. Some people, including myself, have noticed that Battle.net won't start first time or will start and be unresponsive at the login screen. Sometimes wineserver will core dump, other times not. This is related to having esync and/or fsync enabled for Battle.net (kernel and wine version did not seem to matter). It does not affect any of the games. If it is an issue, point to the game directly and only use battle.net for updates. If your battle.net always starts 100% I would love to know your config so I can try it here.
I mean, mine has always started 100% using Bottles, turning off the runtimes, and using FSYNC since you can't have ESync and FSync on at the same time in bottles. I also then on FSR on ultra quality. I think the rest of the settings are on defaults. Using latest versions of WineGE and everything else. -- 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=53697 Daniel <danieL(a)m2.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|danieL(a)m2.nz | -- 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=53697 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #73117|application/x-shellscript |text/plain mime type| | -- 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=53697 --- Comment #74 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Can we please have a normal output from the terminal? Nothing else is required unless asked for. -- 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=53697 --- Comment #75 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- This was apparently a bug on Blizzard's side: new versions of Agent.exe work without the issues described here. -- 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=53697 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Keywords| |Abandoned? --- Comment #76 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- That just means something changed, not that something was fixed. Is it possible to test the original file reported? -- 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