[Bug 44823] New: Steam doesn' t close on exit. Will continue running in background.
https://bugs.winehq.org/show_bug.cgi?id=44823 Bug ID: 44823 Summary: Steam doesn't close on exit. Will continue running in background. Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Created attachment 60857 --> https://bugs.winehq.org/attachment.cgi?id=60857 Steam system information and version Running the latest Steam client, I find that Steam doesn't actually close entirely after I exit normally with Steam>Exit. I have to open System Monitor and kill all steam and wine related processes. I can't open steam again until I do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in the background until I do so. -- 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=44823 --- Comment #1 from Vlad <vblanton(a)gmail.com> --- Oddly, Steam exits fine if run from a commandline directly. This seems to only happen from the .desktop icon launcher for Steam. -- 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=44823 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #2 from Fabian Maurer <dark.shadow4(a)web.de> --- Fresh WINEPREFIX doesn't help? Are you using vanilla wine or PlayOnLinux or something similar? What's inside the .desktop file? -- 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=44823 --- Comment #3 from Vlad <vblanton(a)gmail.com> --- This issue is resolved, running Wine Staging 3.6. Given about 10 seconds after quitting and window closes, steam and all related processes stop. I do not know whether it works fine now on vanilla wine. -- 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=44823 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=44823 Fab <netbox253(a)free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netbox253(a)free.fr --- Comment #4 from Fab <netbox253(a)free.fr> --- Just to say that I'm having the exact same problem. I upgraded to wine-staging 3.7, and the problem is still here. The WINEPREFIX is very old, I did not tried to refresh it, I did not find time yet, but I will report here if find the time to do it. -- 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=44823 --- Comment #5 from Fab <netbox253(a)free.fr> --- Ok, I created a new WINEPREFIX with wine-staging-3.7. Reinstalled steam from scratch. For now the problem seems to be gone. -- 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=44823 --- Comment #6 from Fab <netbox253(a)free.fr> --- ... and after some days/weeks of usage on this new WINEPREFIX, this behavior cames back. -- 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=44823 --- Comment #7 from Fab <netbox253(a)free.fr> --- Still same behavior with wine-staging 3.13. When this happens, opening a terminal and running the following command will make steam exit and all wine processes shutdown :
$ killall Steam.exe
-- 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=44823 --- Comment #8 from Vlad <vblanton(a)gmail.com> --- a recent steam client update may have fixed this issue inadvertently? "Linux:... Fixed an issue where the system might become temporarily unresponsive after exiting the client due to events accruing in the window system" (https://store.steampowered.com/news/42269/) I don't have steam installed on wine anymore, cannot test. I don't think I had this issue anymore in any case. -- 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=44823 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.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=44823 --- Comment #9 from Fab <netbox253(a)free.fr> --- (In reply to Vlad from comment #8)
a recent steam client update may have fixed this issue inadvertently?
"Linux:... Fixed an issue where the system might become temporarily unresponsive after exiting the client due to events accruing in the window system" (https://store.steampowered.com/news/42269/)
That part is for the Linux version of steam, not the Windows version we are talking about here. I also noticed another wrong behavior related to this problem : when launching steam, after a few seconds whithout doing anything, the cpu usage is increasing as if it was entering into some infinite loop or something :
$ ps -p 5413 -o %cpu,%mem,cmd %CPU %MEM CMD 65.7 2.0 Steam.exe
-- 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=44823 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Keywords| |Abandoned?, download --- Comment #10 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Please retry in Wine 7.9 (or later). -- 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=44823 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Probably a dupe, neither gave us logs. *** This bug has been marked as a duplicate of bug 44529 *** -- 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=44823 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #12 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Close duplicate. -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla