[Bug 33858] New: FarCry 3 needs "4gb_patch" to run properly
http://bugs.winehq.org/show_bug.cgi?id=33858 Bug #: 33858 Summary: FarCry 3 needs "4gb_patch" to run properly Product: Wine Version: 1.6-rc3 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: berillions(a)gmail.com Classification: Unclassified Created attachment 44910 --> http://bugs.winehq.org/attachment.cgi?id=44910 Crash Medium/Ultra settings without 4gb_patch Hi, Even if they are the same crash log about msvcr100, this workaround does not works for the bug #32500. 4gb_patch is a tool which allow to have 4GB of virtual memory for a x86 executable instead of 2GB. See her website : http://www.ntcore.com/4gb_patch.php For my test, i play twice at FC3 without apply the patch to attach their bugreport. Laptop Caracteristics : - Nvidia GTX670MX - Intel Core I5 - Debian Unstable 64Bits - Nvidia drivers 319.17 - Wine 1.6-rc3 - 32bits clean wineprefix --- Test #1 (Medium Settings) --- I launch FarCry 3 with these graphic options : - Texture = Medium - Ambient Lighting = Medium - Shadow = Low - Post FX = Low - Geometry = Medium - Vegetation = Medium - Terrain = Medium - Water = Medium - Environment = Medium Result : With these graphic options, the game crashed after 10 minutes when i drove a car. This crash appears during the loading too. --- Test #2 (Very High Settings) --- I launch FarCry 3 with these graphic options : - Texture = High - Ambient Lighting = High - Shadow = Ultra - Post FX = Ultra - Geometry = Ultra - Vegetation = Very High - Terrain = High - Water = Very High - Environment = High Result : the game crash quickly during the first loading when i want to load my savegame. I attach only one log for these two tests because it's the same crash for both. --- Test #3 (Very High Settings) --- Same graphic settings than test #2 but i patched farcry3.exe with the 4gb_patch tool. Result : No crash after 25 minutes ------- Thanks, Max -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 Dan Kegel <dank(a)kegel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dank(a)kegel.com Summary|FarCry 3 needs "4gb_patch" |FarCry 3 crashes unless you |to run properly |set the LARGEADDRESSAWARE | |bit in its .exe --- Comment #1 from Dan Kegel <dank(a)kegel.com> 2013-06-22 14:43:56 CDT --- That tool sets the LARGEADDRESSAWARE flag on the binary. It's probably the same as "editbin /LARGEADDRESSAWARE foo.exe". Berillions mentioned that this only works in a 32 bit wineprefix; the game has other problems in a 64 bit wineprefix. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 --- Comment #2 from Berillions <berillions(a)gmail.com> 2013-06-22 14:59:18 CDT --- (In reply to comment #1)
That tool sets the LARGEADDRESSAWARE flag on the binary. It's probably the same as "editbin /LARGEADDRESSAWARE foo.exe".
Berillions mentioned that this only works in a 32 bit wineprefix; the game has other problems in a 64 bit wineprefix.
As explain in the bug report #32500, FarCry 3 does not works if Wine is set to WiXP. You must to set win7 to launch game. As explain in the bug report #33776, Uplay games don't work if Wine is set to Win7 but they work if Wine is set to WinXP. So, i can't test if this bug exist in 64bits wineprefix. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 --- Comment #3 from Austin English <austinenglish(a)gmail.com> 2013-06-22 19:41:43 CDT --- Have you tested this on 32-bit windows? It may very well be an application bug. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 --- Comment #4 from Berillions <berillions(a)gmail.com> 2013-06-23 02:44:24 CDT --- (In reply to comment #3)
Have you tested this on 32-bit windows? It may very well be an application bug.
Yes, i installed today Windows 7 32bits and i test the game with the same graphic settings (Ultra settings + Directx9 mode) and the game has never crashed. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 Berillions <berillions(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |33776 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 --- Comment #5 from Berillions <berillions(a)gmail.com> 2013-06-23 05:38:05 CDT --- Created attachment 44917 --> http://bugs.winehq.org/attachment.cgi?id=44917 FC3 crash into 64bits prefix+Ultra settings without 4gb_patch I forgot the workaround in the bug report #32500, i must to disable fullscreen in game option to launch the game with WinXP to avoid the crash. So, i tried to play at FC3 (Ultra settings) with and without 4gb_patch : - without 4gb_patch : The game crash during the first loading like with the 32 bits wineprefix - with 4gb_patch : No problem, i played during 30mins with Ultra settings without crash. I attach the crash log for FC3 without 4gb_patch, i have this error : err:d3d:resource_init Out of memory! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 --- Comment #6 from Berillions <berillions(a)gmail.com> 2013-09-18 11:33:23 CDT --- Bug still exist in wine-1.7.2 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 --- Comment #7 from Berillions <berillions(a)gmail.com> 2013-12-06 15:46:50 CST --- (In reply to comment #6)
Bug still exist in wine-1.7.2
Still exist on wine-1.7.8 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33858 DL <dredgingthelake(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dredgingthelake(a)gmail.com --- Comment #8 from DL <dredgingthelake(a)gmail.com> --- This bug also exists with Far Cry 2 at higher settings/resolutions. At the least it crashes with 1440p at Very High/Ultra High settings. After applying the 4GB patch, no crashes occur. -- 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=33858 Bug 33858 depends on bug 33776, which changed state. Bug 33776 Summary: UPlay games does not work into 64Bits prefix and Wine set to Vista/Win7 https://bugs.winehq.org/show_bug.cgi?id=33776 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- 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=33858 --- Comment #9 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine? -- 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=33858 --- Comment #10 from Berillions <berillions(a)gmail.com> --- (In reply to Austin English from comment #9)
This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine?
Still exist on Wine 1.7.51. 4Gb_patch still required to avoid the crash. -- 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=33858 Gabriel Corona <gabriel.corona(a)enst-bretagne.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gabriel.corona(a)enst-bretagn | |e.fr --- Comment #11 from Gabriel Corona <gabriel.corona(a)enst-bretagne.fr> --- Similar bug https://bugs.winehq.org/show_bug.cgi?id=34658 for Bioshock 2. I wrote a patch for Wine which enforces the LARGEADDRESSAWARE flag in order to work around this for Bioshock 2. I also wrote a (FOSS) program which patches the .exe (https://github.com/randomstuff/pe-set-laa) as an alternative to the non-free ones. -- 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=33858 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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=33858 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #12 from joaopa <jeremielapuree(a)yahoo.fr> --- What about this bug with current wine(3.20)? -- 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=33858 --- Comment #13 from Andrey Gusev <andrey.goosev(a)gmail.com> --- Still valid. -- 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=33858 Andrey Gusev <andrey.goosev(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrey.goosev(a)gmail.com --- Comment #14 from Andrey Gusev <andrey.goosev(a)gmail.com> --- *** Bug 46770 has been marked as a duplicate of this 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=33858 --- Comment #15 from Andrey Gusev <andrey.goosev(a)gmail.com> --- *** Bug 46868 has been marked as a duplicate of this 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=33858 --- Comment #16 from Andrey Gusev <andrey.goosev(a)gmail.com> --- *** Bug 46507 has been marked as a duplicate of this 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=33858 Andrey Gusev <andrey.goosev(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|FarCry 3 crashes unless you |Multiple games crash |set the LARGEADDRESSAWARE |without LARGEADDRESSAWARE |bit in its .exe |flag (Far Cry 3, Splinter | |Cell: Blacklist, The | |Testament of Sherlock | |Holmes) -- 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=33858 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #17 from Zebediah Figura <z.figura12(a)gmail.com> --- I really wouldn't. Setting IMAGE_FILE_LARGE_ADDRESS_AWARE is a generic workaround for a generic problem that has many causes and no generic solution. An actually valid solution may look different for each application, and in some cases there may be nothing we can do. Not to mention that making the bug about IMAGE_FILE_LARGE_ADDRESS_AWARE is not great in the first place, since that's just a workaround and cannot be a real solution. -- 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=33858 Paul Gofman <gofmanp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp(a)gmail.com --- Comment #18 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Zebediah Figura from comment #17)
Not to mention that making the bug about IMAGE_FILE_LARGE_ADDRESS_AWARE is not great in the first place, since that's just a workaround and cannot be a real solution.
The bug title looks unfortunate, as the absence of LARGEADDRESSAWARE flag is of course not a bug and is not the reason of the problem. Other than that, isn't it useful to collect the multiple applications which fail most likely due to address space exhaustion? Maybe along with changing bug title? -- 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=33858 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Multiple games crash |Multiple 32-bit |without LARGEADDRESSAWARE |applications crash due to |flag (Far Cry 3, Splinter |virtual address space |Cell: Blacklist, The |exhaustion (Far Cry 3, |Testament of Sherlock |Splinter Cell: Blacklist, |Holmes) |The Testament of Sherlock | |Holmes) --- Comment #19 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Paul Gofman from comment #18)
(In reply to Zebediah Figura from comment #17)
Not to mention that making the bug about IMAGE_FILE_LARGE_ADDRESS_AWARE is not great in the first place, since that's just a workaround and cannot be a real solution.
The bug title looks unfortunate, as the absence of LARGEADDRESSAWARE flag is of course not a bug and is not the reason of the problem. Other than that, isn't it useful to collect the multiple applications which fail most likely due to address space exhaustion? Maybe along with changing bug title?
I'm not sure I see how it's useful, given what I said above—ways to relieve address space pressure, if they even exist, may be specific to each application affected by exhaustion. A bug titled something like "multiple applications exhaust address space" can't really be closed, not even as WONTFIX. -- 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=33858 --- Comment #20 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Zebediah Figura from comment #19)
I'm not sure I see how it's useful, given what I said above—ways to relieve address space pressure, if they even exist, may be specific to each application affected by exhaustion.
I don't see how the ways to relieve address space pressure are specific to applications, at least the ones gathered here now. The common problem is that Wine needs more virtual address space than Windows, mostly due to native libraries often eating more address space (with pulseaudio and opengl somewhere on top). Maybe some Wine components could use optimization in that regards too. It is not a single localized issue in Wine, yes, but what specifics do you see with regards to applications gathered here? And if is anyone going to do something in Wine or some libraries to attempt to relief memory pressure a bit, isn't it easier that the information is linked to the single place, so it is easier to test with different applications?
A bug titled something like "multiple applications exhaust address space" can't really be closed, not even as WONTFIX.
Probably a lot of the multiple individual bugs for this cannot be ever closed the same way, as whatever can be done will reduce the probability of the specific app crash, but will likely not eliminate it completely. If there are convincing enough reasons to think that the issue is about the same, why having distinct records? -- 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=33858 --- Comment #21 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Paul Gofman from comment #20)
(In reply to Zebediah Figura from comment #19)
I'm not sure I see how it's useful, given what I said above—ways to relieve address space pressure, if they even exist, may be specific to each application affected by exhaustion.
I don't see how the ways to relieve address space pressure are specific to applications, at least the ones gathered here now. The common problem is that Wine needs more virtual address space than Windows, mostly due to native libraries often eating more address space (with pulseaudio and opengl somewhere on top). Maybe some Wine components could use optimization in that regards too.
If it's things like PulseAudio or OpenGL, there's broadly little we can do, and in that case it may have to be resolved WONTFIX. But sometimes specific Wine components eat more address space than they need to. Bottom line, I guess, sometimes excessive address space use is a bug (e.g. a leak) and can be fixed; sometimes it's a matter of one of many parts of Wine using more memory than it really needs, sometimes this regarding one or more system components, sometimes it's all necessary overhead related to API translation. Usually PulseAudio and OpenGL are by far the biggest culprit, sure, but not always.
It is not a single localized issue in Wine, yes, but what specifics do you see with regards to applications gathered here? And if is anyone going to do something in Wine or some libraries to attempt to relief memory pressure a bit, isn't it easier that the information is linked to the single place, so it is easier to test with different applications?
Nothing with these applications, but of course I haven't debugged any of them. It may be that all of the applications mentioned here can't be helped by anything in Wine. I'm personally ambivalent as to whether metabugs are useful in general, though the policy here seems to be to avoid them. In the case of address space exhaustion, though, I don't know what there is to test. The problem is quite simple: too much address space is being used. Using less is pretty much universally good. Probably some applications will be helped, and for others it won't be enough.
A bug titled something like "multiple applications exhaust address space" can't really be closed, not even as WONTFIX.
Probably a lot of the multiple individual bugs for this cannot be ever closed the same way, as whatever can be done will reduce the probability of the specific app crash, but will likely not eliminate it completely. If there are convincing enough reasons to think that the issue is about the same, why having distinct records?
Well, maybe. If there's a leak triggered by a specific application causing address space exhaustion, that's a bug and can be fixed. Some other things that are less clearly bugs can probably be fixed. Anything that can't be fixed in Wine is probably fair to resolve as WONTFIX. But it really does depend on the application. The fix for a bug with a title like this one would have to fix *every* application that suffers from address space exhaustion, which is pretty well impossible, or we'd have to resolve it as WONTFIX and thereby say that *no* such application can be fixed, which isn't true either (even if it's rare that there's anything we can 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=33858 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #22 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I think this metabug should be titled 'Wine leaves less virtual address space for 32-bit applications than Windows' and not collect application specific bugs, unless it is made certain that the application bug is caused by the amount of total VA space available within Wine and not by leaks or bad-behaving code. Generic ways to reduce Wine and components VAS footprint fit this metabug. Applications specific bugs that are caused by other kind of VAS exhaustion should be triaged according to the cause of VAS exhaustion and collected on the related bugs. Fix for them don't fit in this metabug because they don't reduce the default VAS footprint of Wine and components. Regards. -- 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=33858 --- Comment #23 from Henri Verbeet <hverbeet(a)gmail.com> --- (In reply to Zebediah Figura from comment #21)
I'm personally ambivalent as to whether metabugs are useful in general, though the policy here seems to be to avoid them.
In case it helps to point out, the alternative to metabugs we use is keywords. I.e., if there's consensus that collecting/grouping the various bugs related to address space exhaustion is generally useful, what we'd do would be to introduce a keyword and add it to the relevant bugs. -- 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=33858 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|Multiple 32-bit |Far Cry 3 crashes due to |applications crash due to |virtual address space |virtual address space |exhaustion |exhaustion (Far Cry 3, | |Splinter Cell: Blacklist, | |The Testament of Sherlock | |Holmes) | --- Comment #24 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Zebediah Figura from comment #17)
I really wouldn't.
I agree. (In reply to Henri Verbeet from comment #23)
(In reply to Zebediah Figura from comment #21)
I'm personally ambivalent as to whether metabugs are useful in general, though the policy here seems to be to avoid them.
In case it helps to point out, the alternative to metabugs we use is keywords. I.e., if there's consensus that collecting/grouping the various bugs related to address space exhaustion is generally useful, what we'd do would be to introduce a keyword and add it to the relevant bugs.
Right, and it sounds like a good idea for these bugs. In the meantime I'm going to reopen the bugs recently resolved as duplicates of this one. -- 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=33858 --- Comment #25 from Paul Gofman <gofmanp(a)gmail.com> --- I was not really advocating for the creation of metabugs. I just had some reasons to think that all the linked bugs are essentially about the same single issue (maybe a broad one), i. e., it is not a metabug. But if there is a consensus that it is not the case though, I don't think I have convincing enough arguments against that. -- 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=33858 --- Comment #26 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- *** Bug 46770 has been marked as a duplicate of this 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=33858 Anya <maniikarabera(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maniikarabera(a)protonmail.ch -- 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=33858 --- Comment #27 from Andrey Gusev <andrey.goosev(a)gmail.com> --- There is a big chance that the problem has gone after bundling FAudio. I don't yet tried with Far Cry, but other affected games work fine. -- 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=33858 soredake <broaden_acid002(a)simplelogin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|broaden_acid002(a)simplelogin | |.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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla