[Bug 37200] New: Warhammer 40k: Kill Team (Steam version) does not start
https://bugs.winehq.org/show_bug.cgi?id=37200 Bug ID: 37200 Summary: Warhammer 40k: Kill Team (Steam version) does not start Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zentarim(a)rambler.ru A game Warhammer 40,000: Kill Team http://store.steampowered.com/app/275610/ does not start. Console log in attachement. OS: Ubuntu 14.04.1 LTS, Trusty Tahr Wine: 1.7.25 What other information should I have to provide? -- 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=37200 hanska2(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hanska2(a)luukku.com --- Comment #1 from hanska2(a)luukku.com --- Did you forget the attachment? -- 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=37200 --- Comment #2 from Zentarim <zentarim(a)rambler.ru> --- Created attachment 49454 --> https://bugs.winehq.org/attachment.cgi?id=49454 error.log woops... -- 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=37200 --- Comment #3 from Zentarim <zentarim(a)rambler.ru> --- I need to provide more information? Thanks in advance. -- 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=37200 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://store.steampowered.c | |om/app/275610/ CC| |focht(a)gmx.net --- Comment #4 from Anastasius Focht <focht(a)gmx.net> --- Hello Zentarim, your console output shows a crash: --- snip --- wine: Unhandled page fault on write access to 0x00000000 at address 0x110025 (thread 0051), starting debugger... --- snip --- Unfortunately that information has not enough context. Can you run the game as follows (make sure no process - including Steam client - runs prior from that WINEPREFIX -> 'wineserver -k'): --- snip --- $ WINEDEBUG=+tid,+seh,+loaddll,+process,+debugstr wine ./steam.exe -applaunch 275610 -nominidumps -nobreakpad -noassert -nocrashdialog >>log.txt 2>&1 --- snip --- I looked up the game 'appid' from Steamdb - please correct if necessary ('-applaunch <appid>'). If a crash reporting tool appears, please save the report too (and exit the tool). After that, kill off any remaining processes -> 'wineserver -k' Attach the logs here. Thanks. 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=37200 --- Comment #5 from Zentarim <zentarim(a)rambler.ru> --- Created attachment 49473 --> https://bugs.winehq.org/attachment.cgi?id=49473 Error log SteamID is correct. log obtained after executing the command: env WINEPREFIX=/mnt/games/wine_killteam WINEDEBUG=+tid,+seh,+loaddll,+process,+debugstr wine gdb ./steam.exe -applaunch 275610 -nominidumps -nobreakpad -noassert -nocrashdialog >>log.txt 2>&1 Can you recommend the name of the debugger with which I could get a trace? Thanks in advance. -- 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=37200 --- Comment #6 from Anastasius Focht <focht(a)gmx.net> --- Hello Zentarim, thanks for the trace. --- quote --- Can you recommend the name of the debugger with which I could get a trace? --- quote --- 'winedbg' as registered just-in-time debugger/crash handler should be fine in most cases. Unfortunately another exception happens during fault handling which prevents 'winedbg' from being started here. --- snip --- ... 0043:trace:process:create_process_impl app L"C:\\Program Files\\Steam\\steamapps\\common\\W40K Kill Team\\killteam.exe" cmdline L"\"C:\\Program Files\\Steam\\steamapps\\common\\W40K Kill Team\\killteam.exe\" -nominidumps -nobreakpad -noassert -nocrashdialog" ... 0043:trace:process:create_process_impl started process pid 0054 tid 0055 ... 0055:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x3bde078, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x33f400, desc (nil) partial stub! 0055:trace:seh:raise_exception code=c0000005 flags=0 addr=0x110025 ip=00110025 tid=0055 0055:trace:seh:raise_exception info[0]=00000001 0055:trace:seh:raise_exception info[1]=00000000 0055:trace:seh:raise_exception eax=03bdae51 ebx=7dda9000 ecx=00000000 edx=03be10b0 esi=03bde078 edi=00000000 0055:trace:seh:raise_exception ebp=0033f3c8 esp=0033f34c cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210202 0055:trace:seh:call_stack_handlers calling handler at 0xc7d2e0 code=c0000005 flags=0 0055:trace:seh:call_stack_handlers handler at 0xc7d2e0 returned 1 0055:trace:seh:call_stack_handlers calling handler at 0xa743d8 code=c0000005 flags=0 ... wine: Unhandled page fault on write access to 0x00000000 at address 0x110025 (thread 0055), starting debugger... 0055:trace:seh:start_debugger Starting debugger "winedbg --auto 84 568" 0055:trace:process:create_process_impl app (null) cmdline L"winedbg --auto 84 568" 0055:trace:process:find_exe_file looking for L"winedbg" 0055:trace:process:find_exe_file Trying native exe L"C:\\windows\\system32\\winedbg.exe" 0055:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc5099b ip=7bc5099b tid=0055 0055:trace:seh:raise_exception info[0]=00000001 0055:trace:seh:raise_exception info[1]=00000004 0055:trace:seh:raise_exception eax=00000000 ebx=7bcc7000 ecx=03be10e8 edx=03bdc360 esi=00000002 edi=000029a0 0055:trace:seh:raise_exception ebp=0033e5f8 esp=0033e440 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210206 0055:trace:seh:call_stack_handlers calling handler at 0x7bc80220 code=c0000005 flags=0 ... 0055:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc5099b 0043:warn:debugstr:OutputDebugStringA "Game removed: AppID 275610 \"Warhammer 40,000: Kill Team\", ProcID 84 \n" --- snip --- You could try to run a few times without trace log (WINEDEBUG) but with the proposed arguments, maybe the debugger can still attach upon first exception. In that case save it to 'backtrace.txt'. --- snip --- WINEDEBUG=+tid,+seh,+loaddll,+process,+debugstr wine gdb ./steam.exe --- snip --- You probably meant 'winedbg' here. Anyway, debugging Steam games is not for the faint-hearted. I wouldn't recommend it unless you have the experience. You either attach at the right point to the child or you need to go the way with parent being debuggee and 'set $AlsoDebugProcChild=1' (which can be very annoying/confusing if multiple child processes are spawned). 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=37200 --- Comment #7 from Zentarim <zentarim(a)rambler.ru> --- Sorry, I sent you the wrong command Right command: env WINEPREFIX=/mnt/games/wine_killteam WINEDEBUG=+tid,+seh,+loaddll,+process,+debugstr wine ./steam.exe -applaunch 275610 -nominidumps -nobreakpad -noassert -nocrashdialog >>log.txt 2>&1 You're right, I did not really work with the debugger. But if it is necessary to provide the findings of several simple commands, then i was ready to try -- 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=37200 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte(a)systemsaviour.com --- Comment #8 from Adam Bolte <abolte(a)systemsaviour.com> --- Created attachment 50362 --> https://bugs.winehq.org/attachment.cgi?id=50362 Requested log with execution on Wine 1.7.33 -- 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=37200 --- Comment #9 from Adam Bolte <abolte(a)systemsaviour.com> --- Created attachment 50363 --> https://bugs.winehq.org/attachment.cgi?id=50363 Requested crash report backtrace with execution on Wine 1.7.33 -- 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=37200 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #10 from super_man(a)post.com --- I think there is clear crash location one of the logs Backtrace: =>0 0x7dd9c815 dxgi_swapchain_SetFullscreenState+0x15() in dxgi (0x0033f8c8) 169 static HRESULT STDMETHODCALLTYPE dxgi_swapchain_SetFullscreenState(IDXGISwapChain *iface, 170 BOOL fullscreen, IDXGIOutput *target) 171 { 172 FIXME("iface %p, fullscreen %u, target %p stub!\n", iface, fullscreen, target); 173 174 return E_NOTIMPL; 175 } Maybe it doesn't like the return call. -- 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=37200 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #50362|0 |1 is obsolete| | --- Comment #11 from Adam Bolte <abolte(a)systemsaviour.com> --- Created attachment 52582 --> https://bugs.winehq.org/attachment.cgi?id=52582 Requested execution log on Wine 1.7.53 Clean 32-bit wine prefix created with 1.7.53. -- 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=37200 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #50363|0 |1 is obsolete| | --- Comment #12 from Adam Bolte <abolte(a)systemsaviour.com> --- Created attachment 52583 --> https://bugs.winehq.org/attachment.cgi?id=52583 Requested crash report backtrace on Wine 1.7.53 -- 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=37200 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Assignee|wine-bugs(a)winehq.org |joseph.kucia(a)gmail.com Ever confirmed|0 |1 --- Comment #13 from Józef Kucia <joseph.kucia(a)gmail.com> --- Created attachment 52597 --> https://bugs.winehq.org/attachment.cgi?id=52597 Patch This patch fixes the crash in dxgi_swapchain_SetFullscreenState(). -- 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=37200 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Component|-unknown |directx-d3d Assignee|joseph.kucia(a)gmail.com |wine-bugs(a)winehq.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=37200 --- Comment #14 from super_man(a)post.com --- Backtrace: =>0 0x7dcf4482 d3d10_device_CreateDepthStencilView+0x Another clear crash location. Have you tried disabling dx10/11 ? -- 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=37200 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia(a)gmail.com --- Comment #15 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to super_man from comment #14)
Backtrace: =>0 0x7dcf4482 d3d10_device_CreateDepthStencilView+0x
This crash is caused by unsupported WINED3DFMT_R24G8_TYPELESS. -- 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=37200 --- Comment #16 from super_man(a)post.com --- (In reply to Józef Kucia from comment #15)
(In reply to super_man from comment #14)
Backtrace: =>0 0x7dcf4482 d3d10_device_CreateDepthStencilView+0x
This crash is caused by unsupported WINED3DFMT_R24G8_TYPELESS.
That is bug 22762 then. Great to know. -- 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=37200 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |e79bf35933439800bd13b55c0cf | |7cc7505c05564 Status|NEW |RESOLVED CC| |leslie_alistair(a)hotmail.com Resolution|--- |FIXED --- Comment #17 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- http://source.winehq.org/git/wine.git/?a=commit;h=e79bf35933439800bd13b55c0c... -- 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=37200 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #18 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.8-rc1. -- 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