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

[Bug 42711] New: Program AntiDupl.net does not start.
by wine-bugs＠winehq.org 13 Nov '20

13 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=42711 Bug ID: 42711 Summary: Program AntiDupl.net does not start. Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: trym(a)2.pl Distribution: --- Created attachment 57687 --> https://bugs.winehq.org/attachment.cgi?id=57687 Details of program error. The problem is with software that searches for repetitive pictures named AntiDupl.NET in version-2.3.8.http://antidupl.sourceforge.net/english/index.html?page=downl… The program does not start. -- 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 48711] New: osu! crashes on dotnet452 when using built-in gdiplus: System.ArgumentException: Font '?' cannot be found.
by WineHQ Bugzilla 13 Nov '20

13 Nov '20

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 12 Nov '20

12 Nov '20

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 12 Nov '20

12 Nov '20

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 12 Nov '20

12 Nov '20

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 11 Nov '20

11 Nov '20

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 46726] New: Dirt Rally 2.0 does not use embedded CA cert
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

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 49289] New: Denuvo Anti-Cheat 'denuvo-anti-cheat.sys' crashes on unimplemented function ntoskrnl.exe.ExRegisterCallback
by WineHQ Bugzilla 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=49289 Bug ID: 49289 Summary: Denuvo Anti-Cheat 'denuvo-anti-cheat.sys' crashes on unimplemented function ntoskrnl.exe.ExRegisterCallback Product: Wine Version: 5.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44925 --- snip --- $ WINEDEBUG=+seh,+relay,+int,+ntoskrnl,+ntdll,+reg wine net start "Denuvo Anti-Cheat" >>log.txt 2>&1 ... 00d0:Call ntoskrnl.exe.ExCreateCallback(00b5f518,00b5f530,00000000,00b5ec01) ret=00d40b52 00d0:fixme:ntoskrnl:ExCreateCallback (0000000000B5F518, 0000000000B5F530, 0, 1): stub 00d0:Call KERNEL32.IsBadStringPtrW(00cfa000,ffffffffffffffff) ret=00236277 00d0:Ret KERNEL32.IsBadStringPtrW() retval=00000000 ret=00236277 00d0:fixme:ntoskrnl:ExCreateCallback name L"\\Callback\\PowerState", RootDirectory 0000000000000000. 00d0:Ret ntoskrnl.exe.ExCreateCallback() retval=00000000 ret=00d40b52 00d0:Call KERNEL32.RaiseException(80000100,00000001,00000002,00b5f4a0) ret=0023f178 00d0:Call ntdll.memcpy(00b5f388,00b5f4a0,00000010) ret=7b010516 00d0:Ret ntdll.memcpy() retval=00b5f388 ret=7b010516 00d0:trace:seh:raise_exception code=80000100 flags=1 addr=0x7b010525 ip=7b010525 tid=00d0 00d0:trace:seh:raise_exception info[0]=000000000025d000 00d0:trace:seh:raise_exception info[1]=000000000025d9f1 00d0:trace:seh:call_vectored_handlers calling handler at 0x22d090 code=80000100 flags=1 00d0:trace:seh:call_vectored_handlers handler at 0x22d090 returned 0 00d0:trace:seh:RtlVirtualUnwind type 1 rip 7b010525 rsp b5f340 ... wine: Call from 0x7b010525 to unimplemented function ntoskrnl.exe.ExRegisterCallback, aborting --- snip --- $ wine --version wine-5.9-161-gadf80db41d 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 5

[Bug 49178] New: Spitfire Audio crashes on start
by WineHQ Bugzilla 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=49178 Bug ID: 49178 Summary: Spitfire Audio crashes on start Product: Wine Version: 5.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzo(a)leonardini.dev Distribution: --- Created attachment 67195 --> https://bugs.winehq.org/attachment.cgi?id=67195 error backtrace The Spitfire Audio App crashes even before showing any window. The application worked fine until version 3.1.18, but since the update 3.2.3, and still in the current version 3.2.6 it doesn't start anymore. Unfortunately, the software doesn't allow you to use an outdated version and automatically updates itself. I am using wine-5.8 (Staging) on an Arch Linux system (64 bit). Links to different version downloads: - 3.1.18 https://d1t3zg51rvnesz.cloudfront.net/p/files/lm/1584702000/win/SpitfireAud… - 3.2.3 https://d1t3zg51rvnesz.cloudfront.net/p/files/lm/1588863600/win/SpitfireAud… - 3.2.6 https://d1t3zg51rvnesz.cloudfront.net/p/files/lm/1589374800/win/SpitfireAud… -- 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 25

[Bug 45536] New: Total Commander 9.x crashes on unimplemented function usp10.dll.ScriptGetFontAlternateGlyphs when Wine is not detected
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=45536 Bug ID: 45536 Summary: Total Commander 9.x crashes on unimplemented function usp10.dll.ScriptGetFontAlternateGlyphs when Wine is not detected Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, while investigating bug 45514 (dupe of bug 42497) my Total Commander 9.x installation stopped working because I made 'wine_get_version' a '-noname' ordinal export (cheaper way, to avoid using Wine-Staging/patchset). The app no longer detects Wine and runs into a problem. Download: https://totalcommander.ch/win/tcmd920x64.exe --- snip --- $ pwd /home/focht/wineprefix64-tcmd/drive_c/totalcmd $ file *.{DLL,EXE} TC7Z64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows TCLZMA64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows TCUNZL64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows UNRAR64.DLL: PE32+ executable (DLL) (console) x86-64, for MS Windows WCMICON2.DLL: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows WCMICONS.DLL: PE32 executable (GUI) Intel 80386, for MS Windows WCMZIP64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows NOCLOSE64.EXE: PE32+ executable (GUI) x86-64, for MS Windows TCMADM64.EXE: PE32+ executable (GUI) x86-64, for MS Windows TCMDX32.EXE: PE32 executable (GUI) Intel 80386, for MS Windows TCUNIN64.EXE: PE32+ executable (GUI) x86-64, for MS Windows TOTALCMD64.EXE: PE32+ executable (GUI) x86-64, for MS Windows $ WINEDEBUG=+seh,+relay wine TOTALCMD64.EXE >>log.txt 2>&1 ... 0030:Call KERNEL32.GetProcAddress(7bc80000,00a8a890 "wine_get_version") ret=00474dbb 0030:Ret KERNEL32.GetProcAddress() retval=00000000 ret=00474dbb ... 0030:Ret usp10.ScriptItemize() retval=00000000 ret=009f4047 0030:Call usp10.ScriptShape(00250258,00bd1bc0,01cb9768,00000001,00000010,00099634,02f35050,02f35090,02f350d0,0037693c) ret=009f40d1 ... 0030:Ret usp10.ScriptShape() retval=00000000 ret=009f40d1 0030:Call KERNEL32.RaiseException(80000100,00000001,00000002,01cb96a0) ret=7fe6fee5eb50 0030:trace:seh:NtRaiseException code=80000100 flags=1 addr=0x7b4944b9 ip=7b4944b9 tid=0030 0030:trace:seh:NtRaiseException info[0]=00007fe6fee5eb80 0030:trace:seh:NtRaiseException info[1]=00007fe6fee5eb95 wine: Call from 0x7b4944b9 to unimplemented function usp10.dll.ScriptGetFontAlternateGlyphs, aborting 0030:trace:seh:call_vectored_handlers calling handler at 0x419950 code=80000100 flags=1 ... --- snip --- Source: https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/usp10/usp10.spec#l9 --- snip --- 9 @ stub ScriptGetFontAlternateGlyphs --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows/desktop/api/usp10/nf-usp10-scriptg… $ sha1sum tcmd920x64.exe d27abd02fe60002cfb60b1c68888a666c48c9142 tcmd920x64.exe $ du -sh tcmd920x64.exe 5.0M tcmd920x64.exe $ wine --version wine-3.13 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 8