[Bug 40767] New: Indiana Jones and The Emperor' s Tomb quits after the splash screen
https://bugs.winehq.org/show_bug.cgi?id=40767 Bug ID: 40767 Summary: Indiana Jones and The Emperor's Tomb quits after the splash screen Product: Wine Version: 1.9.11 Hardware: x86 URL: http://www.gamershell.com/download_1856.shtml OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Regression SHA1: c89dc58deb9ba74d8dcd7faf7012203cff0724a0 Distribution: --- Reproduced this bug with the GOG.com and the original demo version. The problem happens in full-screen and virtual desktop mode too. After starting the game the splash screen is shown then the game suddenly quits. In the terminal I have fixme:win:EnumDisplayDevicesW ((null),0,0x33ea88,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x1fee2d8,0x00000000), stub! failed to create drawable err:d3d:wined3d_adapter_init Failed to get a GL context for adapter 0x1e1e90. fixme:win:EnumDisplayDevicesW ((null),0,0x1cee2d8,0x00000000), stub! X Error of failed request: GLXBadWindow Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 32 (X_GLXDestroyWindow) Serial number of failed request: 840 Current serial number in output stream: 847 Reverting the following commit fixes the crash so that the game plays some intro videos then finally hits bug #27594: commit c89dc58deb9ba74d8dcd7faf7012203cff0724a0 Author: Miklós Máté <mtmkls(a)gmail.com> Date: Thu May 26 23:43:14 2016 +0200 winex11: Use GLX 1.3 for windows. Differentiate between X window and GLX window, use GLX 1.3 for GL window create/destroy. IndyETDemo.exe (225M) sha1: d9c8b61616e29ef8ab75d1c72c55d30cf923471e wine-1.9.11-206-g03b06fb Fedora 23 32-bit XOrg 1.18.3 OpenGL vendor string: nouveau OpenGL renderer string: Gallium 0.4 on NV92 OpenGL core profile version string: 3.3 (Core Profile) Mesa 12.1.0-devel (git-87f0a04) OpenGL core profile shading language version string: 3.30 -- 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=40767 --- Comment #1 from Béla Gyebrószki <gyebro69(a)gmail.com> --- In the meantime I switched my vga card and tested this bug with mixed results: -on a GeForce GTS 250 the crash happens whether I'm using nouveau/mesa (git) or the binary drivers 340.96 -on a GeForce GT 730 the crash happens with nouveau/mesa but not with the latest binary drivers 364.19 What could that mean? Please let me know if you need debug logs or further tests. Wine 1.9.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.
https://bugs.winehq.org/show_bug.cgi?id=40767 --- Comment #2 from Bruno Jesus <00cpxxx(a)gmail.com> --- I can also confirm this in an Intel onboard graphics adapter. -- 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=40767 Miklós Máté <mtmkls(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtmkls(a)gmail.com --- Comment #3 from Miklós Máté <mtmkls(a)gmail.com> --- The problem is that wine calls glXCreateWindow twice on the same X window, and Mesa doesn't like that. It didn't happen with the games I tested previously. -- 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=40767 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |24705 -- 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=40767 j-r(a)online.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |j-r(a)online.de --- Comment #4 from j-r(a)online.de --- Also affects Agarest: Generations of War Reverting commit c89dc58deb9ba74d8dcd7faf7012203cff0724a0 works around the 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=40767 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |35993 -- 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=40767 --- Comment #5 from Miklós Máté <mtmkls(a)gmail.com> --- I just sent out patches to fix this. The problem was that due to a typo the gl_drawable structure wasn't cleaned up properly, but it wasn't an issue until I added GLX 1.3 support :) With GLX 1.3 this meant that the glx window wasn't destroyed along with the x window. As it turned out, xlib aggressively reuses window ids, and thus Wine ended up creating a glx window for a newly created x window, but the glx window of the previous x window with the same id was still around. Mesa caught this by crashing. -- 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=40767 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #6 from super_man(a)post.com --- It seems that your commit broke also bug 24705 and I tested your patch v2 and it did fix the isssue with that 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.
https://bugs.winehq.org/show_bug.cgi?id=40767 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #7 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still there in current wine (1.9.13) -- 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=40767 fjfrackiewicz(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz(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=40767 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #8 from winetest(a)luukku.com --- Created attachment 56887 --> https://bugs.winehq.org/attachment.cgi?id=56887 possible fix -- 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=40767 --- Comment #9 from Miklós Máté <mtmkls(a)gmail.com> --- (In reply to winetest from comment #8)
Created attachment 56887 [details] possible fix
That's cute. Three months ago I submitted v5 of that patch, but it was ignored for two months and then deferred due to the code freeze for Wine 2.0, and now v2 gets posted here? -- 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=40767 --- Comment #10 from winetest(a)luukku.com --- (In reply to Miklós Máté from comment #9)
(In reply to winetest from comment #8)
Created attachment 56887 [details] possible fix
That's cute. Three months ago I submitted v5 of that patch, but it was ignored for two months and then deferred due to the code freeze for Wine 2.0, and now v2 gets posted here?
I attached it because I found it from another bug thread I didnt know the version. I don't know how to search those patches that didnt go in. It would be good to get them into the bug threads. Even they woulndt merge they would help someone. -- 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=40767 --- Comment #11 from Miklós Máté <mtmkls(a)gmail.com> --- OK, here is v5: https://www.winehq.org/pipermail/wine-patches/2016-November/156015.html -- 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=40767 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte(a)systemsaviour.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=40767 --- Comment #12 from Aexander <kq3thih(a)mailnesia.com> --- (In reply to Miklós Máté from comment #9)
Three months ago I submitted v5 of that patch, but it was ignored for two months and then deferred due to the code freeze for Wine 2.0...
Code is unfrozen. With this patch Agarest would move from a garbage rating to gold. I've ran into this bug with a few other applications as well, sometimes intermittently. It would be great to have this in mainline. Resend? -- 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=40767 --- Comment #13 from j-r(a)online.de --- The problem is still present in 3.0rc4 in Indiana Jones, but I can no longer reproduce it in a fresh install of Agarest (GOG version). -- 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=40767 --- Comment #14 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still there in current wine. No plan to fix it? -- 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=40767 --- Comment #15 from Alexandre Julliard <julliard(a)winehq.org> --- It's hopefully fixed in git, please retest. -- 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=40767 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |ac4f2ac36f1b06f7bfe7647753d | |acbc4ce8522b3 --- Comment #16 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Fixed indeed, tested with nouveau/mesa 17.3.3. https://source.winehq.org/git/wine.git/commit/ac4f2ac36f1b06f7bfe7647753dacb... -- 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=40767 --- Comment #17 from Aexander <kq3thih(a)mailnesia.com> --- Also seems fixed for me with both HDNR1 and Agarest, which did not work in a clean prefix with 3.0rc4 here. Tried with both radeon/mesa 17.2.8 and on another PC binary NVidia drivers; multiple launches and succeeded on all of them. -- 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=40767 --- Comment #18 from joaopa <jeremielapuree(a)yahoo.fr> --- Fixed with my nvidia GPU and the proprietary blob. Not with my intel gpu and mesa driver. But maybe it is my setting for the intel gpu.... -- 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=40767 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #19 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.2. -- 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=40767 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstefani(a)winehq.org Target Milestone|--- |3.0.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=40767 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.0.x |--- --- Comment #20 from Michael Stefaniuc <mstefani(a)winehq.org> --- Removing the 3.0.x milestone from bugs included in 3.0.2. -- 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