this post was submitted on 30 Apr 2025
47 points (100.0% liked)

Linux Gaming

18330 readers
278 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]
47
Battle.net error BLZBNTBNA00000005 started today (feddit.org)
submitted 6 days ago* (last edited 5 days 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?

top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 5 days ago

I haven't been playing Blizzard games for years and recently installed Battle-net again. It's nice to see their Agent updates still causing problems. /s

Thanks for the quick fix.

[–] [email protected] 4 points 5 days ago (2 children)

Found a fix here https://www.youtube.com/watch?v=bPNFa3GU7MY

[–] [email protected] 3 points 4 days ago

Thanks for posting. This fix worked for me.

[–] [email protected] 2 points 4 days ago

FY;DW - is there a summary made with letters on a a page?

[–] [email protected] 4 points 6 days ago* (last edited 6 days ago) (2 children)

Same problem. The only thing that fixes it is playing in Proton 10 but that comes with the side effect of locking Overwatch 2 to 60 FPS despite playing on a 165hz monitor.

Doesn't matter whether I change my settings to 720p all low or 1440p all ultra, I'm still locked to 60 fps.

Edit: 7600X, 32GB RAM, 6700XT and 2TB Western Digital Black SSD so it isn't my specs holding me back. Was working fine just a few days ago but now I can't play OW2 and Final Fantasy 16 since the last Proton update.

[–] [email protected] 2 points 4 days ago

+1 for Proton 10 fixing the Battle.net agent issue. Was only playing Starcraft, and didn't look at the fps so no idea if there was any difference.

[–] [email protected] 2 points 6 days ago (1 children)

Do you happen to know what part of Proton 10 is limiting you to 60 FPS? It might be configurable.

[–] [email protected] 1 points 5 days ago

I have no clue at all. All I know is I could get 165 FPS in OW2 when I was running under GE Proton 27.

[–] [email protected] 4 points 6 days ago (1 children)

If you say that out loud you'll skip right to the boss fight in diabolo 2

[–] [email protected] 4 points 6 days ago

xyzzy ;)

[–] [email protected] 3 points 6 days 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.

[–] [email protected] 2 points 6 days ago

Ah nuts. Just as I switched back to Linux on my new rig. ( Dabbled one win11 for a month, but what a forking shirtshow )