October 2020 - Wine-bugs - list.winehq.org

[Bug 35272] New: Mortal Kombat Komplete Edition (Steam) crashing to desktop within graphics autoconf.
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

http://bugs.winehq.org/show_bug.cgi?id=35272 Bug ID: 35272 Summary: Mortal Kombat Komplete Edition (Steam) crashing to desktop within graphics autoconf. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: wine-bugs(a)winehq.org Classification: Unclassified Created attachment 47044 --> http://bugs.winehq.org/attachment.cgi?id=47044 Terminal output See attached terminal output. Linux Mint 16 Petra Cinnamon x64 ; AMD Radeon 5750 ; Wine 1.7.8 -- 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 16

[Bug 49437] New: Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=49437 Bug ID: 49437 Summary: Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD Product: Wine Version: 5.11 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com For the moment, I stick with wine-5.8 which is actually perfectly working for me. Since wine-5.9, it won't run anymore. It builds, it installs but it won't start and I really have no other message than "Segmentation fault (core dumped)" I build wine without any patch in case this creates the issue (already happened a few months ago). All information I succeeded to have is by using WINEDEBUG=all trace:virtual:NtAllocateVirtualMemory 0xffffffff 0x7ffe0000 00001000 3000 00000002 Segmentation fault (core dumped) That's all I get and I don't even know if it's related to the problem. -- 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 24

[Bug 46028] New: Provide separate debug/symbol info files (.pdb) for 32-bit and 64-bit Wine-Gecko 2.47+ package (unstripped 32-bit ' xul.dll' too large to be mapped)
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=46028 Bug ID: 46028 Summary: Provide separate debug/symbol info files (.pdb) for 32-bit and 64-bit Wine-Gecko 2.47+ package (unstripped 32-bit 'xul.dll' too large to be mapped) Product: Wine-gecko Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: focht(a)gmx.net Distribution: --- Hello folks, while investigating some crashes in Gecko's xul.dll I came across the missing debug symbols again. Bug 36941 repeated. https://wiki.winehq.org/Gecko#Debug_info For the 32-bit part this is pointless as the unstripped 32-bit 'xul.dll' will be always be too large for mapping. Split out symbols via PDB is a must. * http://dl.winehq.org/wine/wine-gecko/2.36/wine_gecko-2.36-x86-dbg-msvc-pdb.… * http://dl.winehq.org/wine/wine-gecko/2.40/wine_gecko-2.40-x86-dbg-msvc-pdb.… * http://dl.winehq.org/wine/wine-gecko/2.44/ -> ??? * http://dl.winehq.org/wine/wine-gecko/2.47/ -> ??? $ wine --version wine-3.18-118-g377243b411 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 16

[Bug 50080] New: Burnout Paradise: The Ultimate Box crashes between intros
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50080 Bug ID: 50080 Summary: Burnout Paradise: The Ultimate Box crashes between intros Product: Wine Version: 5.11 Hardware: x86-64 URL: https://www.pcworld.pl/ftp/pobierz/gry/8685.html OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 6d675064f8f9eeb873a2c91d02c3ccbbfd982d56 Distribution: --- Steps to reproduce: 1. Go to 'GameFolder/VIDEOS' 2. Rename INTRO.VP6 to _INTRO.VP6 3. Copy EAFRANCHISE.VP6 and name it INTRO.VP6 4. Launch test drive in-game -- 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 47950] New: Ys: Memories of Celceta crashes on launch
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=47950 Bug ID: 47950 Summary: Ys: Memories of Celceta crashes on launch Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: betaversiondot(a)gmail.com Distribution: --- Created attachment 65452 --> https://bugs.winehq.org/attachment.cgi?id=65452 terminal output Ys: Memories of Celceta crashes on launch. Clear wineprefix, launcher works, intro videos disabled. 4.17-staging, Linux-5.2.17, RX 580, Mesa3D 19.2.1. -- 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 50037] New: wineconsole and mingw64 gdb.exe and keyboard input
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50037 Bug ID: 50037 Summary: wineconsole and mingw64 gdb.exe and keyboard input Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- After the last wineconsole commit, mingw64 gdb.exe(9.2) which works fine in wine17, does not have the ability to control the keyboard input. Any character that is typed on the keyboard is obviously not transferred to the process in which gdb.exe is! commit 627d31fcd9fa1e4657c781ca07ff25e437101820 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Oct 12 18:27:44 2020 +0200 wineconsole: Reimplement as AllocConsole wrapper. -- 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 46237] New: Far 3.0 x86 crashes starting from build 5288
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

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 49975] New: Battlefield 1, 4 and V not start from with wine-staging 5.17 on
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

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 49116] New: Windows 10 1903 SDK (10.0.18362.0) installer crashes (method invocation on wrong CCW interface?)
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

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 04 Dec '20

04 Dec '20

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