Running Battle.net on Linux can feel like a victory—until it suddenly stops working. Many users report it runs smoothly for days via Wine, Lutris, or Bottles… and then one update later, you’re hit with errors like “Agent updater falling asleep” or failed startups for the web.
So what’s going on?
Possible reasons:
– Silent background updates from Blizzard
– Wine or Proton version incompatibility
– OS-level changes (kernel updates, drivers, etc.)
– File path conflicts after reinstallation attempts
What to try:
– Downgrade Wine/Proton version
– Reinstall via Lutris with a fresh config
– Check logs in terminal for exact fail point
– Use a backup of the last working setup if available
For what it’s worth we know what happened, just not why it’s an issue.
This starts when Agent updates to 9124.
Hi traveler!
I recently switched to linux and my battle.net is working however I installed it and launch it trough steam! Just download the battle.net launcher from blizzard and add it trough steam and enable linux during compatibility.
Cheers,
Your friendly Tauren
for me, the problem was solved in this way - install battle.net through wine, then go to steam in the library to add a game , specify the path to battle net, specify in the compatibility settings to force the use of proton 10.1 beta
Been doing that for years, and now things are broken as of two days ago. Proton 10.0 works, but it makes WoW hide my mouse cursor and renders the game unplayable at this time.
1 Like
That worked for me, thx a lot.
It seems we need to wait proton 10 for bottles in my case to work.
Can you please go to the 9124 agent and open up the logs? I’m curious if linux users have a similar issue to Windows and you’re getting a 404 error when your agent tries to phone home.