http://bugs.winehq.org/show_bug.cgi?id=23135
Summary: Mass Effect 2 hangs/crashes after Shepherd is reanimated Product: Wine Version: 1.2-rc3 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
I installed using 'wisotool masseffect2', along with the little mouse hack and MWO recommended in the appdb. Then I tried playing the game, i.e. I tried to go to the cockpit to get the captain. The ship was attacked, and the captain was lost (re-entered the atmosphere?); then there was a fancy sequence showing him being reanimated by "the lazarus project". There was a loading screen that talked about universal clips - then when the game should have continued, it hung instead:
err:ntdll:RtlpWaitForCriticalSection section 0x7df00a20 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 001a, blocked by 000c, retrying (60 sec) fixme:dbghelp:validate_addr64 Unsupported address ffffffffb5d70000 ... fixme:faultrep:ReportFault 0x18fec88 0x0 stub err:ntdll:RtlpWaitForCriticalSection section 0x7df00a20 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 001a, blocked by 000c, retrying (60 sec) ...
and crashed.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #1 from Dan Kegel dank@kegel.com 2010-06-12 00:01:38 --- The patch I used was http://bugs2.winehq.org/attachment.cgi?id=15638 The registry entry I added was [Software\Wine\DirectInput] 1240428288 "MouseWarpOverride"="force"
http://bugs.winehq.org/show_bug.cgi?id=23135
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mass Effect 2 hangs/crashes |Mass Effect 2 hangs/crashes |after Shepherd is |after Shepard is reanimated |reanimated |
--- Comment #2 from Dan Kegel dank@kegel.com 2010-06-12 00:13:01 --- To get my terms right, the hang happens in the Awakening scene, described in http://masseffect.wikia.com/wiki/Mass_Effect_2_Guide before you wake up on the table.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #3 from Dan Kegel dank@kegel.com 2010-06-12 00:34:23 --- On second try, the game exited instead with
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 2341 requests (2340 known processed) with 0 events remaining.
This is with nvidia 195.36.24 on a GT 240 card.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #4 from Dan Kegel dank@kegel.com 2010-06-12 00:51:22 --- Tried gathering a log with +x11drv,+synchronous and this time it worked, so WINEDEBUG=+synchronous seems to be a workaround?
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #5 from Dan Kegel dank@kegel.com 2010-06-12 00:52:24 --- (Oh, and also for the record, the mouse hack + mwo don't work especially well for me; I have to move around to the other side of the window from the outside sometimes. But at least it's playable.)
http://bugs.winehq.org/show_bug.cgi?id=23135
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
--- Comment #6 from Austin English austinenglish@gmail.com 2010-06-13 13:09:49 --- This works fine for me on lucid 64bit, nvidia 9800gtx+, and the 256.25 drivers.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #7 from Scott Carrier scarrier_sonichero@comcast.net 2010-06-20 15:38:40 --- Almost the exact same error message locks up and eventually crashes Mirror's Edge every other time I load a checkpoint, usually after dying. Trying to continue a game from one of these usually results in locking up and eventually crashing the game, but rarely and randomly it works for about 3 lives before it happens again. Interestingly, starting a chapter from the beginning doesn't have any problem.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 2126 requests (2126 known processed) with 0 events remaining. err:ntdll:RtlpWaitForCriticalSection section 0x7deffa20 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0037, blocked by 0035, retrying (60 sec) fixme:dbghelp_dwarf:compute_location Only supporting one breg (18 -> 24) fixme:dbghelp:validate_addr64 Unsupported address fffffffff5970000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5e90000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff74c0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5940000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5860000 fixme:faultrep:ReportFault 0x267f288 0x0 stub err:ntdll:RtlpWaitForCriticalSection section 0x7deffa20 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0037, blocked by 0035, retrying (60 sec) wine: Critical section 7deffa20 wait failed at address 0x7bc356bd (thread 0037), starting debugger...
I was unable to start the debugger to get its readout. The program error box couldn't be clicked on, which is a known bug.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #8 from Dan Kegel dank@kegel.com 2010-06-20 16:32:22 --- Can you attach such a saved game file for the Mirror's Edge problem?
http://bugs.winehq.org/show_bug.cgi?id=23135
Scott Carrier scarrier_sonichero@comcast.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |scarrier_sonichero@comcast. | |net
--- Comment #9 from Scott Carrier scarrier_sonichero@comcast.net 2010-06-20 18:06:39 --- Mirror's Edge save file, stuck at a lock-up point when you hit continue game, at least on my computer. Place the file in My Documents/EA Games/Mirror's Edge/TdGame/Savefiles Rename it from SAVE FILE to your computer login's username.
http://www.filefront.com/16813799/SAFE%20FILE.dat
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #10 from Scott Carrier scarrier_sonichero@comcast.net 2010-06-22 10:25:32 --- My brother with a different computer just tried Mirror's Edge out. He couldn't even start the training level. It would lock up with a white screen while trying to load it. This is definitely a problem in wine.
http://bugs.winehq.org/show_bug.cgi?id=23135
Daniel Harvison sirbubbles01@yahoo.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sirbubbles01@yahoo.com.au
--- Comment #11 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-12 02:15:46 --- I'm using Ubuntu Lucid 64 bit, and various wine versions that I've compiled myself, going back to wine 1.1.39, and I get a crash after loading most of my savegames, or after a bink video plays, or for any number of other situations. The error message that usually shows up in the console is regarding the wine x11 driver, which makes little sense to me because I was able to finish the game five times on another linux kernel, the realtime or linux-rt in the repos.
Error message is as follows: err:ntdll:RtlpWaitForCriticalSection section 0x7e39f600 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0009, blocked by 0015, retrying (60 sec). Or some variation thereof.
Why would this game and others be acting up when they used to run fine on the same wine versions, video drivers, what have you?
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #12 from Dan Kegel dank@kegel.com 2010-07-12 10:30:07 --- I've heard a rumor that it's really a bink video bug, and your report helps confirm this. It's not surprising for an app bug to be nondeterministic...
Tempting to mark this bug NOT A WINE BUG, but I can't quite be sure.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #13 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-12 17:47:38 --- (In reply to comment #12)
I've heard a rumor that it's really a bink video bug, and your report helps confirm this. It's not surprising for an app bug to be nondeterministic...
Tempting to mark this bug NOT A WINE BUG, but I can't quite be sure.
Actually, it first happened for me when switching from the 2.6.31-11 rt kernel in ubuntu, to one of the newer generic ones. Works fine in the older kernel, just quite a bit slower.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #14 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-12 21:58:25 --- I think I've found a solution to keep ME2 running. It involves limiting the game to using only one cpu core with the following script.
padsp wine MassEffect2.exe & sleep 5 taskset -p 1 `pidof MassEffect2.exe` What is needed now is a way to apply this to the steam version of ME2, because this doesn't work with it at the moment. Maybe somehow launching wine and all programs run with it using taskset?
In short, ME2 doesn't seem to like multi core cpus. I myself have an amd 6000+, and this seems to be an issue in the windows world as well.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #15 from Scott Carrier scarrier_sonichero@comcast.net 2010-07-13 10:51:09 --- I just tried running taskset -p 1 `pidof MirrorsEdge.exe` which had no effect in game. However, I'm using the Steam version, and I'm running the command only once the main menu shows up.
In Mirror's Edge, the game always crashes when loading a level, so I think that it isn't a Bink bug in this game's case.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #16 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-14 13:54:39 --- (In reply to comment #15)
I just tried running taskset -p 1 `pidof MirrorsEdge.exe` which had no effect in game. However, I'm using the Steam version, and I'm running the command only once the main menu shows up.
In Mirror's Edge, the game always crashes when loading a level, so I think that it isn't a Bink bug in this game's case.
Seems like doing taskset in any way other than I did with directly executing Mass Effect 2 and then setting the affinity straight away doesn't want to work. Would love to know why. Setting it at launch definitely doesn't work. As for steam, no luck so far.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #17 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-16 00:53:15 --- (In reply to comment #16)
(In reply to comment #15)
I just tried running taskset -p 1 `pidof MirrorsEdge.exe` which had no effect in game. However, I'm using the Steam version, and I'm running the command only once the main menu shows up.
In Mirror's Edge, the game always crashes when loading a level, so I think that it isn't a Bink bug in this game's case.
Seems like doing taskset in any way other than I did with directly executing Mass Effect 2 and then setting the affinity straight away doesn't want to work. Would love to know why. Setting it at launch definitely doesn't work. As for steam, no luck so far.
I just found out about the wine task manager. Run it with wine taskmgr and set the process affinity to a single cpu/core. I've gotten good results using it with the steam version of mass effect 2. I just wish there was a wine way to automate the process, ie like imagecfg for windows.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #18 from Dan Kegel dank@kegel.com 2010-07-17 21:25:47 --- The downloadable beta, http://masseffect.bioware.com/cdn/A/ME2_DEMO/MassEffect2DemoEN.exe doesn't seem to suffer from this problem here. (Maybe it has an updated bink dll?)
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #19 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-18 09:37:25 --- (In reply to comment #18)
The downloadable beta, http://masseffect.bioware.com/cdn/A/ME2_DEMO/MassEffect2DemoEN.exe doesn't seem to suffer from this problem here. (Maybe it has an updated bink dll?)
Well the whole bink dll thing would work in with what I saw when I disabled bink videos in the game via a switch or ini file edit, or something. The game would work pretty much perfectly with no hassles, which I really don't understand. Shouldn't have to disable cpu cores for an issue like this, but it's there in the windows world too, from what I understand.
For me, this issue would strike when loading many levels, after most bink videos, and after more than a few minutes of playtime. Obviously the game wasn't quite as immersive with no bink videos though.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #20 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-25 04:46:54 --- I've had a bit of success with ME2 by stopping the cpufrequtils daemon, that is "sudo service cpufrequtils stop". I also added the grub boot option "clock=notsc" to my system, I'm not sure if that played a part or not. Note that notsc is for 64 bit systems, "clock=pit" might work for you. Again, I'm not sure it played a part in the outcome.
Mass Effect 2 seems to work quite well this way, and I think that cpufrequtils does not affect much when disabled in any case. So it seems clear that ME2 doesn't like cpu frequency adjustments being done mid-game. If there's any way to correct this other than what I've gone over here, I'd really like to know.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #21 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-07-25 04:48:47 --- (In reply to comment #20)
I've had a bit of success with ME2 by stopping the cpufrequtils daemon, that is "sudo service cpufrequtils stop". I also added the grub boot option "clock=notsc" to my system, I'm not sure if that played a part or not. Note that notsc is for 64 bit systems, "clock=pit" might work for you. Again, I'm not sure it played a part in the outcome.
Mass Effect 2 seems to work quite well this way, and I think that cpufrequtils does not affect much when disabled in any case. So it seems clear that ME2 doesn't like cpu frequency adjustments being done mid-game. If there's any way to correct this other than what I've gone over here, I'd really like to know.
To be clear about "clock=pit", that's for 32 bit systems.
http://bugs.winehq.org/show_bug.cgi?id=23135
Evan Goers megatog615@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |megatog615@gmail.com
--- Comment #22 from Evan Goers megatog615@gmail.com 2010-07-28 23:37:44 --- If you want to get around this bug, you can use the -nomovies switch to skip right to where Shepard wakes up, save the game, and start it back up without -nomovies.
Tedious, yes, but it works.
http://bugs.winehq.org/show_bug.cgi?id=23135
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #23 from Xavier Vachon xvachon@gmail.com 2010-10-18 16:02:56 CDT --- I am able to play through this section without problems in current git (1.3.5). I use the mouse and pulseaudio hacks, though I do not believe that they have any effect on this bug.
Dan, can you try again and confirm if this is fixed?
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #24 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-10-29 14:56:10 CDT --- (In reply to comment #23)
I am able to play through this section without problems in current git (1.3.5). I use the mouse and pulseaudio hacks, though I do not believe that they have any effect on this bug.
Dan, can you try again and confirm if this is fixed?
Done, and the problem persists, it's a problem with my cpu and the game design, specifically switching between cpu cores, which is borken in this case. I have an am2+ 6000 cpu, what's yours?
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #25 from Xavier Vachon xvachon@gmail.com 2010-10-29 14:59:42 CDT --- (In reply to comment #24)
(In reply to comment #23)
I am able to play through this section without problems in current git (1.3.5). I use the mouse and pulseaudio hacks, though I do not believe that they have any effect on this bug.
Dan, can you try again and confirm if this is fixed?
Done, and the problem persists, it's a problem with my cpu and the game design, specifically switching between cpu cores, which is borken in this case. I have an am2+ 6000 cpu, what's yours?
I have a quadcore Q6600. What I suggest is that you read this page : http://eengine.org/en/winehq-how-one-can-help/ and produce a sample .exe of the issue you have a problem with. This could maybe help the devs to reproduce the bug.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #26 from Dan Kegel dank@kegel.com 2010-10-29 15:37:45 CDT --- I've just been using the downloadable demo, which is fine.
Has anybody tried copying the bink dll from the demo to the retail game?
And/or has anybody tried the 1.01 or 1.02 ME2 patches, http://www.fileplanet.com/210098/210000/fileinfo/Mass-Effect-2---Patch-v1.01 http://www.fileplanet.com/213326/210000/fileinfo/Mass-Effect-2-Patch-v1.02- ? At least the first one seems to list fixes for similar things.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #27 from Xavier Vachon xvachon@gmail.com 2010-10-29 15:42:20 CDT --- I use patch 1.02(In reply to comment #26)
I've just been using the downloadable demo, which is fine.
Has anybody tried copying the bink dll from the demo to the retail game?
And/or has anybody tried the 1.01 or 1.02 ME2 patches, http://www.fileplanet.com/210098/210000/fileinfo/Mass-Effect-2---Patch-v1.01 http://www.fileplanet.com/213326/210000/fileinfo/Mass-Effect-2-Patch-v1.02- ? At least the first one seems to list fixes for similar things.
I use patch 1.02.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #28 from Dan Kegel dank@kegel.com 2010-10-29 15:45:22 CDT --- Maybe that's why it works for you... Daniel, can you try me2 1.02?
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #29 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-10-30 09:03:21 CDT --- (In reply to comment #28)
Maybe that's why it works for you... Daniel, can you try me2 1.02?
Since my copy of ME2 is of the Steam variety, the best I can do is probably try some cracks on the game and see how that goes. I'll give it a shot. BTW, the demo ran into the same problems, after the sequence of movies before the character creation screen, the game crashed.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #30 from Daniel Harvison sirbubbles01@yahoo.com.au 2010-10-30 11:55:26 CDT --- (In reply to comment #29)
(In reply to comment #28)
Maybe that's why it works for you... Daniel, can you try me2 1.02?
Since my copy of ME2 is of the Steam variety, the best I can do is probably try some cracks on the game and see how that goes. I'll give it a shot. BTW, the demo ran into the same problems, after the sequence of movies before the character creation screen, the game crashed.
Apologies...nothing seems to work, I've tried two different cracks, one for version 1.01 and one for version 1.02. Obviously not the same as having a real patch version, but I've not got much choice. Nothing changed with either crack.
http://bugs.winehq.org/show_bug.cgi?id=23135
jkyro@korjaussarja.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jkyro@korjaussarja.net
--- Comment #31 from jkyro@korjaussarja.net 2010-11-27 03:39:30 CST --- Using version 1.3.6 with mouse hack, still getting the hang without setting affinity. The workaround seems to affect performance quite a lot though.
This is clearly a race condition, something isn't quite thread-safe either in wine or in the game itself. I could try to do some debugging if someone could give some hints.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #32 from Dan Kegel dank@kegel.com 2010-11-27 06:39:25 CST --- I'm tempted to close this as INVALID because rumor is it's a game bug, and the demo works fine.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #33 from Austin English austinenglish@gmail.com 2010-12-22 17:34:16 CST --- (In reply to comment #32)
I'm tempted to close this as INVALID because rumor is it's a game bug, and the demo works fine.
I see it in the demo occasionally, actually...
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #34 from Daniel Harvison sirbubbles01@yahoo.com.au 2011-01-02 05:37:14 CST --- I've done some playing around with wine versions and mass effect 2 lately, and I can definitively say that Mass Effect 2 doesn't have this problem with wine 1.2-rc1, and the game seems to behave itself with this version of wine. If you try it with rc3 and any other more recent version of wine though, it causes problems as described in this bug, and when loading save games and loading levels.
I'd like to do some more involved bug testing, but don't think I have the skills. Can anyone help me?
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #35 from Austin English austinenglish@gmail.com 2011-01-03 12:43:42 CST --- (In reply to comment #34)
I've done some playing around with wine versions and mass effect 2 lately, and I can definitively say that Mass Effect 2 doesn't have this problem with wine 1.2-rc1, and the game seems to behave itself with this version of wine. If you try it with rc3 and any other more recent version of wine though, it causes problems as described in this bug, and when loading save games and loading levels.
I'd like to do some more involved bug testing, but don't think I have the skills. Can anyone help me?
If you can consistently reproduce the problem, a regression test should help: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #36 from Daniel Harvison sirbubbles01@yahoo.com.au 2011-01-06 18:20:25 CST --- (In reply to comment #35)
(In reply to comment #34)
I've done some playing around with wine versions and mass effect 2 lately, and I can definitively say that Mass Effect 2 doesn't have this problem with wine 1.2-rc1, and the game seems to behave itself with this version of wine. If you try it with rc3 and any other more recent version of wine though, it causes problems as described in this bug, and when loading save games and loading levels.
I'd like to do some more involved bug testing, but don't think I have the skills. Can anyone help me?
If you can consistently reproduce the problem, a regression test should help: http://wiki.winehq.org/RegressionTesting
Hello,
I can consistently and reliably play ME2 under wine-1.2-rc1, so I tried comparing rc1 to rc3, since I found that rc3 tends to crash with the err:ntdll:RtlpWaitForCriticalSection section crash. I wasn't able to fix anything by reverting patches. I am wondering though, what changes were made between wine1.2-rc1 and rc3 that might cause these crashes. I was looking at dlls/ntdll/critsection.c and noticed some differences, but I don't really know what that means. It was nothing I could revert through git though.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #37 from Austin English austinenglish@gmail.com 2011-01-06 18:23:19 CST --- (In reply to comment #36)
Hello,
I can consistently and reliably play ME2 under wine-1.2-rc1, so I tried comparing rc1 to rc3, since I found that rc3 tends to crash with the err:ntdll:RtlpWaitForCriticalSection section crash. I wasn't able to fix anything by reverting patches. I am wondering though, what changes were made between wine1.2-rc1 and rc3 that might cause these crashes. I was looking at dlls/ntdll/critsection.c and noticed some differences, but I don't really know what that means. It was nothing I could revert through git though.
The change was very likely not in dlls/ntdll, that code is for entering/exiting critical sections. Running a real regression test will tell you what patch introduced the change. If you've already got wine building from git, it should be pretty easy.
I can't get a consistent crash here though :-/.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #38 from Matteo Bruni matteo.mystral@gmail.com 2011-01-07 07:38:12 CST --- Created an attachment (id=32754) --> (http://bugs.winehq.org/attachment.cgi?id=32754) Don't call glPixelParameter with a random context.
This patch seems to fix the crash for me. There could be other bugs around, however.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #39 from Daniel Harvison sirbubbles01@yahoo.com.au 2011-01-07 09:35:26 CST --- (In reply to comment #38)
Created an attachment (id=32754)
--> (http://bugs.winehq.org/attachment.cgi?id=32754) [details]
Don't call glPixelParameter with a random context.
This patch seems to fix the crash for me. There could be other bugs around, however.
I just spent around half an hour loading savegames and running around the Normandy, which is usually guaranteed to eventually cause the crash, but so far with this patch, it's working perfectly. Much appreciated indeed.
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #40 from Xavier Vachon xvachon@gmail.com 2011-01-07 11:26:38 CST --- Matteo's patch has been committed. Can we get a confirmation from somebody else that this is fixed?
http://bugs.winehq.org/show_bug.cgi?id=23135
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #41 from Austin English austinenglish@gmail.com 2011-01-13 17:40:02 CST --- (In reply to comment #40)
Matteo's patch has been committed. Can we get a confirmation from somebody else that this is fixed?
Looks great here!
http://bugs.winehq.org/show_bug.cgi?id=23135
--- Comment #42 from Austin English austinenglish@gmail.com 2011-01-13 17:41:23 CST --- *** Bug 24805 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=23135
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #43 from Alexandre Julliard julliard@winehq.org 2011-01-21 13:43:38 CST --- Closing bugs fixed in 1.3.12.
-
wine-bugs＠winehq.org