[Bug 40022] New: Steam.exe fails on wine-staging 1.9.1, but working on the latest wine (official) at Git HEAD
https://bugs.winehq.org/show_bug.cgi?id=40022 Bug ID: 40022 Summary: Steam.exe fails on wine-staging 1.9.1, but working on the latest wine (official) at Git HEAD Product: Wine-staging Version: 1.9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: roman(a)hargrave.info CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- `wine Steam.exe` returns exit status 1 on wine-staging 1.9.1 from the `testing` (`stretch`) debian repository. Running Steam.exe two `ERROR` level items are logged by Steam * WSALookupServiceBegin failed with: 8 * DNS Registry watch failed to start Please note that I am using the 32-Bit version of wine-staging and NOT the 64-Bit version. Steps to reproduce: * Using debian testing/stretch install wine-staging * Create and boot a new prefix for Steam * Install Steam * Attempt to run Steam I will submit logs when I am in front of my computer. -- 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=40022 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- Steam works fine for me with Wine Staging 1.9.1. Please provide full log of the terminal output, including description where you got the Wine version from and how you set up the prefix. Please note that the package "wine-staging" installs to /opt/wine-staging/bin/wine on some distributions. If you compiled Wine Staging yourself, make sure that all necessary build dependencies are found during the ./configure step. -- 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=40022 --- Comment #2 from roman(a)hargrave.info <roman(a)hargrave.info> --- Created attachment 53471 --> https://bugs.winehq.org/attachment.cgi?id=53471 wine-staging output when attempting to run 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=40022 --- Comment #3 from roman(a)hargrave.info <roman(a)hargrave.info> --- (In reply to Sebastian Lackner from comment #1)
Steam works fine for me with Wine Staging 1.9.1. Please provide full log of the terminal output, including description where you got the Wine version from and how you set up the prefix. Please note that the package "wine-staging" installs to /opt/wine-staging/bin/wine on some distributions. If you compiled Wine Staging yourself, make sure that all necessary build dependencies are found during the ./configure step.
Yes, I am running the correct WINE. I have tested this with three versions: * wine-1.8 (prebuilt from debian repo's): steam works * wine-1.9.1 (git 8676f7b with ntdll patch for chromium sandbox): steam & steam store works * wine-1.9.1 (staging): steam does not work Where did you get your copy of wine-staging, and what distro are you using? I have provided the output as an attachment. -- 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=40022 --- Comment #4 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to roman(a)hargrave.info from comment #2)
Created attachment 53471 [details] wine-staging output when attempting to run steam
According to the log you have enabled the experimental GTK3 theming support (in the winecfg Staging tab). Could you please test if Steam works for you after disabling this feature? I'm currently testing with the Archlinux wine-staging packages. -- 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=40022 --- Comment #5 from roman(a)hargrave.info <roman(a)hargrave.info> --- Created attachment 53472 --> https://bugs.winehq.org/attachment.cgi?id=53472 result when attempting to run steam via wine-staging with no staging features enabled in winecfg -- 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=40022 --- Comment #6 from roman(a)hargrave.info <roman(a)hargrave.info> --- (In reply to Sebastian Lackner from comment #4)
(In reply to roman(a)hargrave.info from comment #2)
Created attachment 53471 [details] wine-staging output when attempting to run steam
According to the log you have enabled the experimental GTK3 theming support (in the winecfg Staging tab). Could you please test if Steam works for you after disabling this feature? I'm currently testing with the Archlinux wine-staging packages.
Uploaded as attachment 53472 -- 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=40022 --- Comment #7 from roman(a)hargrave.info <roman(a)hargrave.info> --- It looks like this has started happening with all other WINE installations on my system. This is quite likely a result of something that was done by the wine-staging installation, likely a library dep. -- 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=40022 --- Comment #8 from roman(a)hargrave.info <roman(a)hargrave.info> --- This would be the case. After removing wine-staging and cleaning up auto-removable packages, the problem has gone away. I imagine that this is due to wine-staging depending on an apparently optional library that causes issues. -- 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=40022 --- Comment #9 from Sebastian Lackner <sebastian(a)fds-team.de> --- Installing dependencies should not cause issues with Steam. Please provide more details which packages cause such an issue for you. When switching between different versions of Wine, make sure that the wineserver is terminated properly (wineserver -k) inbetween. -- 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=40022 --- Comment #10 from Michael Müller <michael(a)fds-team.de> --- I just tested the same situation (debian stretch - fully updated, wine staging 1.9.1 package from winehq) and can't reproduce the problem. The problem seems to be specific to the system of the bug author, maybe some other third party packages? What is the output of "/opt/wine-staging/bin/wine --check-libs"? -- 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=40022 Michael Müller <michael(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- 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=40022 roman(a)hargrave.info <roman(a)hargrave.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED Resolution|--- |ABANDONED --- Comment #11 from roman(a)hargrave.info <roman(a)hargrave.info> --- I am abandoning this issue, as the issue has returned, and I have determined it to be an issue with a steam update depending on an unimplemented WinSock2 function. As such, I feel that a new issue should be opened. -- 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=40022 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED Resolution|ABANDONED |INVALID --- Comment #12 from Sebastian Lackner <sebastian(a)fds-team.de> --- Bug status INVALID makes more sense when the original error description turns out to be wrong. -- 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=40022 --- Comment #13 from roman(a)hargrave.info <roman(a)hargrave.info> --- (In reply to Sebastian Lackner from comment #12)
Bug status INVALID makes more sense when the original error description turns out to be wrong.
The error message was correct. WSALookupServiceBegin does appear to be causing the problem. -- 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=40022 --- Comment #14 from Austin English <austinenglish(a)gmail.com> --- (In reply to roman(a)hargrave.info from comment #13)
(In reply to Sebastian Lackner from comment #12)
Bug status INVALID makes more sense when the original error description turns out to be wrong.
The error message was correct. WSALookupServiceBegin does appear to be causing the problem.
How did you determine that? -- 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=40022 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #15 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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