[Bug 38531] New: Battlefield 1942 - Crashes after selecting spawn point in local game
https://bugs.winehq.org/show_bug.cgi?id=38531 Bug ID: 38531 Summary: Battlefield 1942 - Crashes after selecting spawn point in local game Product: Wine Version: 1.7.42 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 51400 --> https://bugs.winehq.org/attachment.cgi?id=51400 Console output from Slackware 14.1 with wine 1.7.42 Hello everyone, I have been trying to get the "Battlefield 1942" demo to work. It starts up okay but after creating a local LAN game I can get to choose a "spawn point" and when I want to start the game it crashes. The AppDB entry can be found at the following link: https://appdb.winehq.org/objectManager.php?sClass=version&iId=6669 Have a good week! -- 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=38531 Maik Wagner <maiktapwagner(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://battlefield2.filefro | |nt.com/files/Battlefield_19 | |42/Official_Releases/Demo;1 | |077 CC| |maiktapwagner(a)aol.com Distribution|--- |Slackware -- 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=38531 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Maik Wagner from comment #0)
Created attachment 51400 [details] Console output from Slackware 14.1 with wine 1.7.42
It is probably not related to the issue, but I've noticed this in a couple of your other bug reports already: all your logs contain "preloader: Warning: failed to reserve range 00010000-00110000", which means that Wine will not be able to use the default memory layout. Usually modern apps should be able to deal with that, but especially for older applications it might cause problems. I would recommend to fix that issue and then retest your applications. The following forum post might probably help http://www.linuxquestions.org/questions/slackware-14/dos-support-unavailable.... -- 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=38531 --- Comment #2 from Maik Wagner <maiktapwagner(a)aol.com> --- Hello Sebastian, thanks for the heads up. I made the changes as suggested in the forum and I think I isolated the problem. The crash occurs when clicking on the "Done" button in a local multiplayer game and the timer before the game starts runs out. This is the console output that occurs then: ^[^[^[ fixme:d3d8:d3d8_device_GetPaletteEntries iface 0x138398, palette_idx 0, entries 0x33e0cc unimplemented. fixme:thread:NtQueryInformationThread Cannot get kerneltime or usertime of other threads -- 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=38531 --- Comment #3 from Jeff Zaroyko <jeffz(a)jeffz.name> --- I've tested with the full version (1.6 + gamespy update) on wine-1.7.46 on OSX 10.9.5. All works fine here. Local game, multiplayer, no crashes. -- 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=38531 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #4 from super_man(a)post.com --- Another dead download. Reported once to be working. -- 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=38531 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #5 from joaopa <jeremielapuree(a)yahoo.fr> --- Can anyone confirm the bug is fixed with wine-4.7? -- 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=38531 Jeff Zaroyko <jeffz(a)jeffz.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED --- Comment #6 from Jeff Zaroyko <jeffz(a)jeffz.name> --- (In reply to joaopa from comment #5)
Can anyone confirm the bug is fixed with wine-4.7?
I was never able to reproduce it. I've tested various new wine releases each year. I just retested with wine-4.7 and still see no problem. Resolving abandoned. -- 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=38531 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv(a)dawncrow.de --- Comment #7 from André H. <nerv(a)dawncrow.de> --- closing abandoned -- 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