[Bug 43469] New: Star Wars the old republic give an error message and exits after latest update
https://bugs.winehq.org/show_bug.cgi?id=43469 Bug ID: 43469 Summary: Star Wars the old republic give an error message and exits after latest update Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gnarlin(a)gmail.com Distribution: --- Here's the error message: Certificate authentication failed, please contact customer support This happened very recently with the game's latest update. -- 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=43469 --- Comment #1 from Freyr Ólafsson <gnarlin(a)gmail.com> --- Created attachment 58848 --> https://bugs.winehq.org/attachment.cgi?id=58848 picture of error message popup -- 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=43469 Freyr Ólafsson <gnarlin(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=43469 Freyr Ólafsson <gnarlin(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gnarlin(a)gmail.com -- 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=43469 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #2 from Sebastian Lackner <sebastian(a)fds-team.de> --- I assume you use Wine Staging, is that correct? The issue sounds like what is described in https://dev.wine-staging.com/patches/164/. -- 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=43469 --- Comment #3 from Freyr Ólafsson <gnarlin(a)gmail.com> --- (In reply to Sebastian Lackner from comment #2)
I assume you use Wine Staging, is that correct? The issue sounds like what is described in https://dev.wine-staging.com/patches/164/.
Yes, you are right. This does indeed seem to be the issue I am dealing with. Has this patch been merged upstream? If it's merged how long until it's compiled into the Ubuntu staging ppa? Is it a matter of days, weeks... longer? -- 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=43469 Maik Wagner <maiktapwagner(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maiktapwagner(a)aol.com --- Comment #4 from Maik Wagner <maiktapwagner(a)aol.com> --- Created attachment 58853 --> https://bugs.winehq.org/attachment.cgi?id=58853 Little console output on wine 2.13 (non-staging) Confirming on a fresh installation. You do not need to download the whole 25 GB to test out this but. Console output isn't really revealing but attached. -- 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=43469 Paul Gofman <gofmanp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp(a)gmail.com --- Comment #5 from Paul Gofman <gofmanp(a)gmail.com> --- It can be fixed in vanilla Wine by pulling just the following patches from Wine Staging on top of the current git: https://github.com/wine-compholio/wine-staging/blob/master/patches/wintrust-... https://dev.wine-staging.com/patches/164/ (from comment #2) https://github.com/wine-compholio/wine-staging/blob/master/patches/crypt32-S... -- 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=43469 --- Comment #6 from Freyr Ólafsson <gnarlin(a)gmail.com> --- (In reply to Paul Gofman from comment #5)
It can be fixed in vanilla Wine by pulling just the following patches from Wine Staging on top of the current git:
https://github.com/wine-compholio/wine-staging/blob/master/patches/wintrust- WinVerifyTrust/0003-wintrust-Verify-image-hash-in-WinVerifyTrust.patch
https://dev.wine-staging.com/patches/164/ (from comment #2)
https://github.com/wine-compholio/wine-staging/blob/master/patches/crypt32- SHA_OIDs/0001-crypt32-Recognize-sha256-384-512-KEY-OIDs.patch
I do not relish having to patch and compile wine. Have these patches been merged upstream? Does anyone know how long until they will go into 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=43469 Alexander Waldemar Ahjolinna <ahjolinna(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahjolinna(a)yahoo.com --- Comment #7 from Alexander Waldemar Ahjolinna <ahjolinna(a)yahoo.com> --- (In reply to Freyr Ólafsson from comment #6)
(In reply to Paul Gofman from comment #5)
It can be fixed in vanilla Wine by pulling just the following patches from Wine Staging on top of the current git:
https://github.com/wine-compholio/wine-staging/blob/master/patches/wintrust- WinVerifyTrust/0003-wintrust-Verify-image-hash-in-WinVerifyTrust.patch
https://dev.wine-staging.com/patches/164/ (from comment #2)
https://github.com/wine-compholio/wine-staging/blob/master/patches/crypt32- SHA_OIDs/0001-crypt32-Recognize-sha256-384-512-KEY-OIDs.patch
I do not relish having to patch and compile wine. Have these patches been merged upstream? Does anyone know how long until they will go into staging?
it has been merged and I test it with "wine-staging-git" from aur on my arch system...and YES everything works and is just fine now -- 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=43469 --- Comment #8 from Maik Wagner <maiktapwagner(a)aol.com> --- Hello everyone, I also got informed of a temporary workaround but I have no idea if this can be applied to wine: https://www.reddit.com/r/swtor/comments/6qyz4v/certificate_authentication_fa... -- 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=43469 --- Comment #9 from Alexander Waldemar Ahjolinna <ahjolinna(a)yahoo.com> --- (In reply to Maik Wagner from comment #8)
Hello everyone,
I also got informed of a temporary workaround but I have no idea if this can be applied to wine:
https://www.reddit.com/r/swtor/comments/6qyz4v/ certificate_authentication_failure/
just wait for wine-staging 2.14 release (should arrive anytime now) it will have this new patch that will fix this issue, no need for any work around. (or install the latest git version, if your distro has one or you know how to compile one) (PS. if you don't know SWTOR works nowadays out of the box using wine-staging so there is no need for "swtor_fix.exe" file or any other settings/confs/downloads https://github.com/wine-compholio/wine-staging/releases -- 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=43469 --- Comment #10 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Alexander Waldemar Ahjolinna from comment #9)
(or install the latest git version, if your distro has one or you know how to compile one)
For people unfamiliar with how to compile Wine, please note that you can also grab packages from the Wine daily build bot at https://dev.wine-staging.com/builder/. Packages are kept available for the last 30 days. Just click on a Wine build, then click on "Downloads" (at the bottom of the list) and grab the package files for the distros you need. There is no repository for daily builds, so all files have to be downloaded manually. For Debian Sid 64-bit this would be for example: winehq-staging_2.13.0~sid_amd64.deb wine-staging_2.13.0~sid_amd64.deb wine-staging-amd64_2.13.0~sid_amd64.deb wine-staging-i386_2.13.0~sid_i386.deb (Please note that the version number encoded in the package files is still 2.13 because Wine Staging 2.14 was not released yet.) -- 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=43469 --- Comment #11 from Alexander Waldemar Ahjolinna <ahjolinna(a)yahoo.com> --- (In reply to Sebastian Lackner from comment #10)
(In reply to Alexander Waldemar Ahjolinna from comment #9)
(or install the latest git version, if your distro has one or you know how to compile one)
For people unfamiliar with how to compile Wine, please note that you can also grab packages from the Wine daily build bot at https://dev.wine-staging.com/builder/. Packages are kept available for the last 30 days. Just click on a Wine build, then click on "Downloads" (at the bottom of the list) and grab the package files for the distros you need. There is no repository for daily builds, so all files have to be downloaded manually. For Debian Sid 64-bit this would be for example:
winehq-staging_2.13.0~sid_amd64.deb wine-staging_2.13.0~sid_amd64.deb wine-staging-amd64_2.13.0~sid_amd64.deb wine-staging-i386_2.13.0~sid_i386.deb
(Please note that the version number encoded in the package files is still 2.13 because Wine Staging 2.14 was not released yet.)
@ Sebastian Lackner: unfortunately that doesn't seem to include mac builds, I'm arch user so I don't personally care but there are some SWTOR gamers on mac that do care -- 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=43469 --- Comment #12 from Alexander Waldemar Ahjolinna <ahjolinna(a)yahoo.com> --- okay the 2.14 release should be close anyways so whatever -- 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=43469 --- Comment #13 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Alexander Waldemar Ahjolinna from comment #11)
@ Sebastian Lackner: unfortunately that doesn't seem to include mac builds, I'm arch user so I don't personally care but there are some SWTOR gamers on mac that do care
Of course it does include builds for macOS 10.8+, its directly the first entry ("Cross Mac OS X"). -- 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=43469 --- Comment #14 from Alexander Waldemar Ahjolinna <ahjolinna(a)yahoo.com> --- (In reply to Sebastian Lackner from comment #13)
(In reply to Alexander Waldemar Ahjolinna from comment #11)
@ Sebastian Lackner: unfortunately that doesn't seem to include mac builds, I'm arch user so I don't personally care but there are some SWTOR gamers on mac that do care
Of course it does include builds for macOS 10.8+, its directly the first entry ("Cross Mac OS X").
damn..I'm really blind nowdays, I need to get my eyes check..okay, I just didn't notice that there is a mac version for "Development builds" but not for "Staging builds" ...whatever the difference is off topic anyways -- 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=43469 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|Wine |Wine-staging See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=41356 Resolution|--- |FIXED CC| |erich.e.hoover(a)wine-staging | |.com, michael(a)fds-team.de Component|-unknown |-unknown Status|UNCONFIRMED |RESOLVED --- Comment #15 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Alexander Waldemar Ahjolinna from comment #14)
damn..I'm really blind nowdays, I need to get my eyes check..okay, I just didn't notice that there is a mac version for "Development builds" but not for "Staging builds" ...whatever the difference is
off topic anyways
You still looked wrong, of course its also available for Staging builds. Anyway, this specific issue should be fixed in Wine Staging 2.14. Since this specific bug affected only Wine Staging versions, I'm moving it to the Staging category and will mark it as FIXED. The development version should not need any wintrust patches (they only make checks more strict), and the remaining issue (the OID patchset) is covered by bug 41356. -- 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=43469 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed Staging 3.14 -- 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