https://bugs.winehq.org/show_bug.cgi?id=38322
Bug ID: 38322 Summary: Call of Duty 4 Modern Warfare 3: Wine crashes when Steam is starting the game Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: timsta2000@googlemail.com Distribution: ---
Created attachment 51163 --> https://bugs.winehq.org/attachment.cgi?id=51163 backtrace.txt, the wine "error box" has given me
I've installed PlayOnLinux and downloaded the game over Steam and if I try to start it, Wine crashes when Steam is starting MW3. I've changed the Windows version from Windows XP to Windows 8 and now Steam is showing me a small empty black box before starting the game and then it crashes.
I have a Dualboot-System with Ubuntu 14.10 and Windows 8.
https://bugs.winehq.org/show_bug.cgi?id=38322
timsta2000@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu Severity|normal |trivial
https://bugs.winehq.org/show_bug.cgi?id=38322
--- Comment #1 from Austin English austinenglish@gmail.com --- PlayOnLinux is not supported, please retest in vanilla wine 1.7.39 and if still present, attach the full terminal output.
https://bugs.winehq.org/show_bug.cgi?id=38322
--- Comment #2 from timsta2000@googlemail.com --- OK. I've deleted everything and installed Wine 1.7.39. Then I've installed Steam and then Call Of Duty MW1( because this has only 10GB not 14GB ). But now its in 640*480( with a screen with 1600*900 ) and I cant change the resolution. If I try it and confirm the changes in the menu, the game crashes but Steam is still alive...
And the worst thing with that is, that it keeps the resolution at 640*480 until I restart the System.
Can you help me here or do I have to open a new Report?
https://bugs.winehq.org/show_bug.cgi?id=38322
narri xqwerty123@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xqwerty123@luukku.com
--- Comment #3 from narri xqwerty123@luukku.com --- You can keep console open background and use command xrandr -s 1600x900 to restore the resolution.
You need to provide the content that wine gives while it fails to start the game. Otherwise there is nothing to fix here. Developers don't have crystal balls...
https://bugs.winehq.org/show_bug.cgi?id=38322
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #4 from Adam Bolte abolte@systemsaviour.com --- Created attachment 55006 --> https://bugs.winehq.org/attachment.cgi?id=55006 1.9.13-cod-wm3-sp.log
Still an issue with CoD: MW3 for the single player campaign in 1.9.13. The multiplayer campaign works fine without any overrides or cracks.
https://bugs.winehq.org/show_bug.cgi?id=38322
Christian Inci chris.pcguy.inci@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chris.pcguy.inci@gmail.com
--- Comment #5 from Christian Inci chris.pcguy.inci@gmail.com --- This seems to be a duplicate of #32515.
https://bugs.winehq.org/show_bug.cgi?id=38322
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |crawford.benjamin15@gmail.c | |om
--- Comment #6 from Matteo Bruni matteo.mystral@gmail.com --- *** Bug 42371 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=38322
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com, | |xerox_xerox2000@yahoo.co.uk
--- Comment #7 from winetest@luukku.com --- (In reply to Christian Inci from comment #5)
This seems to be a duplicate of #32515.
I think too it's dupe of bug 32515 comment 63 confirmed by Adam who is at this bug too.
https://bugs.winehq.org/show_bug.cgi?id=38322
--- Comment #8 from Adam Bolte abolte@systemsaviour.com --- Ah yes. I did not try playing the campaign per se, but did play almost all of the survival levels solo (did not unlock the last ~4 because I'm not quite at level 25 yet) as well as the first mission level without an issue.
The only issue I've seen thus far to prevent Gold status (with the patch from bug #32515) is the intro cut scene running at around 1 FPS, which is unrelated.
I guess I should try starting the campaign next time I am able to test to prove that won't crash, and then this bug can be safely closed. But I fully expect it to work.
https://bugs.winehq.org/show_bug.cgi?id=38322
Gijs Vermeulen acescopezz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |acescopezz@gmail.com, | |sebastian@fds-team.de
--- Comment #9 from Gijs Vermeulen acescopezz@gmail.com --- Since this was confirmed working in this bug and in bug 32515 this could be marked Staged? With patchset: https://github.com/wine-compholio/wine-staging/tree/master/patches/server-De... Also maybe remove the "4" from the title, since the name of the game is just Call of Duty Modern Warfare 3. Also, bug 41413 is a dupe of this.
https://bugs.winehq.org/show_bug.cgi?id=38322
Anthony Jagers noonetinone@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |noonetinone@gmail.com
--- Comment #10 from Anthony Jagers noonetinone@gmail.com --- I just got finished playing this. Works great!
https://bugs.winehq.org/show_bug.cgi?id=38322
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |STAGED Staged patchset| |https://github.com/wine-com | |pholio/wine-staging/tree/ma | |ster/patches/server-Debug_R | |egisters CC| |dmitry@baikal.ru, | |erich.e.hoover@wine-staging | |.com, michael@fds-team.de Ever confirmed|0 |1
https://bugs.winehq.org/show_bug.cgi?id=38322
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Call of Duty 4 Modern |Call of Duty Modern Warfare |Warfare 3: Wine crashes |3: Wine crashes when Steam |when Steam is starting the |is starting the game |game |
https://bugs.winehq.org/show_bug.cgi?id=38322
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lonnie.holcomb@gmail.com
--- Comment #11 from Sebastian Lackner sebastian@fds-team.de --- *** Bug 41413 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=38322
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |byi5000@gmail.com
--- Comment #12 from Sebastian Lackner sebastian@fds-team.de --- *** Bug 42533 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=38322
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Call of Duty Modern Warfare |Call of Duty Modern Warfare |3: Wine crashes when Steam |3 and Saints Row 3: Wine |is starting the game |crashes when Steam is | |starting the game
https://bugs.winehq.org/show_bug.cgi?id=38322
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|STAGED |RESOLVED Fixed by SHA1| |abe0b1c57bbe9a952e55d4f8210 | |73b0a5197d746
--- Comment #13 from Sebastian Lackner sebastian@fds-team.de --- This should be fixed, please retest.
https://bugs.winehq.org/show_bug.cgi?id=38322
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 2.14.
https://bugs.winehq.org/show_bug.cgi?id=38322
--- Comment #15 from Anthony Jagers noonetinone@gmail.com --- I just tested it with 2.13 (staging) and it was fine. This thread is old. Just what exactly was the problem?
https://bugs.winehq.org/show_bug.cgi?id=38322
--- Comment #16 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Anthony Jagers from comment #15)
I just tested it with 2.13 (staging) and it was fine. This thread is old. Just what exactly was the problem?
The bug was previously marked as STAGED, which means an experimental patch was already included in Wine Staging to solve or workaround this issue. Users of the development branch version were still affected by this bug until the 2.14 release.
https://bugs.winehq.org/show_bug.cgi?id=38322
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|trivial |normal Component|-unknown |wineserver CC| |focht@gmx.net Keywords| |obfuscation