[Bug 53346] New: Ubisoft connect lose connection after initialization
https://bugs.winehq.org/show_bug.cgi?id=53346 Bug ID: 53346 Summary: Ubisoft connect lose connection after initialization Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 72732 --> https://bugs.winehq.org/attachment.cgi?id=72732 Wine 7.11 WINEDEBUG=+cryptnet terminal output Hello, Wine 7.11. After login into Ubisoft connect, it tries to initialize and then fails with the error message: "Connection lost. A Ubisoft service is currently unavailable. Please try again later." Very similar to bug 53102, but the fix there doesn't seem to be enough. --- +cryptnet log snippet --- ... 0144:trace:cryptnet:CertDllVerifyRevocation (00000001, 1, 1, 0FAF7938, 00000001, 0FAF7954, 0FAF793C) 0144:trace:cryptnet:verify_cert_revocation_from_aia_ext OCSP URL = L"http://ocsp.digicert.com" 0144:fixme:cryptnet:check_ocsp_response_info check responder id 0144:trace:cryptnet:verify_cert_revocation verify_cert_revocation_from_aia_ext() returned 00000000 0144:trace:cryptnet:CertDllVerifyRevocation returning 1 (00000000) 0144:trace:cryptnet:CertDllVerifyRevocation (00000001, 1, 1, 0FAF7938, 00000001, 0FAF7954, 0FAF793C) 0144:trace:cryptnet:verify_cert_revocation_from_aia_ext OCSP URL = L"http://ocsp.digicert.com" 0144:fixme:cryptnet:check_ocsp_response_info check responder id 0144:trace:cryptnet:verify_cert_revocation verify_cert_revocation_from_aia_ext() returned 00000000 0144:trace:cryptnet:CertDllVerifyRevocation returning 1 (00000000) 0144:trace:cryptnet:CertDllVerifyRevocation (00000001, 1, 1, 0FAF7938, 00000001, 0FAF7954, 0FAF793C) 0144:warn:cryptnet:verify_cert_revocation no dist points/aia extension and no issuer 0144:trace:cryptnet:CertDllVerifyRevocation returning 0 (80092012) ... --- end log snippet --- Regards. -- 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=53346 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://ubistatic3-a.akamai | |hd.net/orbit/launcher_insta | |ller/UbisoftConnectInstalle | |r.exe Summary|Ubisoft connect lose |Ubisoft connect loses |connection after |connection after |initialization |initialization Keywords| |download, regression -- 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=53346 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Downgrading to wine 7.9 doesn't fix the issue (same cryptnet output). Regards. -- 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=53346 --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, This must be a change in the application cert/revocation, because I'm sure that I tested it wine 7.9 and it worked. Regards. -- 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=53346 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #3 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, It seems to have fixed itself. I updated to wine 7.13 and there was also an application update. After that the issue was gone. I downgraded to wine 7.11 and it's still working so it was either a certificate check temporary condition or an application bug. Marking invalid. Regards. -- 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=53346 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing INVALID. -- 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=53346 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|INVALID |--- --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I'm reopening this issue because it reappeared. While it may be caused by the application/Ubisoft service, what I've found is that it depends on the internet connection. I have two connections to the Internet: one is CABLE, the other is DSL. When connected through the CABLE connection, Ubisoft Connect fails to initialize. When connected through the DSL connection, Ubisoft Connect initialization is succesful. There must be some difference between the two connections that makes the application fail or succeed. I don't know what it is yet and so don't know if that difference triggers a bug in Wine or is simply an application/Ubisoft service bug. Regards. -- 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=53346 --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- Can you test on windows with both of those connections? -- 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=53346 --- Comment #7 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Created attachment 73462 --> https://bugs.winehq.org/attachment.cgi?id=73462 Through CABLE connection - Failure - Wine 7.19 winsock+wininet log -- 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=53346 --- Comment #8 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Created attachment 73463 --> https://bugs.winehq.org/attachment.cgi?id=73463 Through DSL connection - Success - Wine 7.19 winsock+wininet log Hello, Logs were made with Wine 7.19. Downgrading to 7.7 or switching to wine-staging doesn't fix the issue (same behavior: works on one connection and fails on the other). Regards. -- 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=53346 Erik Reider <ereider20010103(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ereider20010103(a)gmail.com --- Comment #9 from Erik Reider <ereider20010103(a)gmail.com> --- (In reply to Austin English from comment #6)
Can you test on windows with both of those connections?
I'm experiencing the same issue as stated above. My fiber connection won't work with Wine while a mobile hotspot from my phone works just fine. Both work in Windows 11. Let me know if you need additional logs from my end as well :) -- 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=53346 --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Austin English from comment #6)
Can you test on windows with both of those connections?
Hello, Same behavior on Windows 10 in a VirtualBox VM with NAT network: Consistently fails on CABLE connection and succeeds on DSL connection by just switching network connection outside of the VM between attempts. I guess in my case it's not a Wine bug? Regards. -- 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=53346 --- Comment #11 from Erik Reider <ereider20010103(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #10)
(In reply to Austin English from comment #6)
Can you test on windows with both of those connections?
Hello,
Same behavior on Windows 10 in a VirtualBox VM with NAT network: Consistently fails on CABLE connection and succeeds on DSL connection by just switching network connection outside of the VM between attempts.
I guess in my case it's not a Wine bug?
Regards.
I'm experiencing the exact same quirky result with a Windows 10 VM. Ethernet is a no go while my hotspot works. What's weird is that when booting into Windows 11 (not in a VM), everything works as expected!... Could this be a kernel issue? -- 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=53346 --- Comment #12 from Erik Reider <ereider20010103(a)gmail.com> --- (In reply to Erik Reider from comment #11)
(In reply to Olivier F. R. Dierick from comment #10)
(In reply to Austin English from comment #6)
Can you test on windows with both of those connections?
Hello,
Same behavior on Windows 10 in a VirtualBox VM with NAT network: Consistently fails on CABLE connection and succeeds on DSL connection by just switching network connection outside of the VM between attempts.
I guess in my case it's not a Wine bug?
Regards.
I'm experiencing the exact same quirky result with a Windows 10 VM. Ethernet is a no go while my hotspot works. What's weird is that when booting into Windows 11 (not in a VM), everything works as expected!...
Could this be a kernel issue?
I tried switching from a NAT network to a Bridged Adapter connected to my ethernet controller in the Windows 10 VM and it worked while still not working with NAT and in 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=53346 --- Comment #13 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Same result. Using bridged mode in VirtualBox made it work in Windows 10. I tried to set up a namespace with a virtual network interface bridge for Wine + Ubisoft Connect, but initialization still failed. Regards. -- 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=53346 --- Comment #14 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Olivier F. R. Dierick from comment #13)
Same result. Using bridged mode in VirtualBox made it work in Windows 10.
I tried to set up a namespace with a virtual network interface bridge for Wine + Ubisoft Connect, but initialization still failed.
It would be interesting to compare network traces from Windows and Wine, keeping NAT out of the equation. -- 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=53346 --- Comment #15 from Erik Reider <ereider20010103(a)gmail.com> --- (In reply to Hans Leidekker from comment #14)
It would be interesting to compare network traces from Windows and Wine, keeping NAT out of the equation.
Excuse my ignorance but how would one do that in Linux and in Windows? I'm not really a network person -- 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=53346 --- Comment #16 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Erik Reider from comment #15)
(In reply to Hans Leidekker from comment #14)
It would be interesting to compare network traces from Windows and Wine, keeping NAT out of the equation.
Excuse my ignorance but how would one do that in Linux and in Windows? I'm not really a network person
You'd use a program like Wireshark to capture network packets. -- 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=53346 --- Comment #17 from Erik Reider <ereider20010103(a)gmail.com> --- Created attachment 73483 --> https://bugs.winehq.org/attachment.cgi?id=73483 Wine with Ethernet (Not working) Here are my Wireshark outputs. I'm not really sure how to upload multiple files here so I'll just post multiple comments with attachments I guess. -- 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=53346 --- Comment #18 from Erik Reider <ereider20010103(a)gmail.com> --- Created attachment 73484 --> https://bugs.winehq.org/attachment.cgi?id=73484 Windows 10 VM Bridge Adapter (Working) Here's the Windows output. -- 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=53346 --- Comment #19 from Erik Reider <ereider20010103(a)gmail.com> --- Created attachment 73485 --> https://bugs.winehq.org/attachment.cgi?id=73485 Wine with Mobile Hotspot (working) Lastly the mobile hotspot one with 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=53346 --- Comment #20 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Someone on reddit found the explanation: --- quote from reddit [1] --- Somehow some setups/regions run into a MTU black hole with Ubisoft Connect through Proton on Linux. Enabling MTU probing (for the techies out there, rfc4821) will fix this automatically. Lowering the MTU manually works as well. --- end of quote --- I tested this with NetworkManager and it worked: 1. run in a terminal: nmcli connection modify <connection name> 802-3-ethernet.mtu 1452 2. set network off then on in NetworkManager GUI. 3. check that the interface MTU is changed in a terminal: ip link list To get the '802-3-ethernet.mtu' property name I ran: nmcli connection show <connection name> | grep 'mtu' The default value was 'auto'. I tried 1492 but it didn't work. 1452 did. I didn't test other values or enabling MTU probing. I think this makes the issue invalid in Wine. [1] https://www.reddit.com/r/SteamDeck/comments/ymqvbz/comment/j36kk4w/?utm_sour... Regards. -- 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=53346 --- Comment #21 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Is there an actual change in behaviour between Windows and 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.
participants (1)
-
WineHQ Bugzilla