[Bug 46595] New: Rainbow Six Siege hangs on Uplay splash screen
https://bugs.winehq.org/show_bug.cgi?id=46595 Bug ID: 46595 Summary: Rainbow Six Siege hangs on Uplay splash screen Product: Wine Version: 4.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: riesi(a)opentrash.com Distribution: --- Created attachment 63492 --> https://bugs.winehq.org/attachment.cgi?id=63492 Log without specific debug channels To make this clear the game is Battleye protected, but it does not even get far enough to load Battleye. At least I could not see any traces of a Battleye dll when looking at the logs with +loaddll. So the problem is that the game hangs on the Uplay splash screen and doesn't do anything else after that. There is no continuous log output or anything. It just sits there. The part of the log that's interesting for this issue is at the bottom of the file after: 0034:fixme:secur32:schannel_get_mac_algid unknown algorithm 200, cipher 23 This is all the output that is generated when the game tries to start and after its killed. If you need any additional logging with specific WINEDEBUG channels, I am happy to assist. Thanks in advance, Riesi -- 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=46595 --- Comment #1 from Stefan Riesenberger <riesi(a)opentrash.com> --- Created attachment 63505 --> https://bugs.winehq.org/attachment.cgi?id=63505 Log with +relay I was able to get a trace with +relay when starting the game from a different terminal as Uplay. Maybe this is more helpful. -- 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=46595 --- Comment #2 from Stefan Riesenberger <stefan.riesenberger(a)gmail.com> --- Created attachment 66631 --> https://bugs.winehq.org/attachment.cgi?id=66631 Patch by ZeroFault that fixes the hang. With this patch and the following launch options set in Uplay the game starts fine and lets you play solo missions. Be aware that it also requires the already staged bcrypt patches to let it connect to the Ubisoft servers. (Bug 47699) Launch options: /belaunch -be -- 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=46595 Stefan Riesenberger <stefan.riesenberger(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #66631|0 |1 is obsolete| | --- Comment #3 from Stefan Riesenberger <stefan.riesenberger(a)gmail.com> --- Created attachment 66737 --> https://bugs.winehq.org/attachment.cgi?id=66737 more correct patch by ZeroFault This patch should not be as hacky and could probably be accepted upstream, if someone wants to pickup the discussion. -- 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=46595 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- 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=46595 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |ntdll Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |z.figura12(a)gmail.com --- Comment #4 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- CC'ing Zebediah to nominate this patch for 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=46595 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |eb69da2a9cbbc4f9893ca6ae434 | |20c71f9b63571 Status|NEW |RESOLVED CC| |infyquest(a)gmail.com Resolution|--- |FIXED --- Comment #5 from Vijay Kamuju <infyquest(a)gmail.com> --- Should be fixed by https://source.winehq.org/git/wine.git/commitdiff/eb69da2a9cbbc4f9893ca6ae43... -- 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=46595 --- Comment #6 from Stefan Riesenberger <stefan.riesenberger(a)gmail.com> --- Can confirm that the commits from yesterday fixed R6S. Thanks -- 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=46595 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.12. -- 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