March 2021 - Wine-bugs - list.winehq.org

[Bug 49436] New: 64-bit Diablo III hangs on startup since 5.11
by WineHQ Bugzilla 12 May '21

12 May '21

https://bugs.winehq.org/show_bug.cgi?id=49436 Bug ID: 49436 Summary: 64-bit Diablo III hangs on startup since 5.11 Product: Wine Version: 5.11 Hardware: x86-64 URL: https://www.blizzard.com/en-gb/download/confirmation?p roduct=d3 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maciej.stanczew+b(a)gmail.com Regression SHA1: e561ce4b9259071f79d219dddf62f05cdd8dd07b Distribution: ArchLinux Created attachment 67524 --> https://bugs.winehq.org/attachment.cgi?id=67524 64-bit client on Staging 5.11 After updating to Staging 5.11, 64-bit Diablo III client hangs after starting, with message: 00d8:err:seh:setup_exception stack overflow 1920 bytes in thread 00d8 eip 00000001402fed5b esp 0000000000c10e90 stack 0xc10000-0xc11000-0xd10000 32-bit client launches correctly. I'm not able to test vanilla Wine, because the game doesn't work there due to bug #45443. Regression testing lead me to the very first commit after 5.10 release: commit e561ce4b9259071f79d219dddf62f05cdd8dd07b Author: Alexandre Julliard <julliard(a)winehq.org> Date: Sat Jun 6 13:56:19 2020 +0200 ntdll: Move NtRaiseException() implementation to the Unix library. The two final configurations I built were: - good: Wine 3cc3b44575, Staging 044cb930, patch ntdll-NtContinue excluded - bad: Wine e561ce4b92, Staging 044cb930, patch ntdll-NtContinue excluded, incremented NTDLL_UNIXLIB_VERSION to allow staging patches to apply ntdll-NtContinue had to be excluded because it conflicts with ntdll changes in Wine (it was removed from Staging in the following rebase). But as we can see, even with it being excluded from 5.10 (without e561ce4b92), the game runs. -- 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 47

[Bug 45349] New: Multiple applications and games crash due to missing support for 64-bit syscall thunks (StreetFighter V)
by wine-bugs＠winehq.org 12 May '21

12 May '21

https://bugs.winehq.org/show_bug.cgi?id=45349 Bug ID: 45349 Summary: Multiple applications and games crash due to missing support for 64-bit syscall thunks (StreetFighter V) Product: Wine Version: 3.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, had this one lying around for some time, sadly got distracted from further analysis (there are more bugs). The game is "StreetFighter V Arcade Edition" and was gifted to me by Valve for investigation, thanks ;-) https://store.steampowered.com/app/310950/Street_Fighter_V_Arcade_Edition/ It has some custom DRM/protection scheme which uses various 64-bit anti-debug and obfuscation techniques. There are a lot of single-step (TF) exceptions in the code which are there by design (decrypt continuations). At one point it crashes with invalid instruction exception: --- snip --- ... 002e:trace:seh:NtRaiseException code=80000004 flags=0 addr=0x143fc99e9 ip=143fc99e9 tid=002e 002e:trace:seh:NtRaiseException rax=00000000006000aa rbx=000000000000005e rcx=000000000000005f rdx=000000000000071c 002e:trace:seh:NtRaiseException rsi=0000000143fcf826 rdi=0000000000000000 rbp=00000000005ffbd8 rsp=00000000005ffbd0 002e:trace:seh:NtRaiseException r8=0000000143fd2240 r9=000000000000000c r10=0000000143fd26f8 r11=0000000000000000 002e:trace:seh:NtRaiseException r12=000000000000005f r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 002e:trace:seh:RtlVirtualUnwind type 1 rip 143fc99e9 rsp 5ffbd0 002e:trace:seh:dump_unwind_info **** func 3fc9980-3fca910 002e:trace:seh:dump_unwind_info unwind info at 0x143fd26f0 flags 1 prolog 0x0 bytes function 0x143fc9980-0x143fca910 002e:trace:seh:dump_unwind_info handler 0x143fd2240 data at 0x143fd26f8 002e:trace:seh:call_handler calling handler 0x143fd2240 (rec=0x5ffa90, frame=0x5ffbd0 context=0x5fed30, dispatch=0x5ff200) 002e:trace:seh:call_handler handler at 0x143fd2240 returned 0 002e:trace:module:LdrGetDllHandle L"Kernel32.dll" -> 0x7b460000 (load path L"Z:\\home\\focht\\Downloads;C:\\windows\\system32;C:\\windows\\system;C:\\windows;.;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem") 002e:trace:ntdll:NtQueryInformationProcess (0xffffffffffffffff,0x00000007,0x5ffcb0,0x00000008,0x5ffcb0) 002e: get_process_info( handle=ffffffff ) 002e: get_process_info() = 0 { pid=002d, ppid=0000, affinity=000000ff, peb=7fffffeaf000, start_time=1d3e17d69097156 (-0.0309210), end_time=0, exit_code=259, priority=2, cpu=x86_64, debugger_present=0, debug_children=1 } 002e:trace:module:LdrGetDllHandle L"Kernel32.dll" -> 0x7b460000 (load path L"Z:\\home\\focht\\Downloads;C:\\windows\\system32;C:\\windows\\system;C:\\windows;.;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem") 002e:trace:seh:NtRaiseException code=c0000096 flags=0 addr=0x143fca968 ip=143fca968 tid=002e 002e:trace:seh:NtRaiseException rax=00000000564d5868 rbx=000000008685d465 rcx=000000000000000a rdx=0000000143fc5658 002e:trace:seh:NtRaiseException rsi=00000000005ffd58 rdi=0000000143fd3344 rbp=00000000005ffc18 rsp=00000000005ffc08 002e:trace:seh:NtRaiseException r8=0000000143fd26f8 r9=000000000000000c r10=0000000143fd26f8 r11=0000000000000000 002e:trace:seh:NtRaiseException r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 002e:trace:seh:RtlVirtualUnwind type 1 rip 143fca968 rsp 5ffc08 002e:trace:seh:dump_unwind_info **** func 3fca910-3fcfbbc 002e:trace:seh:dump_unwind_info unwind info at 0x143fd26f0 flags 1 prolog 0x0 bytes function 0x143fca910-0x143fcfbbc 002e:trace:seh:dump_unwind_info handler 0x143fcbbe8 data at 0x143fd26f8 002e:trace:seh:call_handler calling handler 0x143fcbbe8 (rec=0x5ffac0, frame=0x5ffc08 context=0x5fed60, dispatch=0x5ff230) 002e:trace:seh:call_handler handler at 0x143fcbbe8 returned 0 ... --- snip --- One has to debug it to see the mess. For that you need to defeat a few anti-debug trickery ;-) The game protection copies native API entry point code around and assumes 64-bit Windows API entries which have a distinct signature/sequence. A similar problem is described in bug 21232 which is about 32-bit syscall thunks. Partial copy of 'ntdll.NtQueryInformationProcess' entry point: --- snip --- 0000000143FCFA88 | 55 | push rbp 0000000143FCFA89 | 48 89 E5 | mov rbp, rsp 0000000143FCFA8C | 57 | push rdi 0000000143FCFA8D | 56 | push rsi 0000000143FCFA8E | 48 81 EC A0 00 00 00 | sub rsp, A0 0000000143FCFA95 | 48 83 E4 F0 | and rsp, FFFFFFFFFFFFFFF0 0000000143FCFA99 | 48 81 EC 40 03 00 00 | sub rsp, 340 0000000143FCFAA0 | 0F 11 B5 50 FF FF FF | movups xmmword ptr ss:[rbp - B0], xmm6 0000000143FCFAA7 | 0F C4 08 33 | pinsrw mm1, word ptr ds:[rax], 33 0000000143FCFAAB | C0 48 83 C4 | ror byte ptr ds:[rax - 7D], C4 0000000143FCFAAF | 28 C3 | sub bl, al 0000000143FCFAB1 | CC | int3 0000000143FCFAB2 | CC | int3 0000000143FCFAB3 | CC | int3 0000000143FCFAB4 | CC | int3 0000000143FCFAB5 | CC | int3 0000000143FCFAB6 | CC | int3 0000000143FCFAB7 | CC | int3 0000000143FCFAB8 | 48 89 5C 24 08 | mov qword ptr ss:[rsp + 8], rbx 0000000143FCFABD | 48 89 6C 24 10 | mov qword ptr ss:[rsp + 10], rbp 0000000143FCFAC2 | 48 89 74 24 18 | mov qword ptr ss:[rsp + 18], rsi 0000000143FCFAC7 | 57 | push rdi 0000000143FCFAC8 | 48 83 EC 30 | sub rsp, 30 0000000143FCFACC | 41 8B D9 | mov ebx, r9d 0000000143FCFACF | 49 8B F0 | mov rsi, r8 0000000143FCFAD2 | 8B EA | mov ebp, edx 0000000143FCFAD4 | 48 8B F9 | mov rdi, rcx 0000000143FCFAD7 | EB 02 | jmp streetfighterv.143FCFADB 0000000143FCFAD9 | 48 EB E8 | jmp streetfighterv.143FCFAC4 --- snip --- This obviously can't work. On 64-bit Windows the native API entry code is much smaller (< 16 bytes). Due to partial opcode copy a fault is triggered when executing. Original 64-bit Wine API entry code: --- snip --- 000000007BCEF058 55 push rbp 000000007BCEF059 48 89 E5 mov rbp, rsp 000000007BCEF05C 57 push rdi 000000007BCEF05D 56 push rsi 000000007BCEF05E 48 81 EC A0 00 00 00 sub rsp, 0A0h 000000007BCEF065 48 83 E4 F0 and rsp, 0FFFFFFFFFFFFFFF0h 000000007BCEF069 48 81 EC 40 03 00 00 sub rsp, 340h 000000007BCEF070 0F 11 B5 50 FF FF FF movups [rbp+var_B0], xmm6 000000007BCEF077 0F 11 BD 60 FF FF FF movups [rbp+var_A0], xmm7 000000007BCEF07E 44 0F 11 85 70 FF FF FF movups [rbp+var_90], xmm8 000000007BCEF086 44 0F 11 4D 80 movups [rbp+var_80], xmm9 000000007BCEF08B 44 0F 11 55 90 movups [rbp+var_70], xmm10 000000007BCEF090 44 0F 11 5D A0 movups [rbp+var_60], xmm11 000000007BCEF095 44 0F 11 65 B0 movups [rbp+var_50], xmm12 000000007BCEF09A 44 0F 11 6D C0 movups [rbp+var_40], xmm13 000000007BCEF09F 44 0F 11 75 D0 movups [rbp+var_30], xmm14 000000007BCEF0A4 44 0F 11 7D E0 movups [rbp+var_20], xmm15 000000007BCEF0A9 48 89 4D 10 mov [rbp+ProcessHandle], rcx 000000007BCEF0AD 89 55 18 mov [rbp+ProcessInformationClass], edx 000000007BCEF0B0 4C 89 45 20 mov [rbp+ProcessInformation], r8 000000007BCEF0B4 44 89 4D 28 mov [rbp+ProcessInformationLength], r9d 000000007BCEF0B8 C7 84 24 3C 03 00 00 00+ mov dword ptr [rsp+3F0h+n+4], 0 000000007BCEF0C3 C7 84 24 38 03 00 00 00+ mov dword ptr [rsp+3F0h+n], 0 000000007BCEF0CE 48 B8 70 CA D9 7B 00 00+ mov rax, offset __wine_dbch_ntdll_6 ... --- snip --- Wine-Staging patchset: https://github.com/wine-staging/wine-staging/tree/HEAD/patches/winebuild-Fa… Relevant part: https://github.com/wine-staging/wine-staging/blob/HEAD/patches/winebuild-Fa… (+prerequisite). Generated 64-bit thunks: --- snip --- ... 0000000143FCFA88 | B8 70 00 00 00 | mov eax, 70 0000000143FCFA8D | 65 FF 14 25 00 01 00 00 | call qword ptr gs:[100] 0000000143FCFA95 | C3 | ret 0000000143FCFA96 | 00 00 | add byte ptr ds:[rax], al 0000000143FCFA98 | B8 71 00 00 00 | mov eax, 71 0000000143FCFA9D | 65 FF 14 25 00 01 00 00 | call qword ptr gs:[100] 0000000143FCFAA5 | C3 | ret ... --- snip --- NOTE: I wanted to keep a separate ticket for 64-bit syscall thunks to track/validate it separately from 32-bit parts (bug 21232). 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.

2 59

[Bug 39389] New: Text does not render in Forward to the Sky
by wine-bugs＠winehq.org 10 May '21

10 May '21

https://bugs.winehq.org/show_bug.cgi?id=39389 Bug ID: 39389 Summary: Text does not render in Forward to the Sky Product: Wine Version: 1.7.51 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: funtimeschaos(a)rocketmail.com Distribution: --- Created attachment 52500 --> https://bugs.winehq.org/attachment.cgi?id=52500 Terminal output Title. I get empty speech bubbles with voice acting, as well as intro screens with just a picture and a button to continue, when there should be text with the picture. I've attached terminal output. -- 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.

2 4

[Bug 46864] New: MyStat 12 crashes when trying to open spreadsheet tab
by wine-bugs＠winehq.org 09 May '21

09 May '21

https://bugs.winehq.org/show_bug.cgi?id=46864 Bug ID: 46864 Summary: MyStat 12 crashes when trying to open spreadsheet tab Product: Wine Version: 4.3 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lleytonj73(a)gmail.com Created attachment 63918 --> https://bugs.winehq.org/attachment.cgi?id=63918 Error backtrace (Wine 4.3) There's actually quite a lot of reasons this program crashes, and I noticed there aren't any existing bug reports for this program here. The error backtrace attached was caused when I selected File > New > Data to open a spreadsheet tab. Instead of opening the tab, the program "encountered an error and needs to close". -- 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.

2 11

[Bug 50205] New: Steam News causes Steam crash after login
by WineHQ Bugzilla 08 May '21

08 May '21

https://bugs.winehq.org/show_bug.cgi?id=50205 Bug ID: 50205 Summary: Steam News causes Steam crash after login Product: Wine-staging Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68716 --> https://bugs.winehq.org/attachment.cgi?id=68716 gnome terminal output running steam Subject tells it all. Attaching terminal output. -- 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 7

[Bug 50559] New: widl-winrt-support patchset breaks compilation with clang
by WineHQ Bugzilla 08 May '21

08 May '21

https://bugs.winehq.org/show_bug.cgi?id=50559 Bug ID: 50559 Summary: widl-winrt-support patchset breaks compilation with clang Product: Wine-staging Version: 6.0 Hardware: x86-64 OS: Linux Status: NEW Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- clang -c -o dlls/windows.media.speech.dll/windows.media.speech_main.cross.o dlls/windows.media.speech.dll/windows.media.speech_main.c \ -Idlls/windows.media.speech.dll -Iinclude -Iinclude/msvcrt -D__WINESRC__ -D_UCRT -DWINE_CROSS_PE \ -Wall -target i686-windows -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body \ -Wignored-qualifiers -Wno-pragma-pack -Wstrict-prototypes -Wtype-limits -Wvla -Wwrite-strings \ -Wpointer-arith -Wabsolute-value -fno-omit-frame-pointer -gdwarf-2 -gstrict-dwarf -g -O2 In file included from dlls/windows.media.speech.dll/windows.media.speech_main.c:18: include/windows.media.speechsynthesis.h:574:14: error: 'selectany' can only be applied to data items with external linkage static const DECLSPEC_SELECTANY WCHAR RuntimeClass_Windows_Media_SpeechSynthesis_VoiceInformation[] = {'W','i','n','d','o','w','s','.','M','e','d','i','a','.','S','p','e','e','c','h','S','y','n','t','h','e','s','i','s','.','V','o','i','c','e','I','n','f','o','r','m','a','t','i','o','n',0}; ^ include/winnt.h:112:39: note: expanded from macro 'DECLSPEC_SELECTANY' #define DECLSPEC_SELECTANY __declspec(selectany) ^ 1 error generated. Source of the breakage is this patch: https://github.com/wine-staging/wine-staging/blob/master/patches/widl-winrt… It even mentions that: https://github.com/wine-staging/wine-staging/blob/master/patches/widl-winrt… + /* MIDL generates extern const here */ + fprintf(header, "static const DECLSPEC_SELECTANY WCHAR RuntimeClass_%s[] = {", c_name); -- 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

[Bug 48200] New: Approach "Shell" function stopped working
by WineHQ Bugzilla 08 May '21

08 May '21

https://bugs.winehq.org/show_bug.cgi?id=48200 Bug ID: 48200 Summary: Approach "Shell" function stopped working Product: Wine-staging Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- $ rpm -qa wine-common wine-common-4.20-1.fc31.noarch Fedora 31, x64 Help! Lotus Approach's "Shell" function in Word Pro stopped working after upgrading to 4.20. Result = Shell ( "z:\home\linuxutil\CopyToClipboard.pl" + " " + FullAddress) CopyToClipboard.pl never see the call. This happens on all me shell call. Its killing me! -- 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 23

[Bug 50700] New: possible regression? unimplemented function dx7vb.dll.DllRegisterServer in application that ships with own dx7vb.dll
by WineHQ Bugzilla 08 May '21

08 May '21

https://bugs.winehq.org/show_bug.cgi?id=50700 Bug ID: 50700 Summary: possible regression? unimplemented function dx7vb.dll.DllRegisterServer in application that ships with own dx7vb.dll Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lunarlambda(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I have an old application that came with dx7vb.dll. To get it to run in wine, I had to `regsvr32 dx7vb.dll`. After that, everything worked fine. After moving to wine-staging, neither the application or regsvr work anymore, crashing with an unimplemented call to dx7vb.dll.DllRegisterServer. Adding a native library override for dx7vb.dll didn't seem to work. I can't provide much info on the application, it's basically vaporware - but it did work on stable nevertheless. -- 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 48037] New: In World of Tanks in battle, mouse stuck in the middle
by WineHQ Bugzilla 08 May '21

08 May '21

https://bugs.winehq.org/show_bug.cgi?id=48037 Bug ID: 48037 Summary: In World of Tanks in battle, mouse stuck in the middle Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HASH.DuOrden(a)gmail.com Distribution: --- Starting with wine 4.17, in battle mouse is stuck to the center of the screen, it's just wiggles in middle and do not move the targeting reticle. This feels very similar to what happens when "MouseWarpOverride"="force" with only difference that with "MouseWarpOverride"="force" mouse acts like this all the time but here mouse are stuck to center only when game requests the lock, I'm not sure that I get the technical part correctly. PS:This feels like a continuation of a bug #47771. -- 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 50586] New: [regression] NtQueryInformationFile returning STATUS_INVALID_INFO_CLASS (0xc0000003) on symlinks opened with option FILE_OPEN_REPARSE_POINT (0x00200000)
by WineHQ Bugzilla 08 May '21

08 May '21

https://bugs.winehq.org/show_bug.cgi?id=50586 Bug ID: 50586 Summary: [regression] NtQueryInformationFile returning STATUS_INVALID_INFO_CLASS (0xc0000003) on symlinks opened with option FILE_OPEN_REPARSE_POINT (0x00200000) Product: Wine-staging Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mr.dovi(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69263 --> https://bugs.winehq.org/attachment.cgi?id=69263 wine_file.c testcase Possible related issue: https://bugs.winehq.org/show_bug.cgi?id=50036 I'm investigating the cause of a application startup crash happening on wine-staging 6.0 but not on wine-staging-5.21, wine-5.13 and wine-6.0 While I think I have found a workaround to have it running on staging-6.0, I realized it may be worth a share since it took me a few hours of searching the relay logs. I have attached a test case but basically, calling NtQueryInformationFile on a symlink opened with the file handle option FILE_OPEN_REPARSE_POINT seem to cause NtQueryInformationFile to return STATUS_INVALID_INFO_CLASS, even if the class is correctly set to FileAllInformation # wine 5.13 # pNtCreateFile -> 0 # NtQueryInformationFile -> 0 # wine 5.13 # pNtCreateFile -> 0 # NtQueryInformationFile -> 0 # wine-staging 5.21 # pNtCreateFile -> 0 # NtQueryInformationFile -> 0 # wine-staging 5.21 # pNtCreateFile -> 0 # NtQueryInformationFile -> 0 # wine-staging 6.0 # pNtCreateFile -> 0 # NtQueryInformationFile -> c0000003 # wine-staging 6.0 # pNtCreateFile -> 0 # NtQueryInformationFile -> 0 My system is Arch Linux -- 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 54