January 2024 - Wine-Bugs - list.winehq.org

[Bug 56136] New: ImageGetDigestStream does not behave the same as on windows
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=56136 Bug ID: 56136 Summary: ImageGetDigestStream does not behave the same as on windows Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: imagehlp Assignee: wine-bugs(a)winehq.org Reporter: hkarlsson(a)gmail.com Distribution: --- Created attachment 75814 --> https://bugs.winehq.org/attachment.cgi?id=75814 Isolated the function and ran it side by side with real windows function to test results Just wanted to report that ImageGetDigestStream does not match the windows (11) version. I suspect this is very low prio and rarely used. It is used by Unreal's ShaderCompileWorker.exe as a way to verify dxcompiler.dll version (and a couple more dlls). The reason it is used is to get same version between signed and unsigned binaries. I tried fixing it up myself but got stuck on some weirdness related to .rsrc section when not having CERT_PE_IMAGE_DIGEST_RESOURCES set (which is a scenario Unreal is not using). Since our usecase is detouring system calls I ended up putting a specialized (and very limited) version of ImageGetDigestStream into our code to workaround the problem for Unreal (The notes section inside wine source code also says that this function is only tested with 32-bit so I suspect this code is very old and extremely rarely used I've attached a hacked up version where my usecase works but there are lots of cases not working so I didn't want to create a pull request. -- 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 55710] New: wine-staging fails to run anything in 64-bit prefix
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=55710 Bug ID: 55710 Summary: wine-staging fails to run anything in 64-bit prefix Product: Wine-staging Version: 8.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal 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: --- Even an attemp to create new 64-bit prefix fails: $ WINEPREFIX=~/.wine64 WINEARCH=win64 ~/wine-staging64/wine winver wine: created the configuration directory '/home/dmitry/.wine64' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:fixme:winediag:LdrInitializeThunk wine-staging 8.17 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 002c:fixme:sync:NtAcceptConnectPort ((nil),832,0x90000002,31,0x7ffffe0ff338,0x7d7d011256a0),stub! *** stack smashing detected ***: <unknown> terminated 002c:err:seh:call_stack_handlers invalid frame 00007FFFFE0FF320 (00007FFFFE102000-00007FFFFE200000) 002c:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. With 32-bit prefix everything seems to work. It looks like this problem started with wine-staging 8.16. -- 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 39

[Bug 52491] New: SpaceDesk: Error when trying to connect to the server now but it worked in 6.10 and below
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=52491 Bug ID: 52491 Summary: SpaceDesk: Error when trying to connect to the server now but it worked in 6.10 and below Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jota0222(a)hotmail.com Distribution: --- Created attachment 71785 --> https://bugs.winehq.org/attachment.cgi?id=71785 Log Of SpaceDesk Runinng After the release of stable 7.0.0, I noticed that SpaceDesk stoped working and then I tried some older versions versions, none of the listed to register the apps in the WineHQ page worked (6.21 and above), however it worked in all the ones below 6.10. I didn't try with the ones in between, so I don't really know when the bug was introduced exactly. The app doesn't throw exceptions or show error in logs, the log attached is basically the same in both 6.10 and 7.0.0 versions. I also tried with winedbg but if I dissable $BreakOnFirstChance it never stops on any exception and the log finish up being the same as the one attached (at least doesn't looks like it's showing things related to the issue). And if I run it with $BreakOnFirstChance set as 1, it's impossible to reach the moment of in which the error occurs due to al the exceptions in which it stops before to even show the window. This image shows the error: https://paste.pics/FTUXV -- 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 11

[Bug 56130] New: Wine is broken on Termux since 8.17-39-g25db1c5d49d
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=56130 Bug ID: 56130 Summary: Wine is broken on Termux since 8.17-39-g25db1c5d49d Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: licy183(a)termux.dev Distribution: --- Created attachment 75807 --> https://bugs.winehq.org/attachment.cgi?id=75807 Error logs I'm trying to port wine on Termux, a Linux emulator on Android. During testing, I found that wine is broken since commit 5db1c5d49dc339e9b5a25514c198a524bd05484. I think simply reverting this commit will break other functions. The log running WINEDEBUG=+all wine a.exe is attached below. My device is Android 10 aarch64. As Wine on Termux is much like a Linux distro rather than an Android APP, I select Linux as OS. This bug is reproducable from 8.18 to 9.0-rc3. -- 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 55731] New: advapi32:eventlog - test_eventlog_start() fails on Windows 10 2004 & 2009
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=55731 Bug ID: 55731 Summary: advapi32:eventlog - test_eventlog_start() fails on Windows 10 2004 & 2009 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:eventlog - test_eventlog_start() fails on Windows 10 2004 & 2009: eventlog.c:1334: Test failed: Expected different handle eventlog.c:1338: Test failed: Expected valid handle eventlog.c:1392: Test failed: EventlogStarted event not found See https://test.winehq.org/data/patterns.html#advapi32:eventlog These failures started on 2023-10-05 which is when test_eventlog_start() was added in the commit below: commit 428a1219fd94919fb93527f2ef582bd28176c03f Author: Daniel Lehman <dlehman25(a)gmail.com> AuthorDate: Mon Oct 2 23:39:16 2023 -0700 advapi32/tests: Add ReadEventLogW tests for EventLogStarted. -- 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 55497] New: regression wine >= 7: page fault on read access to 0x00000000 in "TKKG 1" (EN: Jennifer is Missing, DE: Katjas Geheimnis - Tivoli)
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=55497 Bug ID: 55497 Summary: regression wine >= 7: page fault on read access to 0x00000000 in "TKKG 1" (EN: Jennifer is Missing, DE: Katjas Geheimnis - Tivoli) Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- Created attachment 75060 --> https://bugs.winehq.org/attachment.cgi?id=75060 Wine 7.0.4 backtrace In Wine <= 6.0.4 "TKKG 1" runs fine. But Wine-7.0.2 and newer versions do not work. Game: TKKG 1: Jennifer is Missing (DE: Katjas Geheimnis) Publisher: Tivola (see AppDB) wine-staging-8.14: wine: Unhandled page fault on read access to 00000000 at address 6AB253F0 (thread 0140), starting debugger... Attached Wine-7.0.4 backtrace information. For running with Wine-6.0.4 this patch is needed. https://bugs.winehq.org/show_bug.cgi?id=44931#c10 Installation needs to be done on Windows. Afterwards copy the folder onto the system running Wine. See also: https://bugs.winehq.org/show_bug.cgi?id=55494 -- 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 13

[Bug 55010] New: psapi:psapi_main - test_EnumProcessModulesEx() sometimes gets a 0 image size on Windows 8
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=55010 Bug ID: 55010 Summary: psapi:psapi_main - test_EnumProcessModulesEx() sometimes gets a 0 image size on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - test_EnumProcessModulesEx() sometimes gets a 0 image size on Windows 8: psapi_main.c:250: Test failed: pcs-3232: 0: image size was 0 psapi_main.c:250: Test failed: pcs-3232: 3: image size was 0 or psapi_main.c:250: Test failed: pcs-6432: 1: image size was 0 psapi_main.c:250: Test failed: pcs-6432: 3: image size was 0 or psapi_main.c:250: Test failed: pcs-6464: 2: image size was 0 psapi_main.c:250: Test failed: pcs-6464: 0: image size was 0 psapi_main.c:250: Test failed: pcs-6464: 3: image size was 0 See https://test.winehq.org/data/patterns.html#psapi:psapi_main There can be 1 to 3 failures independently of the bitness. -- 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 38780] New: AArch64 platforms: register X18 must remain reserved for Wine to run 64-bit ARM Windows applications (Distro aarch64 toolchains need '-ffixed-x18' default, loader/libc/userland)
by wine-bugs＠winehq.org Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=38780 Bug ID: 38780 Summary: AArch64 platforms: register X18 must remain reserved for Wine to run 64-bit ARM Windows applications (Distro aarch64 toolchains need '-ffixed-x18' default, loader/libc/userland) Product: Wine Version: 1.7.45 Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, split off from bug 38719 ("64-bit ARM Windows applications from Windows SDK for Windows 10 crash when accessing TEB/PEB members (AArch64 platform specific register X18 must be reserved for TEB)") Resolution is 'upstream' here, the Wine part is bug 38719 http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.… Chapter 5 "THE BASE PROCEDURE CALL STANDARD" --- quote --- The role of register r18 is platform specific. If a platform ABI has need of a dedicated general purpose register to carry interprocedural state (for example, the thread context) then it should use this register for that purpose. If the platform ABI has no such requirements, then it should use r18 as an additional temporary register. The platform ABI specification must document the usage for this register. Note Software developers creating platform independent code are advised to avoid using r18 if at all possible. Most compilers provide a mechanism to prevent specific registers from being used for general allocation; portable hand-coded assembler should avoid it entirely. It should not be assumed that treating the register as callee saved will be sufficient to satisfy the requirements of the platform. Virtualization code must, of course, treat the register as they would any other resource provided to the virtual machine. --- quote --- 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 37

[Bug 56152] New: "Script error: Handler not defined #FileIO" in "TKKG 1" (EN: Jennifer is Missing, DE: Katjas Geheimnis - Tivoli)
by WineHQ Bugzilla Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=56152 Bug ID: 56152 Summary: "Script error: Handler not defined #FileIO" in "TKKG 1" (EN: Jennifer is Missing, DE: Katjas Geheimnis - Tivoli) Product: Wine Version: 6.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Since wine-6.4 this application fails with this message: Script error: Handler not defined #FileIO This is visible since this commit: commit af74bd31229e0f065448253b248ec0cb3b51af26 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Tue Mar 2 18:52:44 2021 +0100 ntdll: Use syscall dispatcher to restore context in NtSetContextThread. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Unfortunately I am not able to revert this commit on current git. I think this is the problematic area of the executable: 004F12C9 push offset aXobglu32Dll ; "xobglu32.dll" 004F12CE call ds:LoadLibraryA 004F12D4 mov ebp, eax 004F12D6 test ebp, ebp 004F12D8 jz short loc_4F1309 004F12DA push offset aMyloadlibrary3 ; "MyLoadLibrary32" 004F12DF push ebp ; hModule 004F12E0 call ds:GetProcAddress 004F12E6 mov ecx, [esp+10h+arg_0] 004F12EA push ecx 004F12EB call eax 004F12ED movzx esi, ax 004F12F0 test esi, esi 004F12F2 jnz short loc_4F12FD 004F12F4 push ebp ; hLibModule 004F12F5 call ds:FreeLibrary 004F12FB jmp short loc_4F1309 004F12FD mov [ebx], esi Inside MyLoadLibrary32 it seems the application does a 16-bit KERNEL.95:LOADLIBRARY of fileio.dll, which looks like it succeeds (retval=00000306). Unfortunately for some reason the FreeLibrary is reached when it was not before the above commit. A +relay trace shows also a NtSetContextThread involved, which got modified by above commit. I tested with: - https://archive.org/details/tkkg-1-jennifer-is-missing - export WINEARCH=win32 - winecfg, set to Windows 95. - Workaround for following error: "This program requires at least 3MB of free virtual memory to run" echo -e "MemTotal: 32768 kB\nMemFree: 32768 kB\nSwapTotal: 32768 kB\nSwapFree: 32768 kB\nBuffers: 0\nCached: 0" > my-meminfo.txt bwrap --dev-bind / / --dev-bind my-meminfo.txt /proc/meminfo wine tkkg1_95.exe -- 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 47406] New: add support for debug symbols is separate files
by wine-bugs＠winehq.org Jan. 12, 2024

Jan. 12, 2024

https://bugs.winehq.org/show_bug.cgi?id=47406 Bug ID: 47406 Summary: add support for debug symbols is separate files Product: Wine Version: 4.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- <will be a bit ranty> One on the "installation options" on Gentoo is 'splitdebug'. It allows to keep debug symbols in separate files (and potentially keep them compressed). gdb supports it (AFAICT) seamlessly. While addr2line doesn't seem to supports it, the one from elfutils does. I don't know where Gentoo got the idea, but given gdb and elfutils, it's likely more wide-spread than Gentoo family. So, would you consider adding support for it in winedbg ? -- 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