I missed that part!
I tried that as well, I guess it’s just waiting until some battlenet update fixes it.
Looks like happened before and was fixed by Blizzard.
I think this is a different issue. The original reddit thread (now down, but archive link) talks about a guy having problems with Classic WoW specifically (though it seems like it affected more games). It seems the games themselves were in update loops and couldn’t launch.
Any updates and fix on these guys? I am using linux mint on a dell inspiron 7559 laptop. this happen just a couple of weeks ago where battle.net just hangs when you update and will not restart itself. but if you restart manually on lutris it will run but still a notification to update. any help will be appreciated…
I made it worse.
I deleted the old Battle.net installation in order to try a fresh install.
The fresh install crashes at the update agent in the installation process.
I’m getting the same.
wine client error:68c: write: Bad file descriptor
wine client error:280: write: Bad file descriptor
If you are having this problem, then temporary workaround is this:
- Open bnet client via lutris, and launch your game, in my case SC2
- Once you are logged into the game, exit the battle.net client (close it) - if you don’t, this is what keeps spawning new agent.exe to continue the background download of beta bnet client.
- Open htop or any process manager
- Kill agent.exe
- It will immediately stop the background download for bnet beta client
If I should get a dc during game (bad internet connection) then I just log in with the bnet password (in game login screen I mean) 
that works for me. It’s been 1-2 months, and again the issue is not yet solved by Blizz or the Lutris community, we need a fix.
I don’t quite get what is this the work around for?
+1, sounds like xve is describing a separate issue
Ok sorry for not posting here - I posted the solution on the Blizzard forums. The Update and Restart in the BNet launcher is most likely an issue with the version of wine GE being used. To check, go to settings on the launcher and confirm that the current launcher version is 2.22.0.14235. If it is, then you are running the most recent non-beta version of the battle.net launcher. To see if you really need to update, switch your wine version on the runner options tab to lutris ge 7.2-2 or a wine-staging 8.x (do not try to launch a game, just for checking bnet launcher) and see if there is an update to be applied. Should you not have the correct launcher version and update and restart leaves you in a “crashed” state, look in activity monitor for the CrBrowserMain process and kill this. Alternately you can use stop in lutris, either way check to see if it is the newer build number or if it failed to install. If you have the newer build, switch back to your normal wine version on runner options tab to play games and simply use this process every couple of Tuesday’s to see if a bnet launcher update really needs to be applied.
In the words of the Bard, this is much ado about nothing…
Thanks for sharing this. I tried this as mentioned here also. When I then launch battlenet a second time with wine-8.6-staging-tkg the update notification is gone. When I then switch back to the the default runner lutris-GE-Proton8-9 I get the update notification again. So it’s definitely the Lutris-GE version having a problem.
Here’s how to get it to update.
- Start Battle.Net from Lutris as you normally would.
- Click the Battle.net icon in the upper left hand corner and select the update now and restart (I forget the exact verbiage, because I just did it and it’s no longer there.
- Open a shell
ps -auxw | grep Battle
You should see something like this:
sinack 1137119 14.3 0.2 1895472 301852 ? Ssl 16:56 0:25 C:\Program Files (x86)\Battle . net\Battle . net.exe --from-launcher
sinack 1137667 1.8 0.1 1821028 208840 ? Sl 16:57 0:02 C:\Program Files (x86)\Battle . net\Battle . net.exe --updatepid=280
sinack 1138636 0.0 0.0 9208 2372 pts/14 S+ 16:59 0:00 grep --color=auto Battle
You specifically want the one that says C:\Program Files (x86)\Battle . net\Battle . net.exe --from-launcher, so in my example, it is PID 1137119
Enter this command, replacing 1137119 with your PID:
kill -9 1137119
Wait a few seconds and Battle_net will automatically relaunch and will be updated.
I hope this helps somebody.
Note: I had to put spaces in Battle . net, because the anti-spam feature in the forum thinks I’m spamming.
2 Likes
Hey sinack82, I followed your guide. Unfortunately it still shows a available update in the client. Not working for me 
Sinack’s method does work, it is the same as locating CrBrowserMain in Activity Monitor and killing that. What you need to check per my post earlier is the Battle.net launcher version you are running. If it is 2.22.0.14235 either the update worked or you had the most recent version anyway. As I noted, the Update and Restart always being present is a “bug” with Wine GE versions, you can switch to wine-staging or lutris-7.2-2 to check (just don’t run any games)
I’ve tried Sinack’s method twice and it doesn’t work for me. And just to be clear.
1 press “Restart and update” ← this is what it says
2 find the process precisely as described, i.e. the one associated with “–from-launcher”
3 kill 9 [process number]
4 battle.net relaunches and is NOT updated.
What I’m fuzzy on is which runner config should be in effect when you do it.
However i did try lutris-7.2-2-x86_64, and when i do that battle . net never comes up even though it’s running in the background, so that seems bad.
This would be a complete don’t care except that braindead Battle . net keeps downloading a cache file, something named
temp_2CD69E80929FBB0A5617FCD87588A4A6.8320
into
drive_c/ProgramData/Battle.net/Agent
over and over again.
My battle . net version IS the latest, i.e. 2.22.0.14235
This was all working flawlessly a week ago. now I have this annoying update bug and D2R won’t start because “it can’t initialize hardware”. Thanks Blizzard.
update:
I starting trying different runners (right click → configure → Runner Options tab)
as i was saying lutris-7.2-2-x86_64 does not seem to work at all
“WineHQ Staging (8.12 (Staging))” DOES work. The update marker is gone AND diablo3 runs correctly.
diablo2 resurrected is still broken, oh well…
edit: well it doesn’t seem to matter what runner i use, WineHQ staging or Proton, battle . net always crashes when it launches the game now. D3 (and D2R ! ) still runs though…
As I mentioned in my original post, don’t try and run a game with the wine-staging - as you have seen, most no longer work. Check that you have vulkan-tools package installed and then check on the System Options tab with the Show advanced options enabled in the multi gpu section that your Vulkan ICD loader is set to something that matches your graphics card and is not set to default, auto or unspecified.
And that folder you note is downloaded over and over… it is the same on Win installs… It has logs, a cache file and an agent.exe file.
I tried to do the same thing, but unfortunately, it doesn’t work.
lutris-GE-Proton8-12 Fixed the issue for me aswell. After I pressed the update and restart Button Battle net came back up an did not show the message anymore.
1 Like
Thanks for sharing this didn’t know there was a new release out for lutris-GE-Proton. Solved it for me as well.