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

[Bug 50009] New: Scrivener installer fails on 5.19
by WineHQ Bugzilla Nov. 13, 2020

Nov. 13, 2020

https://bugs.winehq.org/show_bug.cgi?id=50009 Bug ID: 50009 Summary: Scrivener installer fails on 5.19 Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: garputhefork(a)gmail.com Distribution: --- Created attachment 68418 --> https://bugs.winehq.org/attachment.cgi?id=68418 backtrace of the Scrivener installer With wine 5.19 (with staging), the Scrivener installer crashes. It worked with 5.18 and 5.16 (both staging) I haven't tried a non-staging build for 5.19. I tested it in a clean prefix, as well. (Scrivener installer: https://www.literatureandlatte.com/scrivenerforwindows/beta/Scrivener-29911…) To my knowledge, nothing changed about the installer. (Scrivener, the program, works fine on 5.19.) -- 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 48711] New: osu! crashes on dotnet452 when using built-in gdiplus: System.ArgumentException: Font '?' cannot be found.
by WineHQ Bugzilla Nov. 13, 2020

Nov. 13, 2020

https://bugs.winehq.org/show_bug.cgi?id=48711 Bug ID: 48711 Summary: osu! crashes on dotnet452 when using built-in gdiplus: System.ArgumentException: Font '?' cannot be found. Product: Wine Version: 5.3 Hardware: x86 URL: https://osu.ppy.sh/home/download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: huupoke12(a)gmail.com Distribution: --- Created attachment 66583 --> https://bugs.winehq.org/attachment.cgi?id=66583 Terminal log of the crash on Wine 5.3 with dotnet452 installed osu! crashes when running after installing dotnet452. I also tried dotnet45, dotnet472, dotnet48 and it also crashes with the same error. But it doesn't crash when using dotnet40 (I have created a new WINEPREFIX for each dotnet to test that). This bug only happens when using default built-in gdiplus, since installing Windows native gdiplus solved this bug. And I have tried rolling back to previous Wine version and this bug maybe a regression since Wine 5.1, the 5.0 release does not have this bug. -- 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 3

[Bug 43409] New: Banished won't run on FreeBSD ( failed to initialize the memory allocator!)
by wine-bugs＠winehq.org Nov. 12, 2020

Nov. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=43409 Bug ID: 43409 Summary: Banished won't run on FreeBSD (failed to initialize the memory allocator!) Product: Wine Version: 2.10 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 I'm running FreeBSD 11.0-RELEASE-p1 amd64 and I am using Wine staging 2.10 i386. When I try to run Banished, I have a little window saying : A fatal error has occured and the application cannot continue. Memory: The application failed to initialize the memory allocator! The only message I have in the terminal, after the usual "consider using nouveau instead", is : err:ole:CoUninitialize Mismatched CoUninitialize I don't know if it is linked to my issue. -- 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 1

[Bug 40233] New: Devil Daggers Refuses to Start
by wine-bugs＠winehq.org Nov. 12, 2020

Nov. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=40233 Bug ID: 40233 Summary: Devil Daggers Refuses to Start Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tristanlshockley(a)gmail.com Distribution: --- Created attachment 53778 --> https://bugs.winehq.org/attachment.cgi?id=53778 Devil Dagger Force Close Output I created a thread in the forums (https://forum.winehq.org/viewtopic.php?f=8&t=26228) where I was recommended to create a bug report. To get to this point I needed lib32-openal. After installing samba a winbind error was removed (see the forum link) but this doesn't appear to change anything. The game will not start through terminal because of DRM, you need to run the game through Steam in WINE. When you do so you will see a black box which will autoclose in about five seconds. Attached is the text Steam spits out during this time, and if I can figure out how to post another I will provide an image of the black box. -- 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 12

[Bug 40928] New: Sword of the Stars: The Pit Gold Edition (.NET 4.0/XNA) crashes with a SIGSEGV when using wine-mono
by wine-bugs＠winehq.org Nov. 12, 2020

Nov. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=40928 Bug ID: 40928 Summary: Sword of the Stars: The Pit Gold Edition (.NET 4.0/XNA) crashes with a SIGSEGV when using wine-mono Product: Wine Version: 1.9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 55038 --> https://bugs.winehq.org/attachment.cgi?id=55038 Terminal output for Wine-1.9.13-114-gb1930ee Windows XP mode Windows XP mode, clean 32-bit prefix. After installing the GOG version of Sword of the Stars: The Pit Gold Edition and running "wine ThePit.exe" I am greeted with what appears to be a wine-mono crash. Wine-mono 4.6.3 is installed. -- 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 7

[Bug 47801] New: Growing build/wine VM disk usage
by WineHQ Bugzilla Nov. 11, 2020

Nov. 11, 2020

https://bugs.winehq.org/show_bug.cgi?id=47801 Bug ID: 47801 Summary: Growing build/wine VM disk usage Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 65291 --> https://bugs.winehq.org/attachment.cgi?id=65291 Evolution of wtbdebian10's revert times Every time we update and rebuild Wine in these VMs the VM's qcow2 file grows. The Wine VMs are those where the disk grows fastest, from ~5 GB to 60+ GB in a matter of weeks. Fortunately it does seem to grow slower after a while. For instance <6 GB to 32 GB (du) from 2019-09-20 to 2019-09-25 for wtbdebian10. This may be caused by the way WineRunReconfig handles live snapshots. To summarize: * Restore to the current live snapshot. * Update and rebuild Wine. * Iff that succeeded, delete the live snapshot and recreate it. This may cause QEmu to not realize that all the data from the now deleted old live snapshot can be reclaimed and reused for the next Wine build. But we had to delete the live snapshot at the last minute because losing it would mean the VM would be unusable until the TestBot administrator could come and fix it. However nowadays the TestBot can recreate live snapshots from powered off snapshots. This means we could delete the live snapshot first, rebuild and recreate the snapshot at the end. In the unlikely event that something goes wrong the live snapshot could be recreated from the powered off 'base'... except in the case of a build error. That case would be unrecoverable unlike in the current scheme. A test with this alternative snapshot management should be made to see if it does actually make a difference in the qcow2 growth (there's really no guarantee it does). For these VMs the revert time does seem to degrade a bit with time(*). This may be related to the qcow2 size and/or accumulation of "phantom snapshots". So the experiment should be run for a while to see if it makes a difference on this metric too. (*) See the Munin graph of wtbdebian10's revert time. The drop in week 38 and 39 correspond to maintenance on the VM where all snapshots were deleted and virt-sparsify run on its disk. -- 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 1

[Bug 49666] New: Red Dead Redemption 2 requires HEAP flags offset to match Windows
by WineHQ Bugzilla Nov. 10, 2020

Nov. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=49666 Bug ID: 49666 Summary: Red Dead Redemption 2 requires HEAP flags offset to match Windows Product: Wine Version: 5.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com Distribution: --- Red Dead Redemption 2 gets ProcessHeap from the PEB, and directly accesses the 'flags' and 'force_flags' fields of the HEAP structure. Those fields need to be at the same offset as they are on WinVista through current Win10, 0x40/0x70. Wine currently pads the struct so 'flags' is in the correct place (0xC) vs. WinNT/2000/XP https://ctf-wiki.github.io/ctf-wiki/reverse/windows/anti-debug/heap-flags/ -- 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 49656] New: SAP GUI - Ws2_32.getaddrinfo crashes with non-standard service (/etc/services)
by WineHQ Bugzilla Nov. 10, 2020

Nov. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=49656 Bug ID: 49656 Summary: SAP GUI - Ws2_32.getaddrinfo crashes with non-standard service (/etc/services) Product: Wine Version: 5.14 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: guimaeda(a)gmail.com Created attachment 67890 --> https://bugs.winehq.org/attachment.cgi?id=67890 Terminal output (both success and crash) Calling getaddrinfo with pNodeName = NULL and a non-standard pServiceName that is not present in /etc/services causes an Unhandled page fault. I noticed this issue using SAP GUI, a Windows client for a corporate ERP system that uses unusual TCP ports for some of its connections to servers. These port numbers are registered in %WINDIR%\system32\drivers\etc\services during installation, and after going through some traces I noticed the error stopped after adding the same entries to the host's (macOS) /etc/services file. Since SAP GUI is licensed software, I created a little C program that simulates the same problem. It simply calls getaddrinfo with a service name "I_dont_exist". If this entry is not present in /etc/services, the program crashes. Tested on Wine 5.14 upstream binaries downloaded from PlayOnLinux/Phoenicis Wine building service. I also tested in other Wine version I use, namely 5.14-staging, 5.0 (WineHQ Homebrew), 5.7-staging (WineHQ Homebrew) and CrossOver 19.0.1. All had the same result. Sample C program with .exe and source code: https://abap.ninja/bugreport/wine_getaddrinfo_crash.zip -- 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 46726] New: Dirt Rally 2.0 does not use embedded CA cert
by wine-bugs＠winehq.org Nov. 10, 2020

Nov. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=46726 Bug ID: 46726 Summary: Dirt Rally 2.0 does not use embedded CA cert Product: Wine Version: 4.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: andreas(a)heider.io Distribution: --- Hi, Dirt Rally 2.0 requires an online connection to play the single player campaign, but with Wine 4.2 it can't successfully establish that connection due to a certificate issue. It tries to connect to https://prod.egonet.codemasters.com/, but since it does not trust the certificate the connection fails. The required CA certificate is embedded in dirtrally2.exe, but Wine does not seem to pick it up and use it. It all works perfectly if I manually trust the CA system-wide, by placing codemasters.pem in /etc/ca-certificates/trust-source/anchors and run update-ca-trust. -- 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 15

[Bug 49488] New: uninitialized bytes in server call from ntdll/server_write_file
by WineHQ Bugzilla Nov. 10, 2020

Nov. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=49488 Bug ID: 49488 Summary: uninitialized bytes in server call from ntdll/server_write_file Product: Wine Version: 5.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Created attachment 67607 --> https://bugs.winehq.org/attachment.cgi?id=67607 Configure output. Steps to reproduce * Build wine (currently ec9e556d31). Attached my configure output. See for configure flags. * Build 'int main() { return 0; }' under i686-w64-mingw-gcc * Run under valgrind. Valgrind output attached. The first valgrind error is: ==1472== Syscall param writev(vector[...]) points to uninitialised byte(s) ==1472== at 0x432C2A3: __writev (writev.c:26) ==1472== by 0x432C2A3: writev (writev.c:24) ==1472== by 0x485A099: send_request (server.c:221) ==1472== by 0x485A1DB: server_call_unlocked (server.c:281) ==1472== by 0x485A236: wine_server_call (server.c:297) ==1472== by 0x484B69E: server_write_file (file.c:4706) ==1472== by 0x484CB30: NtWriteFile (file.c:5272) ==1472== by 0x7BC500A8: NtWriteFile (file.c:176) ==1472== by 0x5E267A7: rpcrt4_conn_np_write (rpc_transport.c:415) ==1472== by 0x5E1BF85: rpcrt4_conn_write (rpc_binding.h:197) ==1472== by 0x5E1DB8C: RPCRT4_SendWithAuth (rpc_message.c:850) ==1472== by 0x5E1E9B7: RPCRT4_Send (rpc_message.c:1249) -- 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