http://bugs.winehq.org/show_bug.cgi?id=15984
Summary: Black and White: crashes with page fault on temple completion Product: Wine Version: 1.1.8 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jcollins@asgardsrealm.net
Created an attachment (id=17170) --> (http://bugs.winehq.org/attachment.cgi?id=17170) log of entire Black and White run
Black and White runs pretty well (some textures are black) up until completion of the temple at which point it appears to hang. I've logged the entire run from start to the hang. The apparent hang appears to be due to an exception, specifically:
wine: Unhandled page fault on read access to 0xffffffff at address 0x7deff986 (t hread 0009), starting debugger... Unhandled exception: page fault on read access to 0xffffffff in 32-bit code (0x7 deff986).
Full details are in the attached log file.
http://bugs.winehq.org/show_bug.cgi?id=15984
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other
http://bugs.winehq.org/show_bug.cgi?id=15984
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d
--- Comment #1 from Lei Zhang thestig@google.com 2008-11-10 21:32:24 --- What video card / driver version?
Can you repeat this every time?
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #2 from Jamin Collins jcollins@asgardsrealm.net 2008-11-11 06:31:00 --- Yes, 100% reproducible. Based on the test reports, others are seeing the same problem.
01:00.0 VGA compatible controller: nVidia Corporation Quadro FX 570M (rev a1)
This happens with both the 173.14.12 and 177.80 nvidia drivers.
http://bugs.winehq.org/show_bug.cgi?id=15984
didli didli@auone.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |didli@auone.jp
--- Comment #3 from didli didli@auone.jp 2008-12-13 05:10:30 --- (In reply to comment #0)
Created an attachment (id=17170)
--> (http://bugs.winehq.org/attachment.cgi?id=17170) [details]
log of entire Black and White run
Black and White runs pretty well (some textures are black) up until completion of the temple at which point it appears to hang.
Same here with kernel 2.6.27-9, Wine 1.1.10 & Radeon X800SE + Catalyst 8.12
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #4 from John Haywards normandy@web.de 2009-04-01 13:31:33 --- Created an attachment (id=20255) --> (http://bugs.winehq.org/attachment.cgi?id=20255) Log using wine 1.1.18 (+launch patch)
Still existing in wine 1.1.18.
http://bugs.winehq.org/show_bug.cgi?id=15984
ragnara-dba@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ragnara-dba@gmx.de
--- Comment #5 from ragnara-dba@gmx.de 2009-06-22 13:15:35 --- I had this with Wine 1.1.24 under Archlinux.
http://bugs.winehq.org/show_bug.cgi?id=15984
Matthias-F14@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Matthias-F14@gmx.de
--- Comment #6 from Matthias-F14@gmx.de 2009-09-27 15:04:57 --- I get the same error before completiton of the temple if I try to save the game using Ctrl+S. So it's possible that's an error produced due to saving. This could be the reason for the crash after completiton of the temple, because the program then saves the game automatically.
I'm using Wine 1.1.29, nVidia Quadro FX 770M with nvidia drivers 180.11 and kernel 2.6.27-11
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #7 from Jeff Zaroyko jeffz@jeffz.name 2009-09-27 15:17:07 --- Can someone attach a backtrace for wine-1.1.30 with proper debug symbols? (either compile from source or install them)
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #8 from Matthias-F14@gmx.de 2009-09-28 17:02:23 --- Created an attachment (id=23813) --> (http://bugs.winehq.org/attachment.cgi?id=23813) Log using wine-1.1.30 - Saving game
Starting Black & White and after the first movement tutorial trying to save the game using Ctrl+S
http://bugs.winehq.org/show_bug.cgi?id=15984
Christian Weiske cweiske@cweiske.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cweiske@cweiske.de
--- Comment #9 from Christian Weiske cweiske@cweiske.de 2009-11-22 10:23:27 --- I can confirm this bug on 1.1.33
http://bugs.winehq.org/show_bug.cgi?id=15984
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #10 from Vitaliy Margolen vitaliy@kievinfo.com 2009-11-22 11:53:26 --- Confirming per comment 9
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #11 from ragnara-dba@gmx.de 2010-06-03 06:34:50 --- Still crashs with Wine 1.2-rc2 *sigh*
Archlinux i686, kernel 2.6.33, Nvidia GeForce 9600 GT (driver version 195.36.15).
http://bugs.winehq.org/show_bug.cgi?id=15984
Zach Goldberg zgold550@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zgold550@gmail.com
--- Comment #12 from Zach Goldberg zgold550@gmail.com 2010-11-11 22:10:31 CST --- @ragnara-dba@gmx.de are you able to get the game to run at all on >= Wine 1.2? I'm actually not having much luck getting past the loading screens on 1.2+ and on 1.33- it actually crashes before even showing a splash screen for me. Are you doing anything special? Running the patch?
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #13 from Zach Goldberg zgold550@gmail.com 2010-11-11 22:14:58 CST --- Actually I take that back... applying patch 1.1 allows the game to load past the loading screen in 1.2+
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #14 from Zach Goldberg zgold550@gmail.com 2010-11-11 22:29:29 CST --- Confirmed, B&W 1.1 still crashes when saving even under Wine 1.3.6.
http://bugs.winehq.org/show_bug.cgi?id=15984
Itzamna xamaniqinqu@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xamaniqinqu@gmail.com
--- Comment #15 from Itzamna xamaniqinqu@gmail.com 2010-12-04 17:30:29 CST --- Black & White does not crash due to a segmentation fault while saving specifically, but due to a call to surface_add_dirty_rect() without having a texture handy (see bug 14939). This is because when one saves, the game creates a message box using this function call - but since the required texture is not found, a segmentation fault is thrown. The same crash occurs when going to the God's Playground (by pressing F2) and by starting a Skirmish game, in all instances calls to surface_add_dirty_rect() are made. I have written patches implementing DXT1->ARGB4444 and DXT1->XRGB1555 texture conversion (lo-res textures are now visible, no more black silhouettes or invisible objects - see http://bugs.winehq.org/show_bug.cgi?id=14939 if you want to try them out). All we need is an XRGB1555->DXT1 function and we'll be able to save without crashing and enjoy the best game ever made. I'll have my patch ready within 2 days, keep checking back.
P.S.: Please vote on bug 14939, it will help include these patches in HEAD once the legal side of the story is resolved.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #16 from Itzamna xamaniqinqu@gmail.com 2010-12-12 15:23:28 CST --- Created an attachment (id=32471) --> (http://bugs.winehq.org/attachment.cgi?id=32471) Backtrace with debug symbols of Black & White segmentation fault. A heap corruption occurs in GetFileAttributesA.
Contrary to earlier versions of Wine, in git commit ab8959a0503efef032235acbabc0fcbe81fcd1a1 Black & White crashes in GetFileAttributesA(), as opposed to surface_add_dirty_rect(). Let's hope it's not another, unrelated bug.
http://bugs.winehq.org/show_bug.cgi?id=15984
Itzamna xamaniqinqu@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #32471|Backtrace with debug |Backtrace with debug description|symbols of Black & White |symbols of Black & White |segmentation fault. A heap |segmentation fault under |corruption occurs in |Wine 1.3.9. A heap |GetFileAttributesA. |corruption occurs in | |GetFileAttributesA.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #17 from Itzamna xamaniqinqu@gmail.com 2010-12-12 20:27:33 CST --- Created an attachment (id=32472) --> (http://bugs.winehq.org/attachment.cgi?id=32472) Backtrace showing the segmentation fault is caused by shoddy implementation of ddraw_surface7_Blt.
After a lot of debugging, I managed to identify the problem:
Any time the game saves (auto save after temple completion, when starting a skirmish game, before going to the God's Playground), Black & White creates a screenshot thumbnail to accompany the savegame, which can be viewed in the Temple. However, only a portion of the screen is copied, for which blitting is used. For this, a so-called DDBltFx structure is passed to the Wine DirectDraw function ddraw_surface7_Blt(). If this DDBltFx structure contains dds (DirectDraw Surface) pointers, Wine should replace the ddraw surfaces with WineD3D surfaces. However, this is not being done - therefore, important pointers and variables end up being NULL, causing a segmentation fault further down the road.
I'm working on completing the ddraw_surface7_Blt() function, any assistance is welcome. I've included a backtrace, though note I implemented a dummy XRGB1555->DXT1 conversion function to get at the blitting operation.
http://bugs.winehq.org/show_bug.cgi?id=15984
jannis kripton@kripserver.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kripton@kripserver.net
http://bugs.winehq.org/show_bug.cgi?id=15984
Zdenek Behan rain@matfyz.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rain@matfyz.cz
--- Comment #18 from Zdenek Behan rain@matfyz.cz 2011-03-01 23:18:07 CST --- In latest git, I'm getting an entirely different backtrace: Backtrace: =>0 0x7e03839b texture_cleanup+0xbb(This=0x4576388) [/home/rain/projects/wine.git/dlls/wined3d/texture.c:212] in wined3d (0x0033f164) 1 0x7e03846e IWineD3DTextureImpl_Release+0x3d(iface=0x4576388) [/home/rain/projects/wine.git/dlls/wined3d/texture.c:255] in wined3d (0x0033f1c4) 2 0x7e0be363 ddraw_surface7_Release+0x82(iface=0x456e128) [/home/rain/projects/wine.git/dlls/ddraw/surface.c:357] in ddraw (0x102332f8) 0x7e03839b texture_cleanup+0xbb [/home/rain/projects/wine.git/dlls/wined3d/texture.c:212] in wined3d: call *0x8(%eax)
Looks like the bug moved from surface creation to surface deletion. I wonder if it's just a different manifestation of the same bug.
http://bugs.winehq.org/show_bug.cgi?id=15984
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #23813|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #19 from Zdenek Behan rain@matfyz.cz 2011-03-02 21:58:26 CST --- After a while of crashing the game and tracing, i saw quite a few backtraces. Some of them has been exactly what was reported by Itzamna, some were slightly different, but all seem to essentially boil down to memory corruption and subsequent pointer dereference soon after in the code. This matches the behaviour of crashing in many different ways, likely not at the spot with the real issue.
I don't share the opinion that this is necessarily caused by surface_add_dirty_rect(). Missing texture conversion functions happen quite a bit and the blt function code definitely looks like handling those carefully.
I spent quite a while debugging and tracing the problem, and the one thing standing out in the trace is the use of ddraw_surface7_Blt, where both source and destination rectangles are filled in. Throughout the rest of the trace, this function is always gets (nil) passed in place of rectangles. There's always precisely two calls two ddraw_surface7_Blt() with a rectangle, each with a different rectangle, and the crash occurs right after release of the first surface:
trace:ddraw:ddraw_surface7_Blt iface 0x42c1058, dst_rect (0,0)-(256,128), src_surface 0x42b0780, src_rect (0,0)-(256,128), flags 0x1000000, fx (nil). ... trace:ddraw:ddraw_surface7_Blt iface 0x42b8cc8, dst_rect (0,128)-(128,192), src_surface 0x42b0780, src_rect (0,128)-(128,192), flags 0x1000000, fx (nil). ... trace:ddraw:ddraw_surface7_Release 0x42c1058 decreasing refcount to 0. wine: Unhandled page fault on read access to 0x4545524e at address 0x7e03439b (thread 0020), starting debugger...
I can attach the whole tail of the trace if anyone feels they want to see.
I'm slowly delving into it and enabling more debug channels to perhaps get a more detailed information.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #20 from Itzamna xamaniqinqu@gmail.com 2011-03-02 22:20:45 CST --- Hello Zdenek,
I abandoned the hypothesis that the segmentation fault happens in surface_add_dirty_rect() after looking into ddraw_surface7_Blt(). This function is not fully implemented; a comment in the source code says so too. I won't be able to hack on Wine for a while, I hope someone can implement blitting.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #21 from Zdenek Behan rain@matfyz.cz 2011-03-02 23:53:34 CST --- (In reply to comment #20)
Hello Zdenek,
I abandoned the hypothesis that the segmentation fault happens in surface_add_dirty_rect() after looking into ddraw_surface7_Blt(). This function is not fully implemented; a comment in the source code says so too. I won't be able to hack on Wine for a while, I hope someone can implement blitting.
Actually, I wouldn't be sure about that either. There is a TODO comment, but nothing implies that this is the case.
One thing I do know fairly certain is which surface gets b0rked. One of the traces I made shows the bogus addresses inside surface passed to IWineD3DTextureImpl_Release, which are the most likely place where the corruption happens, and incidentally, the cleaning of that structure is the last thing that happens right before segfault. I have yet to trace the surface since its creation, rather than watching its destruction.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #22 from Itzamna xamaniqinqu@gmail.com 2011-03-03 00:06:35 CST --- The crash occurs when saving. I remember that Black & White makes these small, DXT compressed thumbnails of a screenshot taken when saving for viewing in the citadel. It, however, makes a screenshot of only part of the screen, for which it uses blitting. It just so happens the DDBltFx struct is not fully implemented in Wine ddraw, which I'm pretty sure causes the segmentation fault. Look here:
=>0 0x7ef8fb2b RtlAllocateHeap+0xab(heap=0x110000, flags=0x000a, size=0x20010) [/home/itzamna/src/wine/dlls/ntdll/../../include/wine/list.h:98] in ntdll (0x0033ecd0) 1 0x7d8fbfdc resource_init+0xdb(iface=0x4669928, resource_type=WINED3DRTYPE_SURFACE, device=0x145740, size=0x20000, usage=0, format=0x142638, pool=WINED3DPOOL_SCRATCH, parent=0x0(nil), parent_ops=0x7d99a4a0) [/home/itzamna/src/wine/dlls/wined3d/resource.c:66] in wined3d (0x0033ed30) 2 0x7d94e849 surface_init+0xe8(surface=0x4669928, surface_type=SURFACE_OPENGL, alignment=0x0008, width=0x0100, height=0x0100, level=0, lockable=0x0001, discard=0x0001, multisample_type=WINED3DMULTISAMPLE_NONE, multisample_quality=0, device=0x145740, usage=0, format_id=WINED3DFMT_B5G5R5X1_UNORM, pool=WINED3DPOOL_SCRATCH, parent=0x0(nil), parent_ops=0x7d99a4a0) [/home/itzamna/src/wine/dlls/wined3d/surface.c:376] in wined3d (0x0033eda0) 3 0x7d8bfbbf IWineD3DDeviceImpl_CreateSurface+0xce(iface=0x145740, Width=0x0100, Height=0x0100, Format=WINED3DFMT_B5G5R5X1_UNORM, Lockable=0x0001, Discard=0x0001, Level=0, Usage=0, Pool=WINED3DPOOL_SCRATCH, MultiSample=WINED3DMULTISAMPLE_NONE, MultisampleQuality=0, Impl=SURFACE_OPENGL, parent=0x0(nil), parent_ops=0x7d99a4a0, surface=0x33ee94) [/home/itzamna/src/wine/dlls/wined3d/device.c:1060] in wined3d (0x0033eeb0) 4 0x7d952aa8 IWineD3DBaseSurfaceImpl_Blt+0x607(iface=0x46696b0, DestRect=<is not available>, src_surface=0x4661328, SrcRect=(nil), flags=0x1000000, DDBltFx=(nil), Filter=WINED3DTEXF_LINEAR) [/home/itzamna/src/wine/dlls/wined3d/surface_base.c:1173] in wined3d (0x0033ef20) 5 0x7e113798 ddraw_surface7_Blt+0x167(iface=0x46695b8, DestRect=(nil), SrcSurface=0x4661230, SrcRect=0xdac6dac6, Flags=0x1000000, DDBltFx=(nil)) [/home/itzamna/src/wine/dlls/ddraw/surface.c:907] in ddraw (0x00000000) 0x7ef8fb2b RtlAllocateHeap+0xab [/home/itzamna/src/wine/dlls/ntdll/../../include/wine/list.h:98] in ntdll: movl %eax,0x4(%edx) 98 elem->next->prev = elem->prev;
When I'm less occupied with college, I'll look further into this bug. Though I hope it's quashed by then.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #23 from Zdenek Behan rain@matfyz.cz 2011-03-03 00:45:43 CST --- Created an attachment (id=33512) --> (http://bugs.winehq.org/attachment.cgi?id=33512) Skips the function that causes crash
This is very messy and effectively skips releasing the surfaces but has two important uses:
1) Let's you play and save the game once. This helps debugging because going through the intro with every iteration gets on your nerves after the third or fourth time.
2) Demonstrates which function causes corruption.
http://bugs.winehq.org/show_bug.cgi?id=15984
Zdenek Behan rain@matfyz.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #33512|0 |1 is obsolete| |
--- Comment #24 from Zdenek Behan rain@matfyz.cz 2011-03-07 21:26:53 CST --- Created an attachment (id=33563) --> (http://bugs.winehq.org/attachment.cgi?id=33563) Returns DDRAW_UNSUPPORTED in the failure point
Returning UNSUPPORTED in the snapshot creation is correctly handled by Black & White, and causes all saved game screenshots to be empty (instead of garbage), but makes the game perfectly playable and not crashing (in this spot).
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #25 from Itzamna xamaniqinqu@gmail.com 2011-03-08 00:53:00 CST --- Thank you very much, Zdenek! Your hack is genious through simplicity. Black & White works perfectly (well, disregarding the savegame thumbnails ;)) here.
I wrote a patch to handle DXT decompression ( http://bugs.winehq.org/attachment.cgi?id=32374 ), with it textures are no longer black / invisible.
Fire me an e-mail if you want an online match sometime!
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #26 from Zdenek Behan rain@matfyz.cz 2011-03-08 01:16:56 CST --- I actually believe this to be not very hacky. It merely returns unsupported in a case which is apparently not supported, and the game copes with that just fine. I'm no expert in ddraw to say if this influences any other cases that do work, but if not, I think it could be up for inclusion in the main tree with a proper fixme statement included.
Not to cheer early though, I have experienced _some_ crashes. Exactly one was a save game (quick save - ctrl+s) right before entering the level 1 vortex. The other was supposedly unrelated - I'm running in a virtual desktop, and I accidentally resize the borders sometimes, one of those crashed the app.
That said, the game may be decently playable, just make sure to save often, and brace up for later levels. I remember those being tough, if only for a massive slowdown because of level size and occasional death because memory bloat. (who knows if those are relevant on today's computers, I played it years ago last time)
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #27 from Zdenek Behan rain@matfyz.cz 2011-03-14 15:09:57 CDT --- Ok, much more cheerful now. Just for sake of testing (what other reason could I possibly have), I played through the whole game. No crashes, at least not out of the ordinary game bugs that I've seen before.
http://bugs.winehq.org/show_bug.cgi?id=15984
nh2@deditus.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nh2@deditus.de
http://bugs.winehq.org/show_bug.cgi?id=15984
James Le Cuirot chewi@aura-online.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chewi@aura-online.co.uk
http://bugs.winehq.org/show_bug.cgi?id=15984
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #28 from joaopa jeremielapuree@yahoo.fr 2011-07-27 03:36:58 CDT --- Does the game work without any hack or native dlls now?
I am not sure to have understood the last comment.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #29 from Zdenek Behan rain@matfyz.cz 2011-07-28 15:19:25 CDT --- I don't recall using any native dlls. Just follow what's said in http://appdb.winehq.org/objectManager.php?sClass=application&iId=156
http://bugs.winehq.org/show_bug.cgi?id=15984
Damian Ivanov damianatorrpm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |damianatorrpm@gmail.com
--- Comment #30 from Damian Ivanov damianatorrpm@gmail.com 2011-09-25 22:51:20 CDT --- Hi wine patched with attachment 33563 breaks other apps. I tried with Robin Hood _the Legend of Sherwood is completely broken with the patch.
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #31 from Zdenek Behan rain@matfyz.cz 2011-10-09 18:16:13 CDT --- Does the game work before the patch and break after the patch?
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #32 from Damian Ivanov damianatorrpm@gmail.com 2011-10-09 22:23:41 CDT --- yes, it works before the patch and fails after patch (blank screen and only the mouse cursor is there). There is a demo from robin hood out http://compactiongames.about.com/library/demos/bl_robinhood_demo.htm
http://bugs.winehq.org/show_bug.cgi?id=15984
--- Comment #33 from Damian Ivanov damianatorrpm@gmail.com 2012-06-26 02:27:14 CDT --- Is still an issue in wine 1.5.6 or newer?
http://bugs.winehq.org/show_bug.cgi?id=15984
butraxz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |butraxz@gmail.com
--- Comment #34 from butraxz@gmail.com 2013-04-21 14:34:29 CDT --- No update for over 900 days. Is still an issue with 1.5.28 or higher ?
https://bugs.winehq.org/show_bug.cgi?id=15984
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED
--- Comment #35 from Austin English austinenglish@gmail.com --- (In reply to butraxz from comment #34)
No update for over 900 days. Is still an issue with 1.5.28 or higher ?
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=15984
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #36 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=15984
Sam sam.h.russell@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sam.h.russell@gmail.com
--- Comment #37 from Sam sam.h.russell@gmail.com --- Created attachment 52373 --> https://bugs.winehq.org/attachment.cgi?id=52373 Rebase patch for 1.7.51
https://bugs.winehq.org/show_bug.cgi?id=15984
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|ABANDONED |---
--- Comment #38 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Sam Russell from comment #37)
Created attachment 52373 [details] Rebase patch for 1.7.51
I take that this still happens in current unpatched Wine, right? Reopening.
https://bugs.winehq.org/show_bug.cgi?id=15984
Christian Widmer shadow@umbrox.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shadow@umbrox.de
--- Comment #39 from Christian Widmer shadow@umbrox.de --- I tested Black and White and the game did not crash at the specified point. I think this bug is has been fixed in the meantime.
https://bugs.winehq.org/show_bug.cgi?id=15984
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |425e84dac5c87f6b1e7d89b3630 | |17a045e4c0626 Status|REOPENED |RESOLVED
--- Comment #40 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Christian Widmer from comment #39)
I tested Black and White and the game did not crash at the specified point. I think this bug is has been fixed in the meantime.
Thank you for the heads up, should have been fixed by 425e84dac5c87f6b1e7d89b363017a045e4c0626.
https://bugs.winehq.org/show_bug.cgi?id=15984
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #41 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.7.