wine-bugs April 2022

wine-bugs@winehq.org

1 participants
3554 discussions

[Bug 52466] New: Toolbar: Wrong size returned by TB_GETMAXSIZE message for toolbars with TBSTYLE_WRAPABLE style
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52466 Bug ID: 52466 Summary: Toolbar: Wrong size returned by TB_GETMAXSIZE message for toolbars with TBSTYLE_WRAPABLE style Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: yal(a)csoftcom.com Distribution: --- Under Windows (I've tested Win10/11) TB_GETMAXSIZE always returns size for single row of buttons regardless of wrapped it or not. WINE calculates size for current wrapping. For example: under Win toolbar with initial size (0,0) and 2 buttons (20,20) TB_GETMAXSIZE always returns(40,20), WINE returns (20,40) - 2 rows wrapping. -- 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 52728] New: wine-7.5 build fails in Ubuntu 18.04
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52728 Bug ID: 52728 Summary: wine-7.5 build fails in Ubuntu 18.04 Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- Created attachment 72087 --> https://bugs.winehq.org/attachment.cgi?id=72087 Ubuntu 18.04 failed build log All the other builds were fine, but it failed in winealsa.drv in Ubuntu 18.04 [ 2042s] dlls/winealsa.drv/alsamidi.c:117:8: error: unknown type name 'uint64_t' [ 2042s] static uint64_t get_time_msec(void) [ 2042s] ^~~~~~~~ [ 2042s] dlls/winealsa.drv/alsamidi.c: In function 'get_time_msec': [ 2042s] dlls/winealsa.drv/alsamidi.c:123:17: error: 'uint64_t' undeclared (first use in this function); did you mean 'u_int64_t'? [ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000; [ 2042s] ^~~~~~~~ [ 2042s] u_int64_t [ 2042s] dlls/winealsa.drv/alsamidi.c:123:17: note: each undeclared identifier is reported only once for each function it appears in [ 2042s] dlls/winealsa.drv/alsamidi.c:123:26: error: expected ';' before 'now' [ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000; [ 2042s] ^~~ [ 2042s] dlls/winealsa.drv/alsamidi.c:126:22: error: expected ';' before 'now' [ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000; [ 2042s] ^~~ [ 2042s] dlls/winealsa.drv/alsamidi.c:127:1: warning: control reaches end of non-void function [-Wreturn-type] [ 2042s] } [ 2042s] ^ [ 2042s] Makefile:130009: recipe for target 'dlls/winealsa.drv/alsamidi.o' failed [ 2042s] make[1]: *** [dlls/winealsa.drv/alsamidi.o] Error 1 -- 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

[Bug 52698] New: JW Scheduler installer fails to start: "Requires Microsoft .NET Framework 4.5.2"
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52698 Bug ID: 52698 Summary: JW Scheduler installer fails to start: "Requires Microsoft .NET Framework 4.5.2" Product: Wine Version: 7.4 Hardware: x86-64 URL: https://jwscheduler.com/jw-christian-life-ministry-mee ting-scheduler/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- It checks for the reg key DWORD HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v4\Full\Servicing which is not present. After manually creating it, the app installs and starts for me I guess this should be fixed in Mono (?) -- 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 52658] New: Swisslog
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52658 Bug ID: 52658 Summary: Swisslog Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kvradio(a)seznam.cz Distribution: --- EndeavourOS Wine 7.4-1 Swisslog http://www.swisslogforwindows.com/download.html has stopped working and freezes logo on startup.. No error displayed. Version 7.3 and earlier works very well (If I try to replace the folder /usr/lib32/wine from 7.3 package works 7.4 again) -- 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

[Bug 52660] New: chunk allocator for GL uniform buffers kills performance in World of Warships
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52660 Bug ID: 52660 Summary: chunk allocator for GL uniform buffers kills performance in World of Warships Product: Wine Version: 7.4 Hardware: x86-64 URL: https://worldofwarships.eu/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: janbraun(a)gmx.net Regression SHA1: 86f0ae8efb17ce688986971d24c3e25840a2beef Distribution: --- I've found and bisected a huge performance regresssion in World Of Warships: With 86f0ae8efb17ce688986971d24c3e25840a2beef "wined3d: Use the chunk allocator for GL uniform buffers." applied, my framerate is around 18-20fps during gameplay. With that patch reverted, it's back at >=60fps. The code moved around in the meantime, but simply commenting out the "case GL_UNIFORM_BUFFER:" in use_buffer_chunk_suballocation() restores performance on wine 7.4 (= current git HEAD) as well. I have the subjective impression that other games might be affected too (things feel a bit more sluggy), but certainly nowhere as severely as WoWS. I didn't further test/benchmark, however, because WoWS was such a nice reproducer. Running mesa-21.3.7 on amdgpu. Please holler if you need more info. -- 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 52638] New: The 64-bit winmm:mci fails and crashes in test_openCloseWAVE() in Wine
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52638 Bug ID: 52638 Summary: The 64-bit winmm:mci fails and crashes in test_openCloseWAVE() in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit winmm:mci crashes in test_openCloseWAVE() in Wine: mci.c:389: Test failed: mci sysinfo all quantity returned MCIERR_UNRECOGNIZED_COMMAND mci.c:398: Test failed: sysinfo all quantity string and command differ Unhandled exception: page fault on read access to 0x000000000000020d in 64-bit code (0x00000000709b9ca1). [...] Backtrace: =>0 0x00000000709b9ca1 _wcsicmp_l+0x91(str1=*** Invalid address 0x0000000000000002 *** Internal symbol error: unable to access memory location 0000000000000002, str2=*** Invalid address 0x0000000000000000 *** Internal symbol error: unable to access memory location 0000000000000000, locale=000000000064E980) [Z:\home\winetest\winetest\src\dlls\msvcrt\wcs.c:132] in ucrtbase (0x000000000004dd50) 1 0x00000000709b9d6c _wcsicmp+0xc(str1=<internal error>, str2=<internal error>) [Z:\home\winetest\winetest\src\dlls\msvcrt\wcs.c:158] in ucrtbase (0x00000000709b9d60) 2 0x0000000000bf8057 MCI_FindCommand+0x38(s2=<internal error>, s1=<internal error>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:946] in winmm (0x00000000709b9d60) 3 0x0000000000bf8057 MCI_FindCommand+0x67(uTbl=<internal error>, verb=<register RDI not accessible in this frame>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:938] in winmm (0x00000000709b9d60) 4 0x0000000000bfbcc7 mciSendStringW+0xc57(lpstrCommand=<internal error>, lpstrRet=[<register RSP not accessible in this frame>, uRetLen=[<register RSP not accessible in this frame>, hwndCallback=[<register RSP not accessible in this frame>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:1460] in winmm (0x00000000003e0000) https://test.winehq.org/data/patterns.html#winmm:mci This only happens with the 64-bit build but as far as I can tell it is systematic and impacts all machines. A bisect pointed to the following commit as the trigger: commit 7c76aa05a9d27dd6f5705c4ef90c16862af14f3e Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Mar 7 14:42:32 2022 +0100 win32u: Move class management implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52340] New: wine-mono + RMS Express: COM Port errors connecting to radios
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52340 Bug ID: 52340 Summary: wine-mono + RMS Express: COM Port errors connecting to radios Product: Wine Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: eric.wheez(a)gmail.com Distribution: --- Hello again, I just wanted to report in a "not implemented" exception in wine-mono. I believe that "System.IO.Ports.SerialPort.set_ReceivedBytesThreshold" not implemented in wine-mono is causing RMS Express to not be able to control the radio (channel selection and "push-to-talk"/"PTT" switch) over USB connection. Normal behavior is for RMS Express to tell the radio what radio channel to send/receive on & when to transmit/listen (via PTT switch). This behavior is working on RMS Express via Windows. This behavior is also working with RMS Express on Debian 10 VM with wine & .NET 4.6 (I had to set `sudo adduser $USER dialout && sudo reboot` to set permissions for the COM port for the user account so before channels/PTT worked .NET 4.6 though). The not implemented exception pops up in the linux terminal with wine-mono exactly at the same time that the (known-working-with-.NET4.6) COM port is said to be inaccessible. I've included the short log of the wine-mono not implemented exception at the of this post. [Setup] OS: Debian 10 (VMware Workstation on a Windows laptop) Wine: wine-7.0-rc4 devel Wine Mono: wine-mono 2f50d2c (https://nightly.link/madewokherd/wine-mono/actions/artifacts/131614059.zip) Program: Winlink Express 1.5.44.0 Radio: Yaesu FT-891 transceiver (with dummyload attached directly to radio - no feed line so I don't accidentally send signals) Details: - FT-891 connected to PC via USB cable (and make sure VMWare has the USB line routed into the VM instead of the host PC) - I set the FT-891's on-board settings to data 'baud' 9600. - I set in/out audio devices in ARDOP settings on the PC. Thank you again! And here's to 2022 being better than the previous two years :) Cheers ---- wine-mono not implemented exception log: ``` WINE_MONO_TRACE=E:System.MissingMethodException MONO_INLINELIMIT=0 WINE_MONO_HIDETYPES=1 wine RMS\ Express.exe ... [00000024:] EXCEPTION handling: System.NotImplementedException: The method or operation is not implemented. "<unnamed thread>" tid=00000024 this=04570120 , thread handle : 01df5788, state : not waiting at System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x0000f] in <117354a27af94c36af91c072a84e6fb8>:0 at (wrapper remoting-invoke-with-check) System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x00032] in <117354a27af94c36af91c072a84e6fb8>:0 at RMS_Express.Radio.OpenControlPort () [0x000b3] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Radio.SetRadio () [0x0014f] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Radio.SetFrequency (int,string) [0x00021] in <25c56d5497bc4490bd1b5395b173c5df>:0 at (wrapper remoting-invoke-with-check) RMS_Express.Radio.SetFrequency (int,string) [0x00033] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.ArdopSession.Ardop_Activated (object,System.EventArgs) [0x00823] in <25c56d5497bc4490bd1b5395b173c5df>:0 at System.Windows.Forms.Form.OnActivated (System.EventArgs) [0x0001f] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.set_Active (bool) [0x000a6] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.WmActivate (System.Windows.Forms.Message&) [0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message&) [0x001b8] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00025] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.SafeNativeMethods.ShowWindow (System.Runtime.InteropServices.HandleRef,int) <0x00012> at System.Windows.Forms.Control.SetVisibleCore (bool) [0x00061] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.SetVisibleCore (bool) [0x000d1] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.set_Visible (bool) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.Show () [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at RMS_Express.ArdopSession.ShowSession () [0x00000] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Main.StartSession () [0x005fd] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Main.mnuSession_Click (object,System.EventArgs) [0x00000] in <25c56d5497bc4490bd1b5395b173c5df>:0 at System.Windows.Forms.ToolStripItem.RaiseEvent (object,System.EventArgs) [0x0001b] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs) [0x0001d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.HandleClick (System.EventArgs) [0x00051] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.HandleMouseUp (System.Windows.Forms.MouseEventArgs) [0x000fd] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.FireEventInteractive (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00053] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00103] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00033] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStrip.OnMouseUp (System.Windows.Forms.MouseEventArgs) [0x0007d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.WmMouseUp (System.Windows.Forms.Message&,System.Windows.Forms.MouseButtons,int) [0x001c3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message&) [0x005a0] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message&) [0x00043] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message&) [0x00128] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.MenuStrip.WndProc (System.Windows.Forms.Message&) [0x00056] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00025] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW (System.Windows.Forms.NativeMethods/MSG&) <0x00012> at System.Windows.Forms.Application/ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop (intptr,int,int) [0x001d7] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoopInner (int,System.Windows.Forms.ApplicationContext) [0x00282] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x00033] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext) [0x00006] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun () [0x00044] in <e344caf534bf4ffb982376a141ed987b>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel () [0x00035] in <e344caf534bf4ffb982376a141ed987b>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run (string[]) [0x0001b] in <e344caf534bf4ffb982376a141ed987b>:0 at RMS_Express.My.MyApplication.Main (string[]) [0x0000f] in <25c56d5497bc4490bd1b5395b173c5df>:0 at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) [0x00027] in <25c56d5497bc4490bd1b5395b173c5df>:0 ``` -- 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 42309] New: The Crew (Uplay) crashes at start
by wine-bugs＠winehq.org 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=42309 Bug ID: 42309 Summary: The Crew (Uplay) crashes at start Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 57043 --> https://bugs.winehq.org/attachment.cgi?id=57043 Unhandled page fault read access to 0x0 in 64-bit code backtrace After the loading screen has closed, the screen goes black and then wine crashes with a read access to 0x00000000 in 64-bit code. The terminal is also filled with DirectX 11 fixme's. Tested on wine 2.0 + staged patch from bug 41356. -- 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 21

[Bug 52722] New: Winetricks dotnet installation hangs at wineserver -w
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52722 Bug ID: 52722 Summary: Winetricks dotnet installation hangs at wineserver -w Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: tatidev1454(a)protonmail.com Distribution: --- Created attachment 72082 --> https://bugs.winehq.org/attachment.cgi?id=72082 Logs of the affected function create_surrogate_server with 32 bits wine and WoW64 This bug only happens with 13064f991408ea5fa5e999705b13bda7bbd50e5b commit. 1. Run `winetricks dlls dotnet45` having a 32 bits build of wine in the PATH (or any other dotnet version which requires the installation of an older one) 2. Wait until dotnet40 installs. 3. Winetricks executes wineserver -w and it just hangs there. -- 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 52721] New: d3dx9_36:effect, d3dx11_42:d3dx11 and d3dx11_43:d3dx11 broken by use of vkd3d_shader_compile() for D3DCompile2()
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52721 Bug ID: 52721 Summary: d3dx9_36:effect, d3dx11_42:d3dx11 and d3dx11_43:d3dx11 broken by use of vkd3d_shader_compile() for D3DCompile2() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A recent patch to use vkd3d_shader_compile() to implement D3DCompile2() broke d3dx11_42:d3dx11 and d3dx11_43:d3dx11. In both cases it leads to a crash: d3dx11.c:580: Test failed: Got unexpected errors. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x70bb0990). [...] Backtrace: =>0 0x70bb0990 strrchr+0x10(str=0x000000000, c=0x5c) [Z:\home\winetest\winetest\src\dlls\msvcrt\string.c:3166] in ucrtbase (0x0031d9b8) 1 0x69d8bcc9 d3dcompiler_include_from_file_open+0x49(iface=<internal error>, include_type=<internal error>, filename=<internal error>, parent_data=<internal error>, data=<internal error>, bytes=<internal error>) [Z:\home\winetest\winetest\src\dlls\d3dcompiler_43\compiler.c:521] in d3dcompiler_47 (0x0031db28) https://test.winehq.org/data/patterns.html#d3dx11_42:d3dx11 https://test.winehq.org/data/patterns.html#d3dx11_43:d3dx11 d3dx9_36:effect got broken too but at least in this case it's because of successes in todos so it's probably a trivial fix: effect.c:8108: Test succeeded inside todo block: Unexpected error, hr 0x80004005. effect.c:8133: Test succeeded inside todo block: D3DXInclude test failed with error 0x80004005. https://test.winehq.org/data/patterns.html#d3dx9_36:effect The commit that caused these new failures is: commit 6a062afb75c1e026614403312f2e13207e359634 (HEAD, refs/bisect/bad) Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Thu Mar 3 20:25:26 2022 -0600 d3dcompiler: Implement D3DCompile2() using vkd3d_shader_compile(). Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51713 Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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

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