https://bugs.winehq.org/show_bug.cgi?id=48254
Bug ID: 48254 Summary: Steam + Skyrim Special Edition: unimplemented option 84 Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs@winehq.org Reporter: shumkar@shumkar.ru Distribution: ---
This missing option prevents Skyrim SSE from registering at api.bethesda.net.
fixme:winhttp:set_option unimplemented option 84
It looks like similar to https://bugs.winehq.org/show_bug.cgi?id=43676 but I believe it's another issue because that one must be fixed in 4.0-rc2.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #1 from Shumkar shumkar@shumkar.ru --- Created attachment 65916 --> https://bugs.winehq.org/attachment.cgi?id=65916 +winhttp,+seh,+tid trace
I'm attaching a +winhttp,+seh,+tid trace, as in [43676].
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #2 from Shumkar shumkar@shumkar.ru --- Created attachment 65917 --> https://bugs.winehq.org/attachment.cgi?id=65917 dll overrides
Also, I'm attaching a .reg file with the info about my dll overrides. I tried to change builtin winhttp and wininet to the native one, it did not help.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #3 from Shumkar shumkar@shumkar.ru --- My system has gnutls-3.6.7 with abi 32.
-------
I don't know if it's related:
(1)
while surfing in Steam tabs, I get numerous messages
WARNING:cert_verify_proc_win.cc(104)] Unknown error 161 mapped to net::ERR_FAILED and ERROR:ssl_client_socket_impl.cc(941)] handshake failed; returned -1, SSL error code 1, net_error -2
(2)
After exiting Skyrim, Steam shows Skyrim as "Running" and I can close only both pushing the button "Close now" at exiting Steam.
https://bugs.winehq.org/show_bug.cgi?id=48254
Shumkar shumkar@shumkar.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shumkar@shumkar.ru
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- 0144:trace:winhttp:WinHttpSetOption 0x1, 84, 0x7f86efc9fa80, 4 0144:trace:winhttp:addref_object 0x3a073ec0 -> refcount = 2 0144:trace:winhttp:grab_object handle 0x1 -> 0x3a073ec0 0144:trace:winhttp:session_set_option 0xa80 0144:trace:winhttp:release_object object 0x3a073ec0 refcount = 1
It sets the SECURE_PROTOCOLS option on the session handle, which succeeds.
0144:trace:winhttp:WinHttpConnect 0x1, L"api.bethesda.net", 443, 0 0144:trace:winhttp:addref_object 0x3a073ec0 -> refcount = 2 0144:trace:winhttp:grab_object handle 0x1 -> 0x3a073ec0 0144:trace:winhttp:addref_object 0x3a073ec0 -> refcount = 3 0144:trace:winhttp:addref_object 0x3a037e00 -> refcount = 2 0144:trace:winhttp:release_object object 0x3a037e00 refcount = 1 0144:trace:winhttp:release_object object 0x3a073ec0 refcount = 2 0144:trace:winhttp:WinHttpConnect returning 0x2 0144:trace:winhttp:WinHttpSetOption 0x2, 84, 0x7f86efc9fa80, 4 0144:trace:winhttp:addref_object 0x3a037e00 -> refcount = 2 0144:trace:winhttp:grab_object handle 0x2 -> 0x3a037e00 0144:fixme:winhttp:set_option unimplemented option 84
Here it tries to do the same with the connect handle but we don't support that.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #5 from Shumkar shumkar@shumkar.ru --- (In reply to Hans Leidekker from comment #4)
Thank you for the reply.
Here it tries to do the same with the connect handle but we don't support that.
Do you mean the flag WINHTTP_FLAG_SECURE for the WinHttpOpenRequest function?
https://docs.microsoft.com/en-us/windows/win32/api/winhttp/nf-winhttp-winhtt...
My knowledge does not allow me to understand the problem: is it some Windows specific, or is there some security concern?
Google does not help.
Could you explain that?
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #6 from Hans Leidekker hans@meelstraat.net --- (In reply to Shumkar from comment #5)
(In reply to Hans Leidekker from comment #4)
Here it tries to do the same with the connect handle but we don't support that.
Do you mean the flag WINHTTP_FLAG_SECURE for the WinHttpOpenRequest function?
I mean WINHTTP_OPTION_SECURE_PROTOCOLS. I wrote a test for this case and it fails on Windows with ERROR_WINHTTP_INCORRECT_HANDLE_TYPE. That means Wine behaves correctly here and the problem must be somewhere else.
https://bugs.winehq.org/show_bug.cgi?id=48254
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|winhttp |-unknown
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #7 from Shumkar shumkar@shumkar.ru --- (In reply to Hans Leidekker from comment #6)
I mean WINHTTP_OPTION_SECURE_PROTOCOLS. I wrote a test for this case and it fails on Windows with ERROR_WINHTTP_INCORRECT_HANDLE_TYPE. That means Wine behaves correctly here and the problem must be somewhere else.
Interesting.
I'll try to launch Skyrim SE in pure Windows and to test the same functionality if it is really broken.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #8 from Shumkar shumkar@shumkar.ru --- On Windows Skyrim SSE, after pushing all the same buttons, connects to Bethesda.
How can I debug it further? Which components are being used in this process? Steam, my system libs?
I would appreciate the help.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #9 from Shumkar shumkar@shumkar.ru --- Maybe, wrong vcrun version?
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #10 from Shumkar shumkar@shumkar.ru --- I played with different versions of vcrun / dotnet - nothing changes.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #11 from Shumkar shumkar@shumkar.ru --- The error appears after pushing button "Mods" or button "Creation Club". If the former could be replaced by Nexus mods, the latter could not be replaced by nothing because includes new items, abilities, and gameplay developed from Bethesda for credits.
So, it's important for playing Skyrim SE.
How to make this bug referenced to Skyrim SE App?
https://bugs.winehq.org/show_bug.cgi?id=48254
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Steam + Skyrim Special |Steam + Skyrim Special |Edition: unimplemented |Edition: fails to connect |option 84 |to api.bethesda.net CC| |o.dierick@piezo-forte.be
--- Comment #12 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to Shumkar from comment #11)
How to make this bug referenced to Skyrim SE App?
I submitted the bug to the AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34366
There may be a delay for the AppDB maintainers to review and accept it. When they do the game will appear in the list of apps affected by this bug.
(In reply to Shumkar from comment #8)
How can I debug it further? Which components are being used in this process? Steam, my system libs?
I would appreciate the help.
You could try with wine-devel/wine-staging 4.21. wine-stable 4.0.2 doesn't include the most recent development changes.
--- quote from terminal log --- 0299:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. --- end of quote ---
Probably not related, but you could fix this by installing the winbind package from your distribution (Remember to install the 32-bit package too on 64-bit system).
--- quote from terminal log --- 0131:trace:winhttp:netconn_verify_cert verifying L"api.bethesda.net" 0131:trace:winhttp:netconn_verify_cert returning 00002f7d 0131:warn:winhttp:netconn_secure_connect cert verify failed: 12157 0131:warn:winhttp:netconn_secure_connect Failed to initialize security context failed: 00000000 --- end of quote ---
It could be a cryptographic component issue.
May be a WINEDEBUG=warn+all trace could reveal something?
(In reply to Hans Leidekker from comment #6)
I mean WINHTTP_OPTION_SECURE_PROTOCOLS. I wrote a test for this case and it fails on Windows with ERROR_WINHTTP_INCORRECT_HANDLE_TYPE. That means Wine behaves correctly here and the problem must be somewhere else.
If unimplemented option 84 is not the problem, may be the summary should reflect that? I'll go ahead and change it. Please, correct me if my understanding is wrong.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #13 from Shumkar shumkar@shumkar.ru --- (In reply to Olivier F. R. Dierick from comment #12)
Hello Olivier,
(In reply to Shumkar from comment #8)
How can I debug it further? Which components are being used in this process? Steam, my system libs?
I would appreciate the help.
You could try with wine-devel/wine-staging 4.21. wine-stable 4.0.2 doesn't include the most recent development changes.
Yes! That fixed it. I installed Wine-vanilla 4.21 (decided to try vanilla before staging) and now Skyrim connects to Bethesda.
But the lines about "unimplemented option 84" still are in the log. So,..
If unimplemented option 84 is not the problem, may be the summary should reflect that? I'll go ahead and change it. Please, correct me if my understanding is wrong.
Yes, that's right.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #14 from Shumkar shumkar@shumkar.ru --- (In reply to Olivier F. R. Dierick from comment #12)
--- quote from terminal log --- 0299:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. --- end of quote ---
Probably not related, but you could fix this by installing the winbind package from your distribution (Remember to install the 32-bit package too on 64-bit system).
Thanks for the hint, I'll try to.
--- quote from terminal log --- 0131:trace:winhttp:netconn_verify_cert verifying L"api.bethesda.net" 0131:trace:winhttp:netconn_verify_cert returning 00002f7d 0131:warn:winhttp:netconn_secure_connect cert verify failed: 12157 0131:warn:winhttp:netconn_secure_connect Failed to initialize security context failed: 00000000 --- end of quote ---
It could be a cryptographic component issue.
May be a WINEDEBUG=warn+all trace could reveal something?
May be. But, considering that the connection was established, I'm not sure it's so important now.
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #15 from Shumkar shumkar@shumkar.ru --- (In reply to Olivier F. R. Dierick from comment #12)
I submitted the bug to the AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34366
There may be a delay for the AppDB maintainers to review and accept it. When they do the game will appear in the list of apps affected by this bug.
Thank you.
Anyway, I think it would be useful (not to launch Skyrim SE with wine of a lower version).
https://bugs.winehq.org/show_bug.cgi?id=48254
maniikarabera@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maniikarabera@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=48254
--- Comment #16 from Ken Sharp imwellcushtymelike@gmail.com --- Does this still occur with Wine 7.10 (or later)?
https://bugs.winehq.org/show_bug.cgi?id=48254
soredake broaden_acid002@simplelogin.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|broaden_acid002@simplelogin | |.com |