https://bugs.winehq.org/show_bug.cgi?id=43763
Bug ID: 43763 Summary: Warlords Battlecry II crashes on load map Product: Wine Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: 9xzsnuwq9h@snkmail.com Distribution: ---
Created attachment 59263 --> https://bugs.winehq.org/attachment.cgi?id=59263 wine log with back trace
Fresh install of dev-Version, deleted previous .wine directory. Did not install Mono or Gecko. Installed wb2.
Started program. Chose Skirmish. Created new Hero. Configured an AI opponent (and small retinue points for testing, optional) and started. Selected retinue (optional). Next step is loading the map -> Crash (see attached log).
First line logged line after loading starts is:
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1600x1200x16 @0! (XRandR 1.2)
... 0 FPS is at least a weird setting. But this has probably not much to do with the following:
wine: Unhandled page fault on read access to 0x00000000 at address 0x7bc50f90 (thread 0038), starting debugger...
Tested on different system and wine configurations. Same on 32Bit, 1.6.2-0ubuntu4 and winehq-stable.
https://bugs.winehq.org/show_bug.cgi?id=43763
9xzsnuwq9h@snkmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |9xzsnuwq9h@snkmail.com
https://bugs.winehq.org/show_bug.cgi?id=43763
9xzsnuwq9h@snkmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=43763
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de Severity|blocker |normal
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Not a blocker.
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #2 from 9xzsnuwq9h@snkmail.com --- Sorry, of course severities here are meant in regard to wine releases, not for single applications ... did lose sight of that.
https://bugs.winehq.org/show_bug.cgi?id=43763
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #3 from joaopa jeremielapuree@yahoo.fr --- Looks like it would bee a good idea to install debug symbols.
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #4 from 9xzsnuwq9h@snkmail.com --- I am happy to provide more information, but I need starting points - what does debug symbols mean? I could only find this in faq 10.1.2:
WINEDEBUG=+relay,+seh,+tid wine your_program.exe >> /tmp/output.txt 2>&1
... you mean this, right?:
https://wiki.ubuntu.com/Debug%20Symbol%20Packages
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #5 from 9xzsnuwq9h@snkmail.com --- oh, it seems there are ready made packages for this:
wine-devel-dbg Version: 2.17.0~trusty
... but do I need to give wine parameters to use this? Attaching a new log after installation, but I fail to see much difference.
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #6 from 9xzsnuwq9h@snkmail.com --- Created attachment 59288 --> https://bugs.winehq.org/attachment.cgi?id=59288 wine log after installation of wine-devel-dbg
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #7 from 9xzsnuwq9h@snkmail.com --- Created attachment 59302 --> https://bugs.winehq.org/attachment.cgi?id=59302 crash log transferred from initial test report (wine 1.6.2)
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #8 from 9xzsnuwq9h@snkmail.com --- This exact bug was not reproduceable with the GOG version, only with the original CD. I guess nowadays this looses more and more importance, thus I would shift (lacking) attention away from it. -> won't fix?
https://bugs.winehq.org/show_bug.cgi?id=43763
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #9 from winetest@luukku.com --- I think the crash on first log is because the game cant set the video mode it wants.
https://bugs.winehq.org/show_bug.cgi?id=43763
--- Comment #10 from 9xzsnuwq9h@snkmail.com --- Yes, you were right (obviously). Even with the Gog Version, this can be reproduced by changing he in game screen resolution from 1048 to 1600 for me. Thought I checked this extensively, but I might have missed a relevant combination.
So, not a showstopper, but I'd like to keep this open until I looked into possible workarounds.