https://bugs.winehq.org/show_bug.cgi?id=42316
Bug ID: 42316 Summary: Cannot play multiplayer in Gwent Product: Wine-staging Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: stas5978@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
When tried to start Multiplayer's "Casual Math" and wait about 5 sec you will get wine fixme:
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported
https://bugs.winehq.org/show_bug.cgi?id=42316
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #1 from winetest@luukku.com --- Does overriding bcryt via winecfg as native workaround the issue?
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #2 from Stanislav Zhukov stas5978@gmail.com --- (In reply to winetest from comment #1)
Does overriding bcryt via winecfg as native workaround the issue?
After trying to override bcrypt.dll to native, game obtained a continuous login state.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #3 from winetest@luukku.com --- You need to attach the console output. Without owning the game its impossible to know whats going on.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #4 from Stanislav Zhukov stas5978@gmail.com --- Created attachment 57084 --> https://bugs.winehq.org/attachment.cgi?id=57084 Wine 2.0.0-staging log
https://bugs.winehq.org/show_bug.cgi?id=42316
Stanislav Zhukov stas5978@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|2.0-rc6 |2.0
https://bugs.winehq.org/show_bug.cgi?id=42316
CharlyDelta waste@charlydelta.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |waste@charlydelta.de
--- Comment #5 from CharlyDelta waste@charlydelta.de --- I can confirm this. After selecting a deck to play, the search for an opponent starts. When an opponent is found, the deck selection loads again (at least I think that it occurs when an opponent is found, because the time that it takes to return to the deck selection can vary between 1-20 seconds).
Also, I can confirm the log created, which is:
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported
But this log is only output _ONCE_, even if I repeatedly try to find a match (clicking it again after I get returned to the deck selection). I also tried to overwrite bcrypt.dll to native, but this makes the game not even load up properly.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #6 from CharlyDelta waste@charlydelta.de --- Created attachment 57172 --> https://bugs.winehq.org/attachment.cgi?id=57172 Starting gwent, signing in, clicking "Casual Match"
This is what my log looks like
https://bugs.winehq.org/show_bug.cgi?id=42316
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz@gmail.com
--- Comment #7 from fjfrackiewicz@gmail.com --- (In reply to winetest from comment #3)
You need to attach the console output. Without owning the game its impossible to know whats going on.
In case it helps, GOG is going to be giving away beta keys to the game: https://www.gog.com/news/gwent_nilfgaard_has_arrived_celebrate_with_a_huge_b...
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #8 from CharlyDelta waste@charlydelta.de --- Quick update: The bug is still present for version 0.8.60 of Gwent
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #9 from CharlyDelta waste@charlydelta.de --- Another update: Bug still present in wine 2.1-staging
https://bugs.winehq.org/show_bug.cgi?id=42316
Dmitry fryngies@tomengine.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fryngies@tomengine.ru
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #10 from fjfrackiewicz@gmail.com --- Created attachment 57570 --> https://bugs.winehq.org/attachment.cgi?id=57570 Wine Staging 2.3 terminal output
In Wine Staging 2.3 using GOG Galaxy 1.1.28.49 and Gwent 0.8.60.1, I can't even get to the point where the bcrypt error comes up as the game freezes during the initial sign in.
Terminal output attached.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #11 from CharlyDelta waste@charlydelta.de --- With Wine 2.4-staging and the newest version of Gwent, I do not get this error message anymore (at least I think so, because now the log is getting spammed by some other outputs...)
However, the described bug still exist: After selecting a deck, it loads quite a it and then returns to the deck selection screen
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #12 from CharlyDelta waste@charlydelta.de --- Sorry, the previous comment was false. The fixme is still there:
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported
I just didn't see it because DX11 was spamming hundrets of fixmes per second
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #13 from fjfrackiewicz@gmail.com --- (In reply to CharlyDelta from comment #12)
Sorry, the previous comment was false. The fixme is still there:
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported
I just didn't see it because DX11 was spamming hundrets of fixmes per second
If you want to avoid DX11 spam, you can force the game to run in DX9 mode by simply setting "d3d11" to "disabled" in Wine's configuration utility.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #14 from CharlyDelta waste@charlydelta.de --- (In reply to fjfrackiewicz from comment #13)
(In reply to CharlyDelta from comment #12)
Sorry, the previous comment was false. The fixme is still there:
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported
I just didn't see it because DX11 was spamming hundrets of fixmes per second
If you want to avoid DX11 spam, you can force the game to run in DX9 mode by simply setting "d3d11" to "disabled" in Wine's configuration utility.
Yes, thank you, this is exactly what I did after my first comment. Then I discovered that the fixme is still printed. Unfortunately this came to my mind only after I made the first comment, so sorry again for spam.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #15 from CharlyDelta waste@charlydelta.de --- I am rather unfamiliar with how the workflows are etc, but this issue still has the status UNCONFIRMED. Shouldn't this be changed? I don't want to be demanding or anything, I just want to help somehow, but I not yet contributed to Wine and would need a guiding hand
https://bugs.winehq.org/show_bug.cgi?id=42316
ajgpetty@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ajgpetty@gmail.com
--- Comment #16 from ajgpetty@gmail.com --- fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported
still present when using Wine-2.5-Staging.
Have attached my log.
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #17 from ajgpetty@gmail.com --- Created attachment 57827 --> https://bugs.winehq.org/attachment.cgi?id=57827 Wine-2.5-Staging Log algorithm L"ECDSA_P384" not supported
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #18 from A Petty clicktoload@gmail.com --- Retested on 2.5-Staging and was able to play a multiplayer game. Had to add bcrypt to the overrides
https://bugs.winehq.org/show_bug.cgi?id=42316
--- Comment #19 from Hans Leidekker hans@meelstraat.net --- ECDSA_P384 is supported now, please retest.