wine-bugs

wine-bugs@winehq.org

1 participants
158777 discussions

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

19 Nov '24

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 19 Nov '24

19 Nov '24

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@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@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 19 Nov '24

19 Nov '24

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 55336] New: Touhou 6 : Full-screen with Alt-tabbing or using DXVK breaks inputs
by WineHQ Bugzilla 18 Nov '24

18 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=55336 Bug ID: 55336 Summary: Touhou 6 : Full-screen with Alt-tabbing or using DXVK breaks inputs Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: riyu12383(a)gmail.com Distribution: --- -The Game Here is a very small demo version of the game from archive.org https://archive.org/compress/KoumaTr013/formats=ARCHIVE%20BITTORRENT,METADA… To launch this version, you'll need to add Japanese locale like this : LANG=ja_JP.UTF-8 wine 東方紅魔郷.exe -The bug When launching the game in Full-screen and Alt-Tabbing or using DXVK, the game inputs breaks, its scrolls the menu infinitely or quit the game by itself, the user can't control anything anymore. On the demo version it seems the user only loose the control. Interestingly on Windows, since Windows 10, the game has an exaggerated speed/framerate in full-screen. Which was fixed using this dx8 to dx9 converter : http://enbdev.com/convertor_dx8_dx9_v0036.htm However this doesn't change anything with wine. I originally discovered this bug here : https://github.com/AlpyneDreams/d8vk/issues/155 -- 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 19

[Bug 52215] New: MSTSC (Remote Desktop) 7.0 cannot find its MUI files when Windows version is set to 7
by WineHQ Bugzilla 18 Nov '24

18 Nov '24

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 57007] New: Sequence Editor from Legendary Explorer of ME3Tweaks Mod Manager triggers GDI assert
by WineHQ Bugzilla 18 Nov '24

18 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57007 Bug ID: 57007 Summary: Sequence Editor from Legendary Explorer of ME3Tweaks Mod Manager triggers GDI assert Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: raulvior.bcn(a)gmail.com Distribution: --- Created attachment 76845 --> https://bugs.winehq.org/attachment.cgi?id=76845 Log generated with WINEDEBUG=warn Sequence Editor 6.4.18 from Legendary Explorer of ME3Tweaks Mod Manager 9.0 (Tools->Legendary Explorer) triggers assert from Wine code base "err:msvcrt:_wassert (L"graphics->hdc_refs == 0",L"dlls/gdiplus/graphics.c",2621)". Executing with WINEDEBUG=warn+heap shows the following warning "warn: Using GDI for swapchain presentation. This will impact performance." which belongs to https://github.com/doitsujin/dxvk/blob/master/src/d3d9/d3d9_swapchain.cpp#L… The assert is triggered when trying to add a BioSeqVar_StoryManagerX variable where X is one of {Bool,Float,Int,StateId}. I have not tried all other object types. But from the Variables tab it only crashes when double clicking in any of those four. The PCC file opened with the Sequence Editor can be downloaded here: https://drive.proton.me/urls/GSMNK9XPF8#MHMpgEs2uYHe You have to configure Wine to emulate a virtual desktop. Otherwise tooltips and menus appear as black rectangles. ### Software information Legendary Explorer 6.4.18 from ME3Tweaks Mod Manager 9.0. ### System information - GPU: AMD Radeon VII (RADV VEGA20) - Driver: radv 24.1.3 - Wine version: wine-9.13 ### Apitrace file(s) https://drive.proton.me/urls/DGQS3343J4#0BDgJCGU0pfz -- 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 6

[Bug 57420] New: Incorrect (broken) Japanese Font Substitution for Tahoma via FontLink
by WineHQ Bugzilla 18 Nov '24

18 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57420 Bug ID: 57420 Summary: Incorrect (broken) Japanese Font Substitution for Tahoma via FontLink Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- Created attachment 77410 --> https://bugs.winehq.org/attachment.cgi?id=77410 Left->FontLink,Right->FontSubstitutes When configuring the Tahoma font to use a Japanese fallback font via FontLink, issues arise with proper font substitution in Notepad++ and other applications. Here’s a summary of the issue: 1. A FontLink -> SystemLink registry key is added for Tahoma, which includes VL-Gothic-Regular.ttf,VL Gothic among other fonts. 2. The system locale is set to ja_JP.UTF-8. 3. Notepad++ (and other applications) is launched. Expected Behavior: The Japanese font should display correctly throughout the application interface. Actual Behavior: - In some parts in Notepad++ where using Tahoma font (e.g., menus), the Japanese font does not display correctly, though in other areas, like the settings window, it does. - We have verified this behavior in other applications, and the same issue is consistently observed. - Without linking to VL Gothic, the Japanese text in menus becomes completely unreadable. VL Gothic is used here as an example for a readable fallback font. Workaround: Adding a FontSubstitutes registry entry that maps Tahoma to VL Gothic Regular resolves the issue, and the correct font appears throughout the interface. Problem with the Workaround: This approach is not ideal because changing the system locale does not automatically update the FontSubstitutes entry. As a result, VL Gothic Regular remains set for Tahoma, which is undesirable in an English locale, for example. Additional Information: - Attached are screenshots showing correct and incorrect font rendering. - Tested on Wine 9.0 as well as the main branch, with consistent behavior in both versions. -- 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 57429] New: Wine fails to open a terminal window if a terminal application is invoked from the file manager
by WineHQ Bugzilla 18 Nov '24

18 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57429 Bug ID: 57429 Summary: Wine fails to open a terminal window if a terminal application is invoked from the file manager Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobi17spam(a)gmx.de Distribution: --- This is on Linux Mint. If Wine is invoked from the file manager (using an open action), on a windows terminal exe, it doesn't open a terminal on its own (like Windows would in such a situation). When run from an existing terminal, the executable is run as it should. -- 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 48641] New: skse64 is broken with the ntdll-ForceBottomUpAlloc patchset
by WineHQ Bugzilla 18 Nov '24

18 Nov '24

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 57099] New: Frosty Mod Manager opens up but apply nor launch the game.
by WineHQ Bugzilla 17 Nov '24

17 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=57099 Bug ID: 57099 Summary: Frosty Mod Manager opens up but apply nor launch the game. Product: Wine Version: 9.13 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tanvir.maht(a)outlook.com Frosty Mod Manager can be opened but you can’t apply mods and then launch the 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs