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

[Bug 40972] New: RtlVerifyVersionInfo returns wrong results
by wine-bugs＠winehq.org Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=40972 Bug ID: 40972 Summary: RtlVerifyVersionInfo returns wrong results Product: Wine Version: 1.9.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: marcinwiaz(a)poczta.onet.pl Distribution: --- Created attachment 55126 --> https://bugs.winehq.org/attachment.cgi?id=55126 Tiny test program - EXE and source (Note: this a different problem than in Bug 36143) Steps to reproduce: 1) Download and unpack Reproduce.exe, which is attached to this bug report 2) Configure Wine to emulate Windows 2003 (which has version number 5.2) for Reproduce.exe 3) Launch Reproduce.exe - you will see in the console window: CurrentOS is: 5.2 RequestedOS is >= than: 5.19 CurrentOS is < than RequestedOS (which is WRONG!) 4) Run true Microsoft Windows 2003 Server 5) Launch Reproduce.exe - you will see in the console window: CurrentOS is: 5.2 RequestedOS is >= than: 5.19 CurrentOS is >= than RequestedOS Explanation: Minor version numbers should be treated similarly to digits after a decimal point - so when comparing software versions: version 5.1 is < than version 5.2 version 5.11 is < than version 5.2 (note that 11 is > than 2 !) version 5.19 is < than version 5.2 (note that 19 is > than 2 !) So when comparing for VER_MINORVERSION or VER_SERVICEPACKMINOR inside the "VerifyVersionInfo" API, Microsoft uses a lexical comparison - which works as: lstrcmp(tostring(dwMinorVersion1),tostring(dwMinorVersion2)) or lstrcmp(tostring(wServicePackMinor1),tostring(wServicePackMinor2)) Please note, that it's still different than comparing real numbers, because: 5.20 = 5.2 but lstrcmp("5.20","5.2") != 0 So lstrcmp-like function must be used for VER_MINORVERSION and VER_SERVICEPACKMINOR checking inside the "RtlVerifyVersionInfo" function (which is called by the "VerifyVersionInfo" API in Wine) to be compatible with Microsoft Windows. Possible fix: in "version.c" file, add a new "version_compare_values_lexical" function. It should be based on the original "version_compare_values" function, but should use "lstrcmp" calls instead of integer comparisons. This "version_compare_values_lexical" function should be called instead of "version_compare_values" when checking for VER_MINORVERSION and VER_SERVICEPACKMINOR inside the "RtlVerifyVersionInfo" function. -- 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 5

[Bug 49828] New: MSVC 2019 executables with ASAN enabled fail to start
by WineHQ Bugzilla Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=49828 Bug ID: 49828 Summary: MSVC 2019 executables with ASAN enabled fail to start Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nyanpasu64(a)tuta.io Distribution: --- Recent versions of MSVC allow building Windows .exes with ASAN (it may have already been possible using Clang.): https://devblogs.microsoft.com/cppblog/addresssanitizer-asan-for-windows-wi… I took an old Win32/MFC application and built it using MSVC ASAN on Windows 10, to try to discover memory bugs on Windows and Wine. - Program download at https://cdn.discordapp.com/attachments/653168829891084298/75454092297227479… . - Source at https://github.com/nyanpasu64/Dn-FamiTracker/tree/b3ba802f (permalink at https://cdn.discordapp.com/attachments/653168829891084298/75454082852061186… ). - To build, copy cmake_user_begin.cmake.example to cmake_user_begin.cmake, then run CMake in MSVC 32-bit Release mode. It may be possible using Visual Studio's .json file or msbuild, but I haven't tried yet. On Windows, the program starts without problems. On wine-5.17, when I try to run this program, it crashes during the loading process. nyanpasu64(a)dell-arch ~/apps> wine Dn_FamiTracker_ASAN.exe 0024:fixme:ntdll:EtwEventRegister ({6c6c766d-3846-4e6a-a4fb-5b530bd0f3fa}, 00401030, 00884590, 008845A8) stub. 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0084A41C, 34) stub ==32==AddressSanitizer CHECK failed: D:\agent\_work\3\s\src\vctools\crt\asan\llvm\compiler-rt\lib\asan\asan_rtl.cc:401 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) <empty stack> `winedbg Dn_FamiTracker_ASAN.exe` doesn't work, it gets stuck on `0x00000000005c9701 EntryPoint+0xffffffffffffffff in dn_famitracker_asan: ret`. If I instead `winedbg --gdb Dn_FamiTracker_ASAN.exe`, I get a pile of identical SIGTRAP with different backtraces. These are non-fatal and can be continued. I think these correspond to asan errors that would normally terminate the program, but unfortunately it doesn't print log messages when running in winedbg. I don't know how to fix that. 0x005c9701 in _sanitizer_print_stack_trace () from /home/nyanpasu64/.wine/dosdevices/z:/home/nyanpasu64/apps/Dn_FamiTracker_ASAN.exe The last SIGTRAP is different: 0x7bc52379 in DbgBreakPoint(a)0 () from /home/nyanpasu64/.wine/dosdevices/c:/windows/syswow64/ntdll.dll Afterwards the program starts. (It used to crash, but works with lib32-libpulse and lib32-mpg123 installed, unsure if that's why.) -- 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 15

[Bug 43262] New: Drag&Drop not working between wine explorer and other applications
by wine-bugs＠winehq.org Nov. 19, 2024

Nov. 19, 2024

https://bugs.winehq.org/show_bug.cgi?id=43262 Bug ID: 43262 Summary: Drag&Drop not working between wine explorer and other applications Product: Wine Version: 2.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mintos(a)discard.email Distribution: --- https://pastebin.com/39uSnrR7 console output -- 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 52215] New: MSTSC (Remote Desktop) 7.0 cannot find its MUI files when Windows version is set to 7
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=52215 Bug ID: 52215 Summary: MSTSC (Remote Desktop) 7.0 cannot find its MUI files when Windows version is set to 7 Product: Wine Version: 7.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 71279 --> https://bugs.winehq.org/attachment.cgi?id=71279 Error. File not found. C:\windows\system32\<LANG_NAME>\mstsc.exe.MUI A workaround is to set the Windows version to XP but I don't like it because Wine as far as I know doesn't allow to set a per application Windows version and my default Windows version is set to 7. strace shows that Wine doesn't even attempt to find MUI files as if some resolution inside it breaks completely when Windows != XP. -- 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 48641] New: skse64 is broken with the ntdll-ForceBottomUpAlloc patchset
by WineHQ Bugzilla Nov. 18, 2024

Nov. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=48641 Bug ID: 48641 Summary: skse64 is broken with the ntdll-ForceBottomUpAlloc patchset Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- While SKSE64 now works properly under wine, it hangs (then fails to launch) when the ntdll-ForceBottomUpAlloc patchset is enabled. Building wine-staging without that specific patchset works fine. This is similar to how it was in earlier wine versions, before a better version of the F4SE patches (https://github.com/hdmap/wine-hackery/tree/master/f4se) were mainlined. -- 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 14

[Bug 54114] New: Cyberworld Browser: "Could not resolve 'intro_default.url'"
by WineHQ Bugzilla Nov. 17, 2024

Nov. 17, 2024

https://bugs.winehq.org/show_bug.cgi?id=54114 Bug ID: 54114 Summary: Cyberworld Browser: "Could not resolve 'intro_default.url'" Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: doomtay(a)gmail.com Distribution: --- Created attachment 73649 --> https://bugs.winehq.org/attachment.cgi?id=73649 Example files https://web.archive.org/web/20020808051830id_/http://www.cyberworldcorp.com… Cyberworld Browser Installer When opening up "intro.borg" in the sample zip, I expect both the large web panel and side panel to change. Instead, I get a black screen and the message "Could not resolve 'intro_default.url'" at the bottom -- 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 2

[Bug 30615] New: Audition CS6 (5.0) - strange UI graphics
by wine-bugs＠winehq.org Nov. 17, 2024

Nov. 17, 2024

http://bugs.winehq.org/show_bug.cgi?id=30615 Bug #: 30615 Summary: Audition CS6 (5.0) - strange UI graphics Product: Wine Version: 1.5.3 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jan(a)lugfl.de Classification: Unclassified Created attachment 40072 --> http://bugs.winehq.org/attachment.cgi?id=40072 Audition CS6 Mixer screenshot The UI looks very strange. Results with native and buildin gdiplus looks identical. see attached screenshot. A log of the console output is attached too. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 26

[Bug 43670] New: MsPaint from Win7 does not start
by wine-bugs＠winehq.org Nov. 16, 2024

Nov. 16, 2024

https://bugs.winehq.org/show_bug.cgi?id=43670 Bug ID: 43670 Summary: MsPaint from Win7 does not start Product: Wine Version: 2.16 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- First you need a 32bit copy of mspaint from a win7 machine. You'll also need "winetricks mfc42". Program fails with a messagebox: "Failed to create empty document" -- 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 20

[Bug 54511] New: Cygwin installer hangs during postprocessing step
by WineHQ Bugzilla Nov. 15, 2024

Nov. 15, 2024

https://bugs.winehq.org/show_bug.cgi?id=54511 Bug ID: 54511 Summary: Cygwin installer hangs during postprocessing step Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Install seems to go fine, but in the end it hangs when running C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash" Both wineserver and dash.exe use about half a cpu core each, but nothing seems to happen. Comparing it to windows, that step should be fast. Cygwin used to install fine, but even when downgrading wine I can't seem to get it to work, it all shows the same issue. So it's probably not a Wine regression. -- 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 52159] New: 64-bit cygwin gdb.exe and python3.8.exe fail to run
by WineHQ Bugzilla Nov. 15, 2024

Nov. 15, 2024

https://bugs.winehq.org/show_bug.cgi?id=52159 Bug ID: 52159 Summary: 64-bit cygwin gdb.exe and python3.8.exe fail to run Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 71205 --> https://bugs.winehq.org/attachment.cgi?id=71205 details.txt This issue can be seen if the workarounds for bug #47808 got applied first. Both gdb.exe and python3.8.exe fail in the python initialisation. As far as I see it python allocates 8 bytes for a sem_t structure. This uninitialized struct is given to sem_init which checks if this is a previously initialized semaphore by checking with verifyable_object_isvalid. This check happens inside a __try/__endtry [2] [3]. That way we end up in RtlUnwindEx, which inspects NtCurrentTeb()->Tib.ExceptionList. Unfortunately this list finally contains a pointer to the initial stack, which cygwin deallocated before [1]. See details.txt. -- 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