this post was submitted on 30 Apr 2025
45 points (94.1% liked)

Linux Gaming

18522 readers
183 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
[email protected]
45
Battle.net error BLZBNTBNA00000005 started today (feddit.org)
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
 

A little while ago, the Battle.net app started popping up a message: "Battle.net Agent Went to Sleep" with error code BLZBNTBNA00000005.

Dismissing the message box just results in it popping up again a few seconds later. Killing Battle.net causes the game I was playing to exit immediately, which is no fun when in the middle of a competitive match.

This seems to be a problem with a new version of Blizzard's Agent.exe, located in ProgramData/Battle.net/Agent/Agent.9124. It's not the first time they have pushed out a new version that breaks in Wine (GE-Proton9-27 in my case).

Workaround:

Block the new version from being used or refreshed. This only works if an older version (e.g. Agent.9098) is still installed. One probably is, assuming your Battle.net installation is more than a couple days old, because it keeps a prior version around when updating.

chmod a-rwx ProgramData/Battle.net/Agent/Agent.9124 # Remove all access permissions
sudo chattr +i ProgramData/Battle.net/Agent/Agent.9124 # Prevent Battle.net from restoring the permissions

Anyone else seeing this today?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 2 weeks ago

Yeah, my second time since switching to Linux in the last six months. I've been unable to come close to fixing it on my end. I just created another profile in Lutris and pointed at wow.exe until a better solution comes along. Last time, I tried all the fixes and the only thing that worked for me was a fresh install.