Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Battle.net refuses to work correctly

Open
#416 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
arch-linux
Domain
desktop

Research direction

Start by reproducing the Battle.net setup on Arch Linux using the YAML script and manual setup described in the issue, then compare the behavior with adding the installer to Steam using Proton Hotfix. Done means identifying the configuration difference that prevents the update agent from working or causes freezes, with a reproducible finding for the Bottles programs setup.

Written by the indexing model from the issue text.

Description

Battle.net does not want to work. I've tried using both the yaml script and manually running the setup. The installation works fine, but the actual app gives varying results depending on the runner:

  • soda or wine-ge: Gives the error "Update agent is asleep... trying to wake it up" even though Agent.exe is already running it keeps spawning new Agent.exe processes and the error never goes away - meaning I can't install or run any games
  • Anything else: freezes after a couple of seconds forcing me to manually terminate the process

The interesting thing here is adding the installer to Steam as a non-steam game and using Proton Hotfix makes it work with no issues, I've tried running Warcraft III Reforged this way and it works flawlessly.

So the question here is: what is Steam doing correctly that Bottles isn't?

My setup:
OS: Arch Linux 6.15.6-arch1-1 (64-bit)
Desktop: Plasma 6.4.3 on Wayland
GPU: NVIDIA GeForce RTX 3070
GPU driver: 4.6.0 NVIDIA 575.64.03

Dominant language
No language data
Stars
111
Forks
93
Avg merge
1d 1h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bottlesdevs/programs

All issues in bottlesdevs/programs

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.