https://bugs.winehq.org/show_bug.cgi?id=44024
--- Comment #9 from Sveinar Søpler cybermax@dexter.no --- Used 3.0 GIT, and i installed then logged in, as the bugged interface allowed... The first time.
Then second time i tried, the bugged interface would not accept keystrokes in the authenticator field. I may slightly remember something like that from "back when" i installed battle.net in the first place, but not sure what i did to fix that.
However, closing that bugged window DID close it, and closed Agent.exe after some seconds as you said.
The fun part was that going back to my old prefix with wine-3.0, it did the same!
Going back to wine-staging-2.21 and it did not quit.
With wine-3.0 the process xx\Battle.net\Battle.net.exe --from-launcher closes together with the "Battle.net Helper.exe" process, and after a while the "Agent.exe" process closes. With wine-staging-2.21 only the "Battle.net Helper.exe" process closes, but the "Battle.net.exe --from-launcher" process + Agent.exe keeps open and needs to be killed.
Kinda similar to the "if you set winxp os the browser works in battle net even after you switch back to win7+ after" bug that USED to work in previous battle.net versions. A recent update to battle net only show two white squares in the left corner, and nothing to click in the black window at all tho..
If blizzard has switched to some DX11 overlay that is somewhat similar to the "Unigine Superposition" window bug if you start that with DX11 tho. Maybe DX11 2D text or something? + general problems with Gecko and flash/animations?
Cant play World of Warcraft with wine-3.0 anyway, but i guess a improvement that the app actually closes when you close it with wine-3.0 :)
Just to sum this up (for ME atleast): 1: Make new prefix w/wine-3.0. Battle.net closes as it is supposed to. 2: After running #1 with wine-3.0, my original prefix does the same. 3: Switching to wine-staging "breaks" this function. 4: Just switching to wine-3.0 in my old prefix had the same problems as with 2.x.