June 2025 - Wine-Bugs - list.winehq.org

Solar Powered GPS Tracking devices

by Lora

June 5, 2025

[Bug 58328] New: "msvcrt: Use RVAs in rtti and exception data on all platforms except i386" breaks RTTI on arm32

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58328 Bug ID: 58328 Summary: "msvcrt: Use RVAs in rtti and exception data on all platforms except i386" breaks RTTI on arm32 Product: Wine Version: 9.10 Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st CC: julliard(a)winehq.org Regression SHA1: a794b0224e27f91bf0855cd7376d6af3de44523d Distribution: --- Created attachment 78697 --> http://bugs.winehq.org/attachment.cgi?id=78697 Repro binary Since a794b0224e27f91bf0855cd7376d6af3de44523d, "msvcrt: Use RVAs in rtti and exception data on all platforms except i386", a dynamically linked executable that uses msvcp140.dll and vcruntime140.dll, crashes on startup on 32 bit arm. The corresponding case seems to run fine on arm64 though. -- 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.

June 5, 2025

[Bug 57950] Metatrader refuses to run/install

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57950 --- Comment #14 from Alexandre Julliard <julliard(a)winehq.org> --- (In reply to Aleksandar Petrinic from comment #13) > (In reply to Alexandre Julliard from comment #11) > > Duplicate resolution was lost by Anubis... > > > > *** This bug has been marked as a duplicate of bug 58043 *** > > I see you have marked this bug as the duplicate of the other bug, I checked > that as well and its solution to set by winecfg to Windows 11 didn't work > for mt4 installer. Is this expected even if the bug is a duplicate? > > I am attaching the terminal output, running the last mt4(downloaded from the > URL from this bug report) You need to set version to Windows 11 *and* apply the staging patch mentioned in bug 58043. -- 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.

June 5, 2025

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58327 tactica <tactica.os4(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tactica.os4(a)gmail.com --- Comment #1 from tactica <tactica.os4(a)gmail.com> --- Created attachment 78696 --> http://bugs.winehq.org/attachment.cgi?id=78696 Backtrace This is the backtrace from the debugger. -- 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.

June 5, 2025

[Bug 58327] New: Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58327 Bug ID: 58327 Summary: Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: tactica.os4(a)gmail.com Distribution: --- Created attachment 78695 --> http://bugs.winehq.org/attachment.cgi?id=78695 Savegame to easily trigger the crash East of the Yanov station in Jupiter, looking down the scope of your weapon will crash d3d11 if you look East while you are at a specific location: ---snip--- Assertion failed! Program: Z:\home\tactica\Downloads\Anomaly\Anomaly-1.5.3-Full.2\bin\AnomalyDX11.exe File:dlls/d3d11/inputlayout.c Line: 416 Expression: "iface->lpVtbl == &d3d11_input_layout_vtbl" ---snip--- (note: the quoted text above was typed manually) How to reproduce: 1. Download and unpack STALKER Anomaly. It doesn't require any installation. 2. Unpack the attached savegame files into /appdata/savedgames/ in the game directory. 3. Use winecfg to install d3d11 as override for Wine. 3. Start the game running /bin/AnomalyDX11.exe 4. After the main menu opens, load the provided savegame. 5. Once in the game proper, simply click RMB to use the scope of your weapon while looking at those ruined vehicles The crash does not happen if: a) You run AnomalyDX9.exe instead b) You move the camera to point elsewhere before using the scope, say 90 degrees to your right or left c) You use the shotgun instead (press 2), which doesn't have a long range scope attached c) You load the same savegame on 64-bit Windows 7 and play there, using exactly the same visual settings (I double checked that) This using 64-bit (only) Wine 10.9 on Void Linux (x86-64) with the stock AMDGPU driver. -- 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.

June 5, 2025

[Bug 58326] New: SetupDiGetClassDevs does not enumerate USB devices

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58326 Bug ID: 58326 Summary: SetupDiGetClassDevs does not enumerate USB devices Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: mail(a)3v1n0.net Distribution: --- Created attachment 78694 --> http://bugs.winehq.org/attachment.cgi?id=78694 Example device enumerator In order to enumerate the USB devices in the system, a window application is expected (https://github.com/microsoft/Windows-driver-samples/blob/main/usb/usbview/e…) to use SetupDiGetClassDevs with the `GUID_DEVINTERFACE_USB_DEVICE` GUID, however this returns nothing in WINE. Running a simpler example (attached) of the enumerator that extends to all the device types, I get in fact: ``` Device info is 0x7ffffe8d4760 Device info Date is 1 {4D36E96E-E325-11CE-BFC1-08002BE10318} Device desc name is Generic Non-PnP Monitor Device driver name is {4D36E96E-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0003 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0002 Failed at 186 Device info Date is 1 {4D36E968-E325-11CE-BFC1-08002BE10318} Device desc name is Wine Adapter Device driver name is {4D36E968-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318} Device desc name is Wine HID bus driver Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0000 Failed at 186 Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318} Device desc name is Wine USB bus driver Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0001 Failed at 186 Device info Date is 1 {00000000-0000-0000-0000-000000000000} Failed at 159 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID compatible device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0000 Failed at 186 Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} Device desc name is Wine HID compatible device Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0001 Failed at 186 Device info Date is 0 {00000000-0000-0000-0000-000000000000} ``` While under a windows VM the same code also returns (for example): Device info Date is 1 {CA3E7AB9-B4C3-4AE6-8251-579EF933890F} Device desc name is USB Video Device Device driver name is {ca3e7ab9-b4c3-4ae6-8251-579ef933890f}\0001 As per this it's not possible to find out the device ID that it could be used via `WinUsb_Initialize(deviceHandle, &winusbHandle)` (even though this doesn't seem to work even passing an hardcoded path). -- 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.

June 5, 2025

[Bug 58322] Banished! crashes

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58322 --- Comment #16 from Jesper Pedersen <jesperpedersen.db(a)gmail.com> --- Created attachment 78693 --> http://bugs.winehq.org/attachment.cgi?id=78693 Mini dump generated by Banished itself I don't know if this is useful or not -- 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.

June 5, 2025

[Bug 57950] Metatrader refuses to run/install

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57950 --- Comment #13 from Aleksandar Petrinic <petrinic(a)gmail.com> --- (In reply to Alexandre Julliard from comment #11) > Duplicate resolution was lost by Anubis... > > *** This bug has been marked as a duplicate of bug 58043 *** I see you have marked this bug as the duplicate of the other bug, I checked that as well and its solution to set by winecfg to Windows 11 didn't work for mt4 installer. Is this expected even if the bug is a duplicate? I am attaching the terminal output, running the last mt4(downloaded from the URL from this bug report) -- 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.

June 4, 2025

[Bug 57950] Metatrader refuses to run/install

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57950 --- Comment #12 from Aleksandar Petrinic <petrinic(a)gmail.com> --- Created attachment 78692 --> http://bugs.winehq.org/attachment.cgi?id=78692 terminal output of run mt4 installer -- 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.

June 4, 2025

[Bug 58325] New: wined3d swapchain use-after-free

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58325 Bug ID: 58325 Summary: wined3d swapchain use-after-free Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: yshuiv7(a)gmail.com Distribution: --- Releasing the swapchain brings us to wined3d_swapchain_cleanup, which destroys the front/back buffer textures. Texture destruction is async, happening on the device's command stream. This means these textures can be destroyed way after the swapchain itself. But we did set `texture->swapchain` to `NULL` before queuing their destruction, so that bit is fine. The problem is in texture_resource_unload. Here we try to acquire the context, which goes adapter_gl_acquire_context -> wined3d_context_gl_acquire -> wined3d_context_gl_activate -> wined3d_context_gl_update_window. And here we try to access `context_gl->c.swapchain->win_handle`, which unfortunately points to the swapchain that was just freed. I am unsure what's the fix for this. Do we hold a refcount of the swapchain in the context? Do we clear `context->swapchain` when a swapchain is being freed? Should we release the front/back buffer synchronously? Or something else? -- 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.

June 4, 2025