[Bug 49109] New: Pillars of Eternity 2 - Deadfire [GoG Edition]: crashes at startup (Regression)
https://bugs.winehq.org/show_bug.cgi?id=49109 Bug ID: 49109 Summary: Pillars of Eternity 2 - Deadfire [GoG Edition]: crashes at startup (Regression) Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: speakn2erasmus(a)gmail.com Distribution: Other Created attachment 67082 --> https://bugs.winehq.org/attachment.cgi?id=67082 console output resulting after a crash The game [Pillars of Eternity 2: Deadfire] now crashes on startup with WINE 5.7 and also the current git as of 2020/05/05. The game was working for many versions of the 5.X series prior and worked last on version 5.6. After encountering the bug I did a regression test and located the first bad commit, output included below. sha1sum of relevent GoG installer. $ sha1sum "setup_pillars_of_eternity_ii_deadfire_v5.0.0.0040_(29201).exe" 9edcbf8be79d8da9aaad1cdd9c1ac87a26deda3b setup_pillars_of_eternity_ii_deadfire_v5.0.0.0040_(29201).exe [System info] OS: Manjaro 20.0 Lysia Kernel: x86_64 Linux 5.6.8-1-MANJARO Shell: bash 5.0.16 Resolution: 2560x1440 DE: GNOME 3.36.1 WM: Mutter (Wayland Session) CPU: Intel Core i5-3570K @ 4x 3.8GHz [46.0°C] GPU: Radeon RX Vega (VEGA10, DRM 3.36.0, MESA 20.0.6-2, LLVM 10.0.0) RAM: 7916MiB -- 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=49109 --- Comment #1 from speakn2erasmus(a)gmail.com --- Created attachment 67083 --> https://bugs.winehq.org/attachment.cgi?id=67083 bisect output pointing to first bad commit -- 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=49109 speakn2erasmus(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |speakn2erasmus(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=49109 speakn2erasmus(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |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=49109 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hverbeet(a)gmail.com Regression SHA1| |d16de1e06cb303350ba2461db4a | |57073c344d370 -- 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=49109 --- Comment #2 from Henri Verbeet <hverbeet(a)gmail.com> --- It's not entirely impossible that simply changing the code exposed a bug elsewhere, but the commit in question should have no effect unless you explicitly enable the wined3d Vulkan backend. (In which case currently much more would be broken.) Is there any chance that the bug is not 100% reproducible, and the actual regression was introduced by an earlier commit? -- 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=49109 --- Comment #3 from speakn2erasmus(a)gmail.com --- I don't know how to invoke the new wined3d Vulkan codepath so I don't think that's the problem. I only enter [ WINEPREFIX="..." wine PillarsofEternityII.exe ] Well I did the bisection using "git bisect start -- dlls/wined3d" assuming that is where the issue lay but maybe that was a mistake. I'll do the more generic bisection between 5.6 and 5.7 and report my result. -- 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=49109 --- Comment #4 from speakn2erasmus(a)gmail.com --- Created attachment 67091 --> https://bugs.winehq.org/attachment.cgi?id=67091 newer bisect result -- 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=49109 --- Comment #5 from speakn2erasmus(a)gmail.com --- I just added a newer bisect result that does indeed point to a different commit. I shouldn't have assumed it was a wined3d issue, my apologies for the previous bisection result. -- 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=49109 speakn2erasmus(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hans(a)meelstraat.net -- 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=49109 speakn2erasmus(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown -- 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=49109 speakn2erasmus(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|d16de1e06cb303350ba2461db4a |78e9b02cebf4b107aba69aa9a84 |57073c344d370 |5ab661a7daf10 -- 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=49109 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- That bisect result also seems suspect; it shouldn't affect any functionality. Are you sure that the bug only happens with that commit applied? -- 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=49109 --- Comment #7 from speakn2erasmus(a)gmail.com --- (In reply to Zebediah Figura from comment #6)
That bisect result also seems suspect; it shouldn't affect any functionality. Are you sure that the bug only happens with that commit applied?
I'm not sure. In keeping with the Regression Testing page I attempted to rebuild with that commit reverted (after resetting the bisect) but it would not successfully build. This is my first attempt at a regression test so I'm sorry about the missteps. Can you give me any guidance how I can provide any further useful info? -- 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=49109 --- Comment #8 from Zebediah Figura <z.figura12(a)gmail.com> --- If the commit cannot be cleanly reverted on top of current git, then in lieu of that it is generally most useful to test the commit itself and its parent, i.e. check 78e9b02ce and 0a35f0053a. It is possible that an error was made in 78e9b02ce, but not especially likely... -- 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=49109 mphantomx(a)yahoo.com.br changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mphantomx(a)yahoo.com.br --- Comment #9 from mphantomx(a)yahoo.com.br --- I think it's the same problem fixed here: https://bugs.winehq.org/show_bug.cgi?id=49128#c12 . -- 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=49109 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #10 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to PXMB from comment #9)
I think it's the same problem fixed here: https://bugs.winehq.org/show_bug.cgi?id=49128#c12 .
Yes, it seems likely. *** This bug has been marked as a duplicate of bug 49128 *** -- 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=49109 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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=49109 --- Comment #12 from speakn2erasmus(a)gmail.com --- Can confirm that building with the patch from the linked bug report the issue is resolved, the game launches again without issue. Many thanks to those involved. -- 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