wine-bugs March 2019

wine-bugs@winehq.org

1 participants
7773 discussions

[Bug 23175] New: Zak McKracken - Between Time and Space fails to play back intro video
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=23175 Summary: Zak McKracken - Between Time and Space fails to play back intro video Product: Wine Version: 1.2-rc3 Platform: x86 URL: http://www.mckracken.net/cms/die-fortsetzung/download. html OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: arethusa26(a)gmail.com Created an attachment (id=28827) --> (http://bugs.winehq.org/attachment.cgi?id=28827) Zak McKracken - Between Time and Space output After starting Zak McKracken - Between Time and Space and waiting for the loading animation to complete, an intro video is supposed to be played, but only the audio portion of the video is played back correctly, and the video is simply rendered as black for the duration. -- 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.

1 18

[Bug 45577] New: Skyrim tries to install MS VC Redist Package each launch
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45577 Bug ID: 45577 Summary: Skyrim tries to install MS VC Redist Package each launch Product: Wine Version: 3.13 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahyattdev(a)icloud.com When launched by Steam, Skyrim tries to install "Microsoft VC Redist Package" every time it is launched. This should only happen once. -- 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.

1 6

[Bug 45927] New: Tom Clancy' s TheDivision.exe terminates itself a few seconds after launch
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45927 Bug ID: 45927 Summary: Tom Clancy's TheDivision.exe terminates itself a few seconds after launch Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: m4ng4n(a)gmx.de Distribution: --- Created attachment 62454 --> https://bugs.winehq.org/attachment.cgi?id=62454 Screenshot message box TheDivision My hardware/software/setup: - AMD FX 8320 - AMD Radeon RX580 - amdgpu open-source driver - openSUSE Tumbleweed 20180926 64-bit - Kernel 4.18.8-1-default 64-bit - Mesa 18.3 with LLVM 8.0 - Plasma 5.13.5 - wine 3.17 (I also tried with 3.17-staging, the results are the same) - uplay client from Thursday, September 27th 2018, running flawlessly and starting Watch Dogs and Splinter Cell Blacklist without problems - all tests on a fresh 64-bit Wine Prefix, only corefonts installed via winetricks (needed by uplay) Hello All, when I start Tom Clancy's The Division with uplay for the first time after downloading it, the launcher installs DX and vcrun correctly and after that it starts TheDivision.exe that terminates itself immediately. At every subsequent launch with uplay or from a terminal TheDivision.exe terminates itself wihtin a few seconds after launch. No logo or window or any kind of lifesign is to be seen. The only feedback I get is when I try to start it from a terminal: /games/Ubisoft/Tom Clancy's The Division> WINEPREFIX=$HOME/.wine-division-64 WINEARCH=win64 wine TheDivision.exe 00d1:fixme:heap:RtlSetHeapInformation 0x7d0000 0 0x23e830 4 stub 00d1:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 102 00d1:err:seh:setup_exception stack overflow 1760 bytes in thread 00d1 eip 000000007bc63b8a esp 0000000000140f30 stack 0x140000-0x141000-0x240000 I tried to debug it with WINEPREFIX=$HOME/.wine-division-64 WINEARCH=win64 winedbg TheDivision.exe but all I get is a message box - titled "TheDivision.exe" - that says: "A debugger has been found running in your system. Please, unload it from memory and restart your program." After clicking that message box away I can only quit the debugger. See the attched screenshot. This is my first debugging attempt and I am pretty much lost here. So I decided to create a log file with WINEPREFIX=$HOME/.wine-division-64 WINEARCH=win64 WINEDEBUG=+relay wine TheDivision.exe as stated here, https://wiki.winehq.org/Wine_Developer%27s_Guide/Debugging_Wine#Debugging_T… and hope it is useful. I also managed to do a backtrace, once only, a couple of days ago because the exe is gone too fast to catch it. I do not know if it is of any use but will include it for further investigation. If you need any more debugging information just tell me and I will provide it. Thank you. -- 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.

1 48

[Bug 30548] New: MediaOne Plus 2.0 PhotoImpact (Ulead PhotoImpact X3) installer runs "regedit" with unsupported "/c" switch
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=30548 Bug #: 30548 Summary: MediaOne Plus 2.0 PhotoImpact (Ulead PhotoImpact X3) installer runs "regedit" with unsupported "/c" switch Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, encountered while testing Ulead PhotoImpact X3 installer ... non-fatal but of course worth to be reported/fixed. It seems related to "MediaOne Plus 2.0 PhotoImpact" package which can be optionally installed. /C = "Create and replace an existing registry from a file" WINEDEBUG=+tid,+seh,+loaddll,+process A couple of 'regedit /c foo.reg': --- snip --- trace:process:create_process_impl app (null) cmdline L"regedit.exe /c /s \"C:\\users\\focht\\Temp\\COR9595\\MsgSchedule.reg\"" ... regedit: Undefined switch /C! trace:process:create_process_impl app (null) cmdline L"regedit.exe /c /s \"C:\\users\\focht\\Temp\\COR9595\\Pages_Premium.reg\"" ... regedit: Undefined switch /C! ... --- snip --- Regards -- 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.

1 10

[Bug 44793] New: EpicGamesLauncher.exe: Fatal Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0xdaaaa600
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=44793 Bug ID: 44793 Summary: EpicGamesLauncher.exe: Fatal Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0xdaaaa600 Product: Wine-staging Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: katoflip(a)protonmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60825 --> https://bugs.winehq.org/attachment.cgi?id=60825 Data from opening EpicGamesLauncher.exe in the terminal Starting the EpicGamesLauncher.exe leads to a fatal exception, among many other errors. -- 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.

1 31

[Bug 39606] New: Infinite loop in StackWalk
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39606 Bug ID: 39606 Summary: Infinite loop in StackWalk Product: Wine Version: 1.7.54 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: ralf.habacker(a)freenet.de Distribution: --- While working on x86_64 fixes of the dbus backtrace generator for windows https://bugs.freedesktop.org/show_bug.cgi?id=92721, I recognized an infinite loop while calling StackWalk on x86_64 systems. start /home/ralf.habacker/src/dbus-2-cmake-cross-x86_64-build/bin/manual-backtrace.exe... Backtrace: 0 0xe3b17b7b in libpthread.so.0 1 wait_select_reply+0x49 [/usr/src/debug/wine-snapshot/dlls/ntdll/server.c:349] in ntdll 2 server_select+0x1f8 [/usr/src/debug/wine-snapshot/dlls/ntdll/server.c:614] in ntdll 3 wait_objects+0x7e [/usr/src/debug/wine-snapshot/dlls/ntdll/sync.c:1006] in ntdll 4 NtWaitForMultipleObjects+0x62 [/usr/src/debug/wine-snapshot/dlls/ntdll/sync.c:1017] in ntdll 5 0x7b887a8b in kernel32 6 WaitForSingleObject+0x26 [/usr/src/debug/wine-snapshot/dlls/kernel32/sync.c:127] in kernel32 7 dump_backtrace+0xa7 [/home/ralf.habacker/src/dbus-2/dbus/dbus-sysdeps-win.c:2553] in libdbus-1-3 8 _dbus_print_backtrace+0xd [/home/ralf.habacker/src/dbus-2/dbus/dbus-sysdeps-win.c:2563] in libdbus-1-3 9 test2+0x11 [/home/ralf.habacker/src/dbus-2/test/manual-backtrace.c:34] in manual-backtrace 10 test1+0xd [/home/ralf.habacker/src/dbus-2/test/manual-backtrace.c:39] in manual-backtrace 11 test+0xd [/home/ralf.habacker/src/dbus-2/test/manual-backtrace.c:44] in manual-backtrace 12 main+0x4f [/home/ralf.habacker/src/dbus-2/test/manual-backtrace.c:58] in manual-backtrace 13 0x4013ed in manual-backtrace 14 0x40152b in manual-backtrace 15 start_process+0x91 [/usr/src/debug/wine-snapshot/dlls/kernel32/process.c:1105] in kernel32 16 call_thread_func+0x6e [/usr/src/debug/wine-snapshot/dlls/ntdll/signal_x86_64.c:3675] in ntdll 17 RtlRaiseException+0x7e in ntdll 18 0xe32aa016 in ntdll 19 wine_call_on_stack+0x13 in libwine.so.1 20 wine_switch_to_stack+0x9 [/usr/src/debug/wine-snapshot/libs/wine/port.c:60] in libwine.so.1 21 LdrInitializeThunk+0x2a4 [/usr/src/debug/wine-snapshot/dlls/ntdll/loader.c:3094] in ntdll 22 __wine_kernel_init+0x941 [/usr/src/debug/wine-snapshot/dlls/kernel32/process.c:1276] in kernel32 23 __wine_process_init+0x154 [/usr/src/debug/wine-snapshot/dlls/ntdll/loader.c:3303] in ntdll 24 wine_init+0x2ce [/usr/src/debug/wine-snapshot/libs/wine/loader.c:961] in libwine.so.1 25 main+0x82 [/usr/src/debug/wine-snapshot/loader/main.c:248] in <wine-loader> 26 __libc_start_main+0xf5 in libc.so.6 27 _start+0x29 in <wine-loader> 28 _start+0x29 in <wine-loader> 29 _start+0x29 in <wine-loader> 30 _start+0x29 in <wine-loader> 31 _start+0x29 in <wine-loader> 32 _start+0x29 in <wine-loader> .... -- 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.

1 11

[Bug 17005] New: CT: Rendering issues
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=17005 Summary: CT: Rendering issues Product: Wine Version: 1.1.13 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: normandy(a)web.de I have got a modified version of Chicken Tournament. It does not crash but does not render everything. For example, trees, HUD and the radar, grass and the walls are not rendered correctly. Here's a screenshot using wine: http://tinyurl.com/8q39ec And one using windows (grass disabled): http://tinyurl.com/7tousz My console's output: http://pastebin.com/f40a0aa3 And the long one (+all) was to big (<200MB) Here you can find the modified ct1.exe, just extract this: http://tinyurl.com/8llxtp (You'll need native d3dxof.dll to load models...) Thank you! -- 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.

1 32

[Bug 46798] New: Multiple Microsoft applications need support for Antimalware Scan Interface (AMSI) 'AMSI.dll'
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46798 Bug ID: 46798 Summary: Multiple Microsoft applications need support for Antimalware Scan Interface (AMSI) 'AMSI.dll' Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track the introduction of Antimalware Scan Interface component with recent commits. Search didn't return any Wine related bug reports hence I assume it's some sekrit stuff CodeWeavers works on. My guess would be it's Microsoft Office 2016/Office 365 that has AMSI integration for VBA Macro's (VBE7.dll). Microsoft docs: https://docs.microsoft.com/en-us/windows/desktop/amsi/antimalware-scan-inte… https://www.microsoft.com/security/blog/2015/06/09/windows-10-to-offer-appl… --- quote --- Antimalware Scan Interface (AMSI) Purpose The Windows Antimalware Scan Interface (AMSI) is a versatile interface standard that allows your applications and services to integrate with any antimalware product that's present on a machine. AMSI provides enhanced malware protection for your end-users and their data, applications, and workloads. AMSI is agnostic of antimalware vendor; it's designed to allow for the most common malware scanning and protection techniques provided by today's antimalware products that can be integrated into applications. It supports a calling structure allowing for file and memory or stream scanning, content source URL/IP reputation checks, and other techniques. AMSI also supports the notion of a session so that antimalware vendors can correlate different scan requests. For instance, the different fragments of a malicious payload can be associated to reach a more informed decision, which would be much harder to reach just by looking at those fragments in isolation. Windows components that integrate with AMSI The AMSI feature is integrated into these components of Windows 10. User Account Control, or UAC (elevation of EXE, COM, MSI, or ActiveX installation) PowerShell (scripts, interactive use, and dynamic code evaluation) Windows Script Host (wscript.exe and cscript.exe) JavaScript and VBScript Office VBA macros --- quote --- Found an app that makes use of AMSI here: https://github.com/wchen-r7/amsiscanner --- quote --- AMSI Scanner A C/C++ implementation of Microsoft's Antimalware Scan Interface. --- quote --- --- snip --- $ wine ./amsiscanner.exe amsiscanner.exe 0009:fixme:amsi:AmsiInitialize L"\794d\6d41\6973\6353\6e61\656er", 0x33fdd4 0009:fixme:amsi:AmsiOpenSession 0xdeadbeef, 0x33fdd0 0009:fixme:amsi:AmsiScanBuffer 0xdeadbeef, 0x340000, 178688, L"\6d61\6973\6373\6e61\656e\2e72\7865er.\0188", 0xdeadbeef, 0x33fdcc 0009:fixme:amsi:AmsiUninitialize 0xdeadbeef Sample size: 178688 bytes Risk level = 1 (No threat detected) --- snip --- $ sha1sum amsiscanner.exe 257626250fd91de2f853758c3cccc8e5f5830113 amsiscanner.exe $ du -sh amsiscanner.exe 176K amsiscanner.exe $ wine --version wine-4.3-188-gab7756619c 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.

1 2

[Bug 37585] New: 64-bit Google Chrome 38.x crashes (core dlls must be prelinked at fixed addresses)
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=37585 Bug ID: 37585 Summary: 64-bit Google Chrome 38.x crashes (core dlls must be prelinked at fixed addresses) Product: Wine Version: 1.7.31 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as 64-bit Google Chrome has finally been released I thought to give it a try. Only useful for improving Wine 64-bit compatibility, not really meant to be used seriously since native port exists. --- snip --- $ pwd /home/focht/wineprefix64/drive_c/Program Files (x86)/Google/Chrome/Application $ file chrome.exe chrome.exe: PE32+ executable (GUI) x86-64, for MS Windows $ WINEDEBUG=+tid,+seh,+relay,+server,+virtual,+module wine64 ./chrome.exe >>log.txt 2>&1 ... 003f:Call advapi32.CreateProcessAsUserW(000002f8,05fad480 L"C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",0011f680 L"\"C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-deferred-image-decoding --lang=en-US --force-fieldtrials=Prerender/PrerenderEnabled/UMA-New-Install-Uniformity-Trial/Control/UMA-Session-Randomized-Uniformity-Trial-5-Percent/default/UMA-Uniformity-Trial-1-P"...,00000000,00000000,00000000,383330300100040c,00000000,00000000,05bbc4d0,05bbbe98) ret=14003e6bb ... 003f: new_process() = 0 { info=0308, pid=0051, phandle=030c, tid=0052, thandle=0310 } 003f: select( flags=2, cookie=05bbadb4, timeout=infinite, prev_apc=0000, result={}, data={WAIT,handles={0308}} ) 003f: select() = PENDING { timeout=infinite, call={APC_NONE}, apc_handle=0000 } 003f: *wakeup* signaled=0 003f: get_new_process_info( info=0308 ) 003f: get_new_process_info() = 0 { success=1, exit_code=259 } 003f: close_handle( handle=0308 ) 003f: close_handle() = 0 003f: close_handle( handle=0304 ) 003f: close_handle() = 0 003f:Ret advapi32.CreateProcessAsUserW() retval=00000001 ret=14003e6bb ... 003f:Call KERNEL32.VirtualAllocEx(0000030c,00000000,0000006c,00001000,00000004) ret=1400443eb 003f:trace:virtual:NtAllocateVirtualMemory 0x30c (nil) 0000006c 1000 00000004 003f: queue_apc( handle=030c, call={APC_VIRTUAL_ALLOC,addr==00000000,size=0000006c,zero_bits=0,op_type=1000,prot=4} ) 003f: queue_apc() = 0 { handle=0304, self=0 } 003f: select( flags=2, cookie=05bbbc14, timeout=infinite, prev_apc=0000, result={}, data={WAIT_ALL,handles={0304}} ) 003f: select() = PENDING { timeout=infinite, call={APC_NONE}, apc_handle=0000 } 003f: *wakeup* signaled=0 003f: get_apc_result( handle=0304 ) 003f: get_apc_result() = 0 { result={APC_VIRTUAL_ALLOC,status=0,addr=00240000,size=00001000} } 003f:Ret KERNEL32.VirtualAllocEx() retval=00240000 ret=1400443eb 003f:Call KERNEL32.WriteProcessMemory(0000030c,00240000,00113070,0000006c,05bbc350) ret=14004440f 003f: write_process_memory( handle=030c, addr=00240000, data={01,00,00,00,00,00,00,00,00,00,00,00,60,00,00,00,00,00,00,00,30,00,00,00,00,00,00,00,01,00,00,00,00,33,6b,00,65,00,72,00,6e,00,65,00,6c,00,33,00,32,00,2e,00,64,00,6c,00,6c,00,00,00,30,00,00,00,00,00,00,00,02,00,00,00,0e,00,00,00,78,e0,04,40,01,00,00,00,43,72,65,61,74,65,4e,61,6d,65,64,50,69,70,65,57,00,00,00,00,01,00,11,00} ) 003f: write_process_memory() = 0 003f:Ret KERNEL32.WriteProcessMemory() retval=00000001 ret=14004440f .... 003f:Call KERNEL32.VirtualAllocEx(0000030c,0025c000,00001000,00001000,100000040) ret=140044b18 003f:trace:virtual:NtAllocateVirtualMemory 0x30c 0x25c000 00001000 1000 00000040 003f: queue_apc( handle=030c, call={APC_VIRTUAL_ALLOC,addr==0025c000,size=00001000,zero_bits=0,op_type=1000,prot=40} ) 003f: queue_apc() = 0 { handle=0304, self=0 } 003f: select( flags=2, cookie=05bbbb94, timeout=infinite, prev_apc=0000, result={}, data={WAIT_ALL,handles={0304}} ) 003f: select() = PENDING { timeout=infinite, call={APC_NONE}, apc_handle=0000 } 003f: *wakeup* signaled=0 003f: get_apc_result( handle=0304 ) 003f: get_apc_result() = 0 { result={APC_VIRTUAL_ALLOC,status=0,addr=0025c000,size=00001000} } 003f:Ret KERNEL32.VirtualAllocEx() retval=0025c000 ret=140044b18 003f:Call KERNEL32.GetModuleHandleW(14007d2b0 L"ntdll.dll") ret=1400447aa 003f:trace:module:LdrGetDllHandle L"ntdll.dll" -> 0x7fa7c6270000 (load path L"C:\\Program Files (x86)\\Google\\Chrome\\Application;.;C:\\windows\\system32;C:\\windows\\system;C:\\windows;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem") 003f:Ret KERNEL32.GetModuleHandleW() retval=7fa7c6270000 ret=1400447aa 003f:Call KERNEL32.GetModuleHandleExW(00000006,7fa7c6273fe0,05bbc0e0) ret=1400447f5 003f:Ret KERNEL32.GetModuleHandleExW() retval=00000001 ret=1400447f5 ... 003f:Call KERNEL32.ReadProcessMemory(0000030c,7fa7c627462c,05bbc010,00000020,05bbc040) ret=14004e728 003f: read_process_memory( handle=030c, addr=7fa7c627462c ) 003f: read_process_memory() = ACCESS_VIOLATION { data={} } 003f:Ret KERNEL32.ReadProcessMemory() retval=00000000 ret=14004e728 ... 003f:Call KERNEL32.GetLastError() ret=14003bb29 003f:Ret KERNEL32.GetLastError() retval=000003e6 ret=14003bb29 003f:Call KERNEL32.TerminateProcess(0000030c,00000000) ret=14003eafd 003f: terminate_process( handle=030c, exit_code=0 ) 003f: terminate_process() = 0 { self=0 } 003f:Ret KERNEL32.TerminateProcess() retval=00000001 ret=14003eafd 003f:Call KERNEL32.WaitForSingleObject(0000030c,00000032) ret=14003e406 003f: select( flags=2, cookie=05bbbdc4, timeout=+0.0500000, prev_apc=0000, result={}, data={WAIT,handles={030c}} ) 003f: select() = 0 { timeout=1d0037eb30ca43e (+0.0500000), call={APC_NONE}, apc_handle=0000 } 003f:Ret KERNEL32.WaitForSingleObject() retval=00000000 ret=14003e406 003f:Call KERNEL32.GetExitCodeProcess(0000030c,05bbc3d0) ret=14003e414 003f: get_process_info( handle=030c ) 003f: get_process_info() = 0 { pid=0051, ppid=0008, affinity=0000000f, peb=7fffff7ef000, start_time=1d0037eb2fe710c (-0.0431540), end_time=1d0037eb304b832 (-0.0020110), exit_code=0, priority=2, cpu=x86_64, debugger_present=0 } 003f:Ret KERNEL32.GetExitCodeProcess() retval=00000001 ret=14003e414 ... 003f:trace:seh:raise_exception code=80000003 flags=0 addr=0x14001d86d ip=14001d86d tid=003f 003f:trace:seh:raise_exception rax=0000000000000000 rbx=00000001400a3f88 rcx=0000000005bbeb1f rdx=0000000005bbeae0 003f:trace:seh:raise_exception rsi=0000000000110980 rdi=000000000000dead rbp=0000000005bbc500 rsp=0000000005bbc3d0 003f:trace:seh:raise_exception r8=0000003071e48cfd r9=000000000000001e r10=0000000000000000 r11=0000003071f811c0 003f:trace:seh:raise_exception r12=0000000000101160 r13=0000000000101140 r14=0000000000075680 r15=000000000000dead --- snip --- Child process address space for 64-bit 'ntdll.dll': --- snip --- 0054:trace:module:load_dll looking for L"ntdll.dll" in L"C:\\Program Files (x86)\\Google\\Chrome\\Application;.;C:\\windows\\system32;C:\\windows\\system;C:\\windows;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem" 0054:trace:module:load_dll Found L"C:\\windows\\system32\\ntdll.dll" for L"ntdll.dll" at 0x7f3184050000, count=3 0054:trace:virtual:NtProtectVirtualMemory 0xffffffffffffffff 0x7f317d8f9bc0 000002d0 00000004 0054:trace:virtual:VIRTUAL_SetProt 0x7f317d8f9000-0x7f317d8f9fff c-rW- 0054:trace:virtual:VIRTUAL_DumpView View: 0x7f317d680000 - 0x7f317d8fbfff (system) 0054:trace:virtual:VIRTUAL_DumpView 0x7f317d680000 - 0x7f317d680fff c-r-- 0054:trace:virtual:VIRTUAL_DumpView 0x7f317d681000 - 0x7f317d8f4fff c-r-x 0054:trace:virtual:VIRTUAL_DumpView 0x7f317d8f5000 - 0x7f317d8f8fff c-rw- 0054:trace:virtual:VIRTUAL_DumpView 0x7f317d8f9000 - 0x7f317d8f9fff c-rW- 0054:trace:virtual:VIRTUAL_DumpView 0x7f317d8fa000 - 0x7f317d8fbfff c-rw- --- snip --- App sandboxing scheme at work, setting up intermediate trampoline code in the child and then patch out the API entries. Unfortunately the code relies on 64-bit Windows core dlls being mapped at the same (fixed) locations across processes hence it fails here, triggering abort in the parent. Probably same rationale applies here as for 32-bit Windows core dlls. $ sha1sum googlechromestandaloneenterprise64.msi 586f91c05925e22fd5f891aa3e99e1cb9762950a googlechromestandaloneenterprise64.msi $ du -sh googlechromestandaloneenterprise64.msi 47M googlechromestandaloneenterprise64.msi $ wine --version wine-1.7.31-47-g516ed8e 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.

1 21

[Bug 46783] New: Metro Exodus crash on start [DXGI]
by wine-bugs＠winehq.org 15 Mar '19

15 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46783 Bug ID: 46783 Summary: Metro Exodus crash on start [DXGI] Product: Wine Version: 4.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: timofeevsv1989(a)gmail.com Distribution: --- Some DXGI function unimplemented. 003b:fixme:dxgi:dxgi_output_FindClosestMatchingMode1 iface 0x34e5880, mode 0x54de30, closest_match 0x54de50, device (nil) stub! -- 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.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2019