[Bug 51173] New: Bloons TD 6: Crash when attempting llaunch
https://bugs.winehq.org/show_bug.cgi?id=51173 Bug ID: 51173 Summary: Bloons TD 6: Crash when attempting llaunch Product: Wine-staging Version: 6.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fv61590(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70042 --> https://bugs.winehq.org/attachment.cgi?id=70042 Terminal output during appliaction crash. Using wine-6.9 (staging). On Arch Linux with kernel 5.12.6. Crashes when attempting to launch Bloons TD 6 from the wine bottle I have created for Win10 with 64-bit architecture. It is the only application located in that bottle, and thus is isolated from tampering from other applications. It seems to be a Unity Engine crash, as this is reported in the terminal output attached, it was working fine before the update done on <05-22-2021>. -- 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=51173 --- Comment #1 from fv61590(a)gmail.com --- The game was downloaded as a torrent, but worked perfectly fine with the (at-the-time) current wine build available in my repository. Including torrent magnet link if it serves of any purpose for debugging purposes: magnet:?xt=urn:btih:58cece566748fbe790c535f10627f3ac19c53bff&dn=Bloons%20TD%206%20v25.1.3828%20by%20Pioneer -- 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=51173 fv61590(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Bloons TD 6: Crash when |Bloons TD 6: Crash when |attempting llaunch |attempting launch -- 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=51173 --- Comment #2 from Alexandre Julliard <julliard(a)winehq.org> --- Comment deleted, please don't post links to illegal downloads. -- 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=51173 --- Comment #3 from fv61590(a)gmail.com --- (In reply to Alexandre Julliard from comment #2)
Comment deleted, please don't post links to illegal downloads.
I am very sorry, wanted to provide a link to possibly help but should have considered it might not be the best idea, thank you for taking the time to remove the comment. -- 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=51173 Sveinar Søpler <cybermax(a)dexter.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #4 from Sveinar Søpler <cybermax(a)dexter.no> --- Maybe related? https://bugs.winehq.org/show_bug.cgi?id=51172 Could you test with wine-staging-6.8? -- 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=51173 --- Comment #5 from fv61590(a)gmail.com --- (In reply to Sveinar Søpler from comment #4)
Maybe related? https://bugs.winehq.org/show_bug.cgi?id=51172
Could you test with wine-staging-6.8?
I tried building wine-staging-6.8 by cloning the wine repo and changing to the 6.8 release branch and doing the same with wine-staging and applying the patches with the available script, but come C files produced errors when compiling saying they were missing a certain header file <stdarg.h> where va_list was declared. I am unaware of whether this is a bug or how can I build or unselect certain patches as I am not well versed in how all the patches interact. And also the precommit_hook.sh script from the wine-staging repo spits out at the end: 1 out of 1 hunk FAILED ERROR: Changes to file dlls/wined3d/wined3d.spec don't apply: nvapi-Stub_DLL I can build regular wine-6.8 but as you specified using the staging patches, with my current knowledge am unable to get that to compile. -- 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=51173 --- Comment #6 from Sveinar Søpler <cybermax(a)dexter.no> --- It is easy to miss stuff when you mess around with git-tree's, so what i usually do is to reset my local branch with e.g (to reset the wine repo to wine-6.8): git reset --hard wine-6.8 && git clean -xdf This way if you have patched your local git tree, you will just "roll back" what you have done locally :) The staging repo uses a slightly different tag, so to reset your local staging tree to eg. staging-6.8, you can use: git reset --hard v6.8 && git clean -xdf However, the other issue seems fixed now with https://github.com/wine-staging/wine-staging/commit/69765f438bd1f2822f0b2147... Hopefully this is related, and fix it for Bloons TD 6 aswell. PS. You can ofc also download the source outside of git: https://www.winehq.org/announce/6.8 https://github.com/wine-staging/wine-staging/archive/refs/tags/v6.8.tar.gz -- 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=51173 --- Comment #7 from fv61590(a)gmail.com --- Wow, I was able to read the documentation and everything went smoothly, forgot to add make -jN to the build to make it exponentially quicker, but alas that sped up the final steps. Was able to build wine-staging-6.8 and the game ran fine. Time to build with HEAD of the master branch of staging to see if the commit mentioned fixes the 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=51173 fv61590(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from fv61590(a)gmail.com --- Fixed! Was able to build with latest wine-staging commits. Sveinar Søpler mentioned a commit for fixing some issues, and that seemed to be the solution, thank you for your contribution and hard work. -- 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=51173 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed wine-staging bug. -- 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