wine-bugs April 2025

wine-bugs@winehq.org

1 participants
116 discussions

[Bug 57713] New: Tom Clancy's Rainbow Six: Lockdown leads to a black screen on launch
by WineHQ Bugzilla 08 Apr '25

08 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=57713 Bug ID: 57713 Summary: Tom Clancy's Rainbow Six: Lockdown leads to a black screen on launch Product: vkd3d Version: 1.14 Hardware: x86-64 URL: https://www.moddb.com/games/tom-clancys-rainbow-six-lo ckdown/downloads/rainbow-six-lockdown-demo OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Continuation of bug 56855. 0024:err:d3dcompiler:D3DCompile2 c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/shaders/vsdiffusepmsmsemdynlit.hlsl:499:20: W5300: Implicit truncation of vector type. 0024:err:d3dcompiler:D3DCompile2 c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/shaders/vsdiffusepmsmsemdynlit.hlsl:549:25: W5300: Implicit truncation of vector type. 0024:err:d3dcompiler:D3DCompile2 c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/shaders/vsdiffusepmsmsemdynlit.hlsl:550:25: W5300: Implicit truncation of vector type. 0024:err:d3dcompiler:D3DCompile2 ... 0024:err:d3dcompiler:D3DCompile2 c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/shaders/skinfragments.hlsl:510:20: W5300: Implicit truncation of vector type. 0024:err:d3dcompiler:D3DCompile2 c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/shaders/skinfragments.hlsl:632:6: W5300: Implicit truncation of vector type. 0024:err:d3dcompiler:D3DCompile2 c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/shaders/skinfragments.hlsl:666:22: W5300: Implicit truncation of vector type. 0024:err:d3dcompiler:D3DCompile2 vkd3d:0024:fixme:fold_cast Cast from float to float4. vkd3d:0024:fixme:fold_cast Cast from float to float3. 1.14-325-g5bfcd811 -- 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 58073] New: Pager: Incorrect PGM_RECALCSIZE behaviour
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=58073 Bug ID: 58073 Summary: Pager: Incorrect PGM_RECALCSIZE behaviour Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 78327 --> https://bugs.winehq.org/attachment.cgi?id=78327 Win11 Correct rendering See https://jira.reactos.org/browse/CORE-7017 App tested: https://github.com/katahiromz/BeginBar/releases/tag/1.0 Code of the app: https://github.com/katahiromz/BeginBar After installing, run the app, it will create a Taskbar. It begins in "Horizontal" mode. Right click on it, change it to "Vertical" mode. In Windows, changing to "Vertical" mode means that the Taskbar has now a width equal to button "Begin" width and a new height based on Desktop height. In Ubuntu/Wine, when changing to "Vertical" mode a problem happens: 1)The new width is equal to the Horizontal width. -->Bug 2)The height is correctly calculated. --->Correct Proposal fix: https://github.com/reactos/reactos/pull/7875 -- 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 58072] New: LVSCW_AUTOSIZE does not include the size of the state imagelist
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=58072 Bug ID: 58072 Summary: LVSCW_AUTOSIZE does not include the size of the state imagelist Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 78326 --> https://bugs.winehq.org/attachment.cgi?id=78326 TweakUI Wine 10.5 See: https://jira.reactos.org/browse/CORE-20080 https://jira.reactos.org/browse/CORE-15423 TweakUI v2 sets LVS_NOCOLUMNHEADER and uses a custom state image list and a normal image list causing the text of items to be cut off with no way to adjust it. Size calculation checks for LVS_EX_CHECKBOXES instead of the size of the state imagelist when calculating the size of column 0. Fix proposal: https://github.com/reactos/reactos/pull/7873 -- 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 49802] New: Crash at AfxBeginThread of x64 apps on macOS when built with VS2019
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=49802 Bug ID: 49802 Summary: Crash at AfxBeginThread of x64 apps on macOS when built with VS2019 Product: Wine Version: 5.16 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: reinhold.hoffmann(a)hotmail.com Created attachment 68117 --> https://bugs.winehq.org/attachment.cgi?id=68117 Samples to demonstrate the issue Our x64 apps built with Visual Studio 2010 (VS2010) run on macOS for a long time. We recently have started a project to move to Visual Studion 2019 (VS2019). The same x64 app which works fine when built with VS2010 crashes on macOS when it is built with VS2019. The crash occurs when the MFC function AfxBeginThread is called. Static linking is used for linking the MFC and other libs. After a very painful research we identified that a simular report has been made in Nov. 2019 in the Wineskin area (see https://github.com/Gcenx/WineskinServer/issues/22). The reporter said "I ended up replacing the AfxBeginThread call with a call to CreateThread which works fine on all versions." We did the same thing with the same result. Replacing AfxBeginThread by CreateThread works fine with VS2019. However, according to https://stackoverflow.com/questions/21718674/difference-between-afxbeginthr… a replacement of AfxBeginThread by CreateThread is not really recommended when MFC is used. The crash happens on all macOS versions with Wine 5.4, 5.7 and 5.16 (we took 5.16 from Gcenx (https://github.com/Gcenx/macOS_Wine_builds)). On Windows and Linux the VS2019 app runs fine. Further, the Win32 equivalent app runs fine on macOS. In summary: A crash happens for AfxbeginThread in an x64 app on macOS with Wine 5.4, 5.7, 5.16. We did a deeper dive and found that the crash happens inside AfxbeginThread, module Thread.cpp inside the function __acrt_get_begin_thread_init_policy. See address: 0001:001ab7cc __acrt_get_begin_thread_init_policy 00000001401ac7cc f libucrt:win_policies.obj According to the backtrace.txt (attached) the exception happens when reading from a 32 bit address. This sounds strange to me for a x64 app. Any help is highly appreciated. Reinhold ========================================================================== As a C++ sample I have compiled a trivial app which AfxBeginThread which demonstrate the problem. In the attached zip file you can find backtrace.txt Test_of_AfxBeginThread_VS2019.exe Test_of_AfxBeginThread_VS2010.exe The code and project files for VS2010 and VS2019 can be downloaded from www.notation.com/download/Wine/Bugzilla/Project_Files_AfxBeginThread_sample… -- 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 51575] New: Texconv fails with mipmap error unless "-nowic" is supplied to disable WIC use
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=51575 Bug ID: 51575 Summary: Texconv fails with mipmap error unless "-nowic" is supplied to disable WIC use Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: windowscodecs Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)63bit.net Distribution: --- Texconv.exe returns mysterious errors about mipmaps if "-nowic" is not passed. This appears to be some problem in the interaction between windowscodecs.dll and texconv mipmap level detection. Example (probably any DDS will work to repro): Texconv.exe -nologo -y -sepalpha -f BC7_UNORM -bc q -o "C:\blah\out" "C:\blah\TamrielTreeLod.dds" returns FAILED [mipmaps] (80070057: Invalid parameter.) Source for texconv is here: https://github.com/microsoft/DirectXTex/blob/54ce2c8da97c3508899c31f80bfb1e… Binary is available here: https://github.com/microsoft/DirectXTex/releases/tag/aug2021 Passing "-nowic" parameter succeeds, causing me to suspect windowscodecs.dll -- 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 39453] New: Graphs not rendering using gdiplus
by wine-bugs＠winehq.org 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=39453 Bug ID: 39453 Summary: Graphs not rendering using gdiplus Product: Wine Version: 1.7.52 Hardware: x86 OS: other Status: UNCONFIRMED Severity: minor Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: ldv1452(a)gmail.com Created attachment 52566 --> https://bugs.winehq.org/attachment.cgi?id=52566 Comparison builtin gdiplus vs native gdiplus Certain graphs (e.g. box plots) and graph components (e.g. axes) are not rendered while using builtin gdiplus. This happens irrespective of the OS and is solved when using native gdiplus (see attached examples). The problem can be observed using this software: https://sourceforge.net/projects/fruits/files/FRUITS2_installer.msi/download a file needs to be loaded and run (by pressing Estimate in the software) to generate the graphs: https://sourceforge.net/projects/fruits/files/simple_CN_model.frt/download I created the software (using Visual Studio). If requested I can provide the source code. -- 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 18

[Bug 36917] New: Synthmasters fails to draw correctly
by wine-bugs＠winehq.org 07 Apr '25

07 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=36917 Bug ID: 36917 Summary: Synthmasters fails to draw correctly Product: Wine Version: 1.7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: bique.alexandre(a)gmail.com Created attachment 49028 --> http://bugs.winehq.org/attachment.cgi?id=49028 Screenshot Synthmaster is a Windows VST (synthesizer). I use it along with vst-bridge and renoise. https://github.com/abique/vst-bridge http://renoise.com/ It fails to render correctly, and I think that it is related to the following lines: fixme:wincodecs:PngDecoder_Block_GetCount stub fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipDrawPath graphics object has no HDC fixme:gdiplus:resample_bitmap_pixel Unimplemented interpolation 7 Is it an issue coming from wine or SynthMaster? Thanks! -- 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 19

[Bug 57239] New: Tearing doesn't work when the window is in full screen
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=57239 Bug ID: 57239 Summary: Tearing doesn't work when the window is in full screen Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: artewar6767(a)gmail.com Distribution: --- If run the application in full screen with wayland driver then the screen tearing rule is not accepted by the window. I tested on Hyprland and KDE Plasma. -- 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 58067] New: [Regression] comctl32/edit: Unable to enter values in Adobe Lightroom Classic 10.4
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=58067 Bug ID: 58067 Summary: [Regression] comctl32/edit: Unable to enter values in Adobe Lightroom Classic 10.4 Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: bugs(a)bzatek.net CC: bunglehead(a)gmail.com Regression SHA1: d18a1fded2e2024ae2c8cdc4235654ff2d8dd5e9 Distribution: --- Created attachment 78320 --> https://bugs.winehq.org/attachment.cgi?id=78320 the tool on mouseover bug 56108 resp. https://gitlab.winehq.org/wine/wine/-/merge_requests/7606 has broken ability to enter values in some of the edit boxes in Adobe Lightroom Classic 10.4. Reverting the two mentioned changes fixes the issue. FWIW, Adobe often modifies widget look and behaviour. In this case the particular tool's value looks like a label, clicking and dragging the label will change value of the slider on the left. Single click will turn the label into an edit, which then acts normally - enter letters and numbers, either confirm by the Enter key or cancel by the Escape key. Tested against wine-10.5 -- 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 57954] New: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device
by WineHQ Bugzilla 07 Apr '25

07 Apr '25

https://bugs.winehq.org/show_bug.cgi?id=57954 Bug ID: 57954 Summary: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- Created attachment 78201 --> https://bugs.winehq.org/attachment.cgi?id=78201 wd-winedbg 10.2 seems to work fine, 10.3 gives an error about rawinput and the splash screen that should have the main character and game title is a black box and hangs using wow64 build, other 32bit games seem to work fine. running with WINEDBEUG ends in multiple varying lines of `0158:warn:rawinput:add_device Failed to open device file L"\\??\\HID#some-device-name#{hex-hash-id}", status 0xc0000034.` -- 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

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 April 2025