[Bug 44024] New: Battle.net leaves processes open after exiting.
https://bugs.winehq.org/show_bug.cgi?id=44024 Bug ID: 44024 Summary: Battle.net leaves processes open after exiting. Product: Wine-staging Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: peter.g.anderson(a)live.co.uk CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When exiting the Blizzard App / Battle.net client, the application window closes, but looking in system monitor shows that there is a Battle.net.exe and an Agent.exe still running, as well as the associated wine processes such as wineserver etc. These persist until Battle.net.exe and Agent.exe are killed manually, in that order. If the application was launched in a virtual desktop, the desktop will remain open and visible, but unusable. This bug would perhaps affect plain wine as well as staging, but there are other issues that prevent plain wine from running Battle.net. Unable to find any workaround for this, except for manually killing the processes in task manager. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Dox <IngeniousDox(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |IngeniousDox(a)gmail.com --- Comment #1 from Dox <IngeniousDox(a)gmail.com> --- What is worse, if you do not kill them manually, you can actually end up with mouse issues in the blizzard games. Symptoms observed: 1) Slow turning in WoW, unable to click UI elements. 2) Jittery mouse in Overwatch 3) Unable to click cards in Hearthstone If you encounter these issues, they get resolved immediately after you "killall Battle.net.exe Agent.exe" in a terminal. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #2 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to Dox from comment #1)
What is worse, if you do not kill them manually, you can actually end up with mouse issues in the blizzard games.
Symptoms observed:
1) Slow turning in WoW, unable to click UI elements. 2) Jittery mouse in Overwatch 3) Unable to click cards in Hearthstone
If you encounter these issues, they get resolved immediately after you "killall Battle.net.exe Agent.exe" in a terminal.
Your post gave me an idea. I've made a hotkey binding for my desktop to 'killall Battle.net.exe Agent.exe'. It saves calling up task manager or a terminal after using the Blizzard App. Cheers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #3 from Dox <IngeniousDox(a)gmail.com> --- Just for the record, I don't see this bug attached to Blizzard Battle.net App page. It it still happening. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Luke Bratch <luke(a)bratch.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luke(a)bratch.co.uk -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Sveinar Søpler <cybermax(a)dexter.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #4 from Sveinar Søpler <cybermax(a)dexter.no> --- Change this to CONFIRMED.. cos it is still happening. Bug reporting on WineHQ is dead slow. "Status UNCONFIRMED" since november.. What does it take? That Mr. Julliard himself installs battle.net to try? :) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC| |z.figura12(a)gmail.com --- Comment #5 from Zebediah Figura <z.figura12(a)gmail.com> --- I can't reproduce. Using wine 3.0 in a clean wineprefix, I consistently see Battle.net.exe exit cleanly, and then Agent.exe runs for another few seconds before also exiting cleanly. I get this same result regardless of whether I use corefonts (as the AppDB page dictates). Please retest using current wine in a clean prefix. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #6 from Sveinar Søpler <cybermax(a)dexter.no> --- Before i make a clean prefix, just going to check that you are using a 64-bit prefix and NOT a 32-bit? :) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #7 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Sveinar Søpler from comment #6)
Before i make a clean prefix, just going to check that you are using a 64-bit prefix and NOT a 32-bit? :)
Yes, this is with a 64-bit prefix. The installer and application are 32-bit; I did not see any 64-bit download on the website. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #8 from Dox <IngeniousDox(a)gmail.com> --- This is a bug with Wine Staging since 2.18 where they implemented: Support for ECDSA certificate chains. This was so Battle.net can be run in Win7 / Win10 mode etc. Before that you could only use it in WinXP mode. WinXP mode doesn't have the issue. But Blizzard is erquiring you to have Win7 or higher set to install games now. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #9 from Sveinar Søpler <cybermax(a)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. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #10 from Dox <IngeniousDox(a)gmail.com> --- Going to say again: This is a bug with a patch in Wine-Staging. This patch hasn't made it into mainline yet. You won't reproduce this with Wine 3.0. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Battle.net leaves processes |Battle.net leaves processes |open after exiting. |open after exiting | |(staging-only) Status|NEEDINFO |NEW CC|z.figura12(a)gmail.com | --- Comment #11 from Zebediah Figura <z.figura12(a)gmail.com> --- Clarifying the topic and setting status to confirmed. Apologies for not reading the fields (which, to be fair, few submitters do either...) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #12 from Dox <IngeniousDox(a)gmail.com> --- Well, it is a shame this patch (and the ntdll patches that allows you to log Blizzard games) didn't make it into Wine 3.0. But from what I can gather a lot of patches are getting stranded in Staging atm. Lets hope you folks have a chance to get some of them into the coming releases of Wine. So I can stop telling people that they need Wine Staging 2.21 instead of Wine 3.0 after they have upgraded thinking that Wine 3.0 > Staging 2.21. Which is probably true aswell, but that doesn't help if your game doesn't start. ^^ Dox -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Battle.net leaves processes |Battle.net application does |open after exiting |not exit cleanly when |(staging-only) |version >= Win7 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Maciej Stanczew <maciej.stanczew+b(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b(a)gmail.com --- Comment #13 from Maciej Stanczew <maciej.stanczew+b(a)gmail.com> --- I can reproduce this on Staging 2.21, but with Staging 3.3 (and earlier, from the start of new repo) I don't encounter the problem anymore – all Battle.net processes exit cleanly. Can anyone confirm this? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 --- Comment #14 from PeterG <peter.g.anderson(a)live.co.uk> --- Confirming that this issue is no longer pesent in 3.4 staging. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 PeterG <peter.g.anderson(a)live.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from PeterG <peter.g.anderson(a)live.co.uk> --- Marking this as RESOLVED / FIXED as the issue is gone with the current (3.4) wine-staging. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44024 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed Staging 3.14 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org