[Bug 45814] New: Blizzard agent went to sleep. Attempting to wake it up...
https://bugs.winehq.org/show_bug.cgi?id=45814 Bug ID: 45814 Summary: Blizzard agent went to sleep. Attempting to wake it up... Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hewanci(a)gmail.com Distribution: --- Every now and then randomly, and also after every time the Blizzard app updates this issue occurs. After launching, the Blizzard app is stuck indefinitely with the message: "Blizzard agent went to sleep. Attempting to wake it up..." The only way I found to fix it is by closing the app, deleting the folder 'drive_c/Program Data/Battle.net' and restarting. This however removes all installed games from the app, and they will need to be re-added using Settings > Game Install/Update > Scan for games, which may take anywhere between 1 second to 15 minutes. -- 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=45814 Maciej Stanczew <maciej.stanczew+b(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b(a)gmail.com --- Comment #1 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- This is the same issue as the one where Battle.net is unable to install/update games; it's described in AppDB, under "Cannot install or update games" note. (There was no bug submitted until now, so this might as well be the main bug for this whole problem.)
The only way I found to fix it is by closing the app, deleting the folder 'drive_c/Program Data/Battle.net' and restarting. It's enough to delete a single file, 'drive_c/ProgramData/Battle.net/Agent/product.db' – but it will still cause the need to rescan games.
Also, a while back (when this problem started appearing) there were rumors that it was also happening for Windows users – can anyone confirm/deny this? -- 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=45814 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- There is a lot of people complaining on the blizzard forums [1], so yes, this happens in Windows too, and the suggested workaround for Windows users is to kill every blizzard processes (agent.exe *, battle.net *, games), and then delete C:\ProgramData\Battle.net and, then re-detect all games. The link in the error message itself also suggest that it occurs in Windows and hints at deleting the aforementioned directory. Seems to be an upstream bug but it may get triggered by Wine for specific reasons, so I can't confirm whether it's an upstream bug or not. [1] Search "Blizzard agent went to sleep" in your favorite search engine. -- 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=45814 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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=45814 --- Comment #3 from Storm Engineer <hewanci(a)gmail.com> --- (In reply to Maciej Stanczew from comment #1)
It's enough to delete a single file, 'drive_c/ProgramData/Battle.net/Agent/product.db'
Indeed, that is the offender. So it seems that what triggers the problem is if there is an update for anything - but that the Battle net app itself or any of the games, before the App starts. My theory is that the reason I had it happen after updating battle net was that the update for it arrived while it was already running, it updated fine, but game updates might have only been triggered once the App was updated, which is why after restarting the condition for an update being available before the App starts was met. I keep an eye on it. The last two times it happened I had an App update and a game update ready respectively, before the App launched. -- 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=45814 --- Comment #4 from Storm Engineer <hewanci(a)gmail.com> --- (In reply to Storm Engineer from comment #3)
if there is an update for anything - but that the Battle net app itself or any of the games I meant: "if there is an update for anything, either the Battle net app itself or any of the 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=45814 Luke Bratch <luke(a)bratch.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luke(a)bratch.co.uk -- 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=45814 --- Comment #5 from Storm Engineer <hewanci(a)gmail.com> --- This doesn't seem to happen for me anymore. -- 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=45814 --- Comment #6 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- It still does for me -- in fact it happened just now. I think it's related to the number of games installed. More games installed -> more updates to check -> higher probability for product.db to get corrupted. In one of my systems I have 5 games installed and in the other I have 2, and I feel the first one gets broken quite more often. -- 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=45814 --- Comment #7 from Storm Engineer <hewanci(a)gmail.com> --- (In reply to Maciej Stanczew from comment #6)
It still does for me -- in fact it happened just now.
I think it's related to the number of games installed. More games installed -> more updates to check -> higher probability for product.db to get corrupted. In one of my systems I have 5 games installed and in the other I have 2, and I feel the first one gets broken quite more often.
And I just got it again as well... :( I have 7 games installed, and I was consistently getting it every time for a long time, until recently I didn't for just a few times, and now again. So your theory may be correct about the number of 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=45814 aaahaaap(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaahaaap(a)gmail.com --- Comment #8 from aaahaaap(a)gmail.com --- Can confirm. I only have a single game installed (HotS) and I'm getting this as well. Have been getting it for quiet a long time, at least since the start of August, maybe a bit before that. It's consistently getting into this broken state on every update of 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=45814 --- Comment #9 from Storm Engineer <hewanci(a)gmail.com> --- I used to get this consistently with every single update. Now I only get it maybe one time out of 10, but it still does happen every now and then. -- 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=45814 --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- I had two updates the last week and the issue did not happen. I can't tell if the issue disappeared completely, but at least it doesn't happen every time like it used to. -- 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=45814 --- Comment #11 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- I too didn't see this issue since about 1-2 months ago. Also, the Lutris Wiki[1] suggests "Use wine version 3.20 or newer" regarding this problem -- so maybe there really was a change that fixed it (or maybe it's just a coincidence and Battle.net fixed itself). [1] https://github.com/lutris/lutris/wiki/Game:-Blizzard-App -- 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=45814 --- Comment #12 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- I had to update both battle.net and World of Warcraft today. I did not get the issue. -- 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=45814 --- Comment #13 from Storm Engineer <hewanci(a)gmail.com> --- To join the comments above, I had Battle.net and Overwatch update today after not launching them for months, and the issue was not present. -- 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=45814 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED --- Comment #14 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- I think it is safe to assume the issue is resolved. It may have been caused by the mixed plain/staging ACLs issue mentioned in bug 46218. The ACL issue would make cache files inaccessible, resulting in truncated files and a game error. I guess it's what happened to the product.db file this bug is about. For me, that ACL issue eventually got fixed by a game update and so maybe this bug was fixed by a Blizzard agent update. I will resolve as ABANDONED because we may never know the actual cause. If someone is still affected or find interest in analyzing this further, feel free to reopen. -- 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=45814 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #15 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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)
-
wine-bugs＠winehq.org