December 2020 - Wine-Bugs - list.winehq.org

[Bug 49975] New: Battlefield 1, 4 and V not start from with wine-staging 5.17 on
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=49975 Bug ID: 49975 Summary: Battlefield 1, 4 and V not start from with wine-staging 5.17 on Product: Wine-staging Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: llenort(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68376 --> https://bugs.winehq.org/attachment.cgi?id=68376 crash dump wine-staging 5.19 - BF 1 Hi, from Version 5.17 on, current Version 5.19, no Battlefield game i tested can't start. Tested with wine-staging Version 5.17, 5.18 and 5.19. I attached a crash dump file. Wine-staging Version 5.16 works perfect for all BF Games i tested so far. Thank you for your support. All the Best :-) lle -- 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 8

[Bug 46237] New: Far 3.0 x86 crashes starting from build 5288
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=46237 Bug ID: 46237 Summary: Far 3.0 x86 crashes starting from build 5288 Product: Wine Version: 3.21 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)chatty.de Created attachment 62934 --> https://bugs.winehq.org/attachment.cgi?id=62934 Build 5287 runs fine. Starting from build 5288 Far 3.0 x86 crashes at startup. -- 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 22

[Bug 49116] New: Windows 10 1903 SDK (10.0.18362.0) installer crashes (method invocation on wrong CCW interface?)
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=49116 Bug ID: 49116 Summary: Windows 10 1903 SDK (10.0.18362.0) installer crashes (method invocation on wrong CCW interface?) Product: Wine Version: 5.7 Hardware: x86 URL: https://web.archive.org/web/20200215010843/https://dow nload.microsoft.com/download/4/2/2/42245968-6A79-4DA7- A5FB-08C0AD0AE661/windowssdk/winsdksetup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- It calls _AppDomain::CreateInstance() from unmanaged code to retrieve a COM pointer to one of its own objects (specifically, BootstrapperApplicationFactory, hosted in BootstrapperCore.dll), and then tries to invoke a method on the object. The problem is that the method it invokes has vtbl offset 0x38, but Mono gives us back what *seems* to be an IDispatch vtbl, so it ends up invoking junk. This consistently results in an execute fault for me. Relevant disassembly, from mbahost.dll: 1286: 8b 45 08 >mov eax, [ebp+08h] 1289: 8d 55 fc lea edx, [ebp-04h] 128c: 52 push edx 128d: 57 push edi 128e: 53 push ebx 128f: 8b 08 mov ecx, [eax] 1291: 50 push eax 1292: ff 91 94 00 00 00 call dword [ecx+00000094h] // CreateInstance(), apparently 1298: 8b f0 mov esi, eax 129a: 85 f6 test esi, esi 129c: 79 08 jns 12a6 // jump if SUCCEEDED 129e: 56 push esi 129f: 68 1f 02 00 00 push dword 0000021Fh 12a4: eb 48 jmp 12ee 12a6: 8b 45 fc >mov eax, [ebp-04h] 12a9: 8d 55 ec lea edx, [ebp-14h] 12ac: 52 push edx 12ad: 50 push eax 12ae: 8b 08 mov ecx, [eax] 12b0: ff 51 38 call dword [ecx+38h] // crashes Presumably Mono is wrong in returning IDispatch here, but I'm not sure why, and it's not clear what should be returned in its stead. The class in question actually has a ClassInterfaceType of AutoDispatch, but maybe that doesn't actually mean we should return IDispatch? But the CIL interface that class explicitly implements, IBootstrapperApplicationFactory, only has one method, so I'm not sure how an offset of 0x38 makes sense there either. When I get the time I'll build and run a testcase... -- 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 20

[Bug 46236] New: Far 3.0 x64 crashes starting from build 5200
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=46236 Bug ID: 46236 Summary: Far 3.0 x64 crashes starting from build 5200 Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)chatty.de Distribution: --- Created attachment 62932 --> https://bugs.winehq.org/attachment.cgi?id=62932 Build 5199 runs fine. Starting from build 5200 Far 3.0 x64 crashes at startup. -- 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 29

[Bug 44435] New: Call of Duty WWII crash
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=44435 Bug ID: 44435 Summary: Call of Duty WWII crash Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 60377 --> https://bugs.winehq.org/attachment.cgi?id=60377 Wine crash log The game installs fine but it crashes after the splash screen. I tested with Wine 3.0. -- 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 8

[Bug 44882] New: Call of Duty Infinite Warfare crashes after Splash-Screen with a Direct-X Error
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=44882 Bug ID: 44882 Summary: Call of Duty Infinite Warfare crashes after Splash-Screen with a Direct-X Error Product: Wine Version: 3.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Created attachment 60948 --> https://bugs.winehq.org/attachment.cgi?id=60948 logfile (7z format) part 1 Hi, when trying to start the game, i shows the splash screen and then shows a message Box with an Direct-X Error (sadly in german, but you can find it in the attached trace): 6549764:008b:Call user32.MessageBoxW(00050162,00238e80 L"Schwerwiegender DirectX-Fehler.\n\nWeitere Hinweise finden Sie in der Readme-Datei.",00238c80 L"DirectX-Fehler",00000010) ret=140d577cb The first number is the line number. As i noticed that none of the newer Cod titles is working in wine and it is still a somewhat popular gameing franchise, it would be fantastic if a dev could take a look at the trace. If there are any questions, i am glad to help. Had to split the 7z logfile in 2 pieces, xaa and xab. Thx a lot ! Christian -- 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 6

[Bug 50213] New: Summer Pockets (demo) complains about timezone settings.
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=50213 Bug ID: 50213 Summary: Summer Pockets (demo) complains about timezone settings. Product: Wine Version: 5.21 Hardware: x86-64 URL: http://suezou.dyndns.org/dl2018/key/summer_pokets/Summ er_Pockets_trial.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 68721 --> https://bugs.winehq.org/attachment.cgi?id=68721 error dialog Similar to bug 42719, Summer Pockets (demo version) complains about timezone settings. It says "North Korea Standard Time", instead. When I launch the game, it shows: ----- 日本語版Windows判定 ----- This Game is Japan Only このゲームは日本国内でのみプレイ可能です。動作させるには『日本語版Windows』が必要です。コンピュータの現在のタイムゾーン設定は『North Korea Standard Time』です。タイムゾーンを『日本（大阪、札幌、東京）』に設定してください。ゲームを終了します。 ----- Translated: ----- Japanese version Windows detection ----- This Game is Japan Only This game is only playable in Japan. "Japanese version Windows" is required to operate. Current timezone settings for this PC is "North Korea Standard Time". Please set the timezone to "Japan (Osaka, Sapporo, Tokyo)". Quitting the game. ----- Of course, I ran it with Japan Standard Time, i.e. /etc/localtime points to /usr/share/zoneinfo/Asia/Tokyo. -- 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 4

[Bug 50154] New: Allow using SDL_GAMECONTROLLERCONFIG to configure SDL controller mappings
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=50154 Bug ID: 50154 Summary: Allow using SDL_GAMECONTROLLERCONFIG to configure SDL controller mappings Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: braiamp(a)gmail.com Distribution: --- As of 5.22, the only way to modify SDL mappings is via a registry key modification (which also has problems on bug #48545). Other applications that support SDL allows using environmental variables to set mappings, which would allow end users to adapt their mappings to the application adhoc rather than having to modify the registry. -- 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 9

[Bug 42623] New: Changing current dir ~/.wine crashes Wine
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=42623 Bug ID: 42623 Summary: Changing current dir ~/.wine crashes Wine Product: Wine Version: 2.3 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)chatty.de When running Far 3.0.4912.x86 on MacOS 10.12.3 with Wine 2.3 Staging (because Develop does not yet support GetStorageDependencyInformation) it crashes when executing "cd ~/.wine": fixme:console:GetConsoleAliasW (L"cd",0xc8e118,8192,L"cmd.exe"): stub fixme:explorerframe:taskbar_list_SetProgressValue iface 0xbbfc80, hwnd 0x40060, ullCompleted 1, ullTotal 1 stub! fixme:win:FlashWindowEx 0x33e790 - semi-stub wine: Unhandled page fault on read access to 0x00190002 at address 0x420a055d (thread 007d), starting debugger... And when starting Far I get lots of: fixme:module:load_library unsupported flag(s) used (flags: 0x00000800) -- 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 14

[Bug 50236] New: Wine builtin 'winepath' doesn't show any output since Wine 5.22
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=50236 Bug ID: 50236 Summary: Wine builtin 'winepath' doesn't show any output since Wine 5.22 Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, just found by chance ... --- snip --- $ export PATH=/home/focht/projects/wine/mainline-install-5.21-x86_64/bin:$PATH $ wine --version wine-5.21 $ winepath -u "c:" /home/focht/.wine/dosdevices/c:/ --- snip --- --- snip --- $ export PATH=/home/focht/projects/wine/mainline-install-5.22-x86_64/bin:$PATH $ wine --version wine-5.22 $ winepath -u "c:" --- snip --- Same with current master HEAD. $ wine --version wine-5.22-260-g2ad09b01673 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 7