wine-bugs

wine-bugs@winehq.org

1 participants
159090 discussions

[Bug 40009] New: Lego Mindstorms EV3 Software does not find EV3 brick using Bluetooth: needs irprops.cpl.BluetoothFindFirstRadio implementation
by wine-bugs＠winehq.org 04 Sep '25

04 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=40009 Bug ID: 40009 Summary: Lego Mindstorms EV3 Software does not find EV3 brick using Bluetooth: needs irprops.cpl.BluetoothFindFirstRadio implementation Product: Wine Version: 1.9.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Lego Mindstorms EV3 software does not find the EV3 brick, needs irprops.cpl.BluetoothFindFirstRadio implementation. Brick is turned on and has Bluetooth enabled. -- 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 9

[Bug 58652] New: UWAMP httpd.exe serious error
by WineHQ Bugzilla 04 Sep '25

04 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58652 Bug ID: 58652 Summary: UWAMP httpd.exe serious error Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wsgo0sookosssc8ko4cowkcgc48k4wws(a)ai.notifier.in Distribution: --- Created attachment 79227 --> http://bugs.winehq.org/attachment.cgi?id=79227 httpd It works fine on Windows - until I move them to Linux & tried with Wine. There were 2 issues: 1. "Launcher Server" GUI no longer collect CLI windows (you know what I mean if you compare the behavior on Windows) 2. And this error pops up. Steps to reproduce: 1. Download & Extract "RELEASE SRV4.rar" from https://drive.google.com/drive/folders/1r4cXG1NfE-KEZYIN9ns3_V7mGzPO7EaK 2. run "wine explorer", navigate to server directory (where RAR files extracted) 3. start "Pangya Server Launcher.exe" 4. start "@WebServer\UwAmp.exe", it should start 5. press "START" on Server Launcher Result: httpd.exe encountered srious problem. -- 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 58664] New: Linux Mint, X11, nVidia, 200% scaling reverts to 100% scaling on Screen Res Changing
by WineHQ Bugzilla 04 Sep '25

04 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58664 Bug ID: 58664 Summary: Linux Mint, X11, nVidia, 200% scaling reverts to 100% scaling on Screen Res Changing Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: LiveFreeDead(a)hotmail.com Distribution: --- Mint 22.2 Cinnamon NVidia 575 Open Drivers WINE 9.0 from the built in repo has been used. I have been testing thing in Mint 22.2 Cinnamon and noticed that my 4k screen requires 200% DPI to make it readable, this lets WINE run fine. I am able to use 100% or 200%, but after a game changes to 800x600 or 640x480 etc, when it changes back to 100% Scaling on me, even though it was set to 200% when I executed the game, I understand why it does this during gameplay, but it should remember and revert my old Scaling option where possible. I also understand this is only one Desktop Environment on one Distro, but I have had it have other issues, I'll just mention them here as I don't expect them to be fixed as it's Cinnamon issues and not a Wine, you guys shouldn't be the ones to make work around's to issues like these. But if you happen to, I don't mind who repairs it as I would like it to change itself back to 200% when Wine is done if it gets changed by the WINE app or at least while the WINE app was running but has exited, I do know that if 2 wine games or apps were running, you would have to leave it set to 100% until both have ended, so understand it's not straight forward to fix. If I use Wayland it doesn't change screen resolutions at all, xrandr isn't even available and the alternatives they offer are not very capable for me to script it for games that require it (Multi system, I can do my current system, but it doesn't have a default display, you have to provide the output port, HDMI, DP, RGB etc). I found using Steam to execute them works fine, will change the res and stretch to fit the screen. Even though WINE is able to run them, it puts them in a 800x600 or whatever res it is meant to scale, on the top left of my 4k display (set to 100% or 200%). Using Nouveau drivers for nvidia or MESA on AMD cards works fine and scales. so I just chalk this up to NVidia issues. But I use my system for LLM's, AI Gen and need the Cuda drivers and 3D acceleration to achieve this, so that's not an option. Thanks for all you do. -- 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 36668] New: Under Wine, Installation of Hotspot Shield Fails/Crashes
by wine-bugs＠winehq.org 03 Sep '25

03 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=36668 Bug ID: 36668 Summary: Under Wine, Installation of Hotspot Shield Fails/Crashes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bugs(a)piouseye.com Created attachment 48713 --> http://bugs.winehq.org/attachment.cgi?id=48713 Report Generated By Wine @ Failure Hotspot Shield crashes during installation. This does not SEEM to be the same issue as in Bug 16002 or other "Possible Duplicates," so I'm passing along the report Wine generated. -- 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 15

[Bug 58265] New: regression in Wine >=10.7 for DXVK DLL override on macOS
by WineHQ Bugzilla 03 Sep '25

03 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58265 Bug ID: 58265 Summary: regression in Wine >=10.7 for DXVK DLL override on macOS Product: Wine Version: 10.7 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78608 --> http://bugs.winehq.org/attachment.cgi?id=78608 macOS Terminal log, wine-devel 10.7 On macOS, there is a bug (https://bugs.winehq.org/show_bug.cgi?id=58145) that can be worked around with a DXVK DLL override (for d3d11.dll) in Wine-devel 10.6 and lower, but this workaround stops working in Wine-devel 10.7 (also tested not working in 10.8) repost of my comment from that previous bug: regression in wine-devel 10.7 - DXVK DLL workaround stops working There's new regression in wine-devel 10.7: now the DXVK DLL override workaround doesn't work, the app always gives the original error pop-up window with the same message. Attached is the macOS Terminal log after copying Gcenx's 32-bit `d3d11.dll` from his DXVK-macOS package to the same directory as the OutOfCtrl.exe executable. When tested with wine-devel 10.6, it still works. > % cp /Users/toastybug/dxvk-macOS/x32/d3d11.dll /Users/toastybug/Windows_Apps/OutOfCtrl_v1_2_EXE/ > % cd /Users/toastybug/Windows_Apps/OutOfCtrl_v1_2_EXE/ > % WINEDEBUG=module WINEDLLOVERRIDES="d3d11=n" wine OutOfCtrl.exe tested using Gcenx's wine-devel 10.7 build (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.7) with GStreamer 1.26.1 on macOS 11.7.10 and Gcenx's DXVK-macOS v1.10.3-20230507-repack (https://github.com/Gcenx/DXVK-macOS/releases/tag/v1.10.3-20230507-repack) -- 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 58264] New: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93"
by WineHQ Bugzilla 03 Sep '25

03 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58264 Bug ID: 58264 Summary: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevu lkan/loader_thunks.c, line 93" Product: Wine Version: 10.7 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78605 --> http://bugs.winehq.org/attachment.cgi?id=78605 macOS Terminal log, wine-devel 10.8 running cpuz_x64.exe On macOS, there is a regression in multiple Windows programs since Wine-devel 10.7 (including 10.8) releases by Gcenx, with the final lines of the terminal output reading: > -[MTLHeapDescriptorInternal validateWithDevice:]:327: failed assertion `Heap Descriptor Validation > Placement heap type is not supported. > ' > 01a0:err:msvcrt:_wassert (L"!status && \"vkAllocateMemory\"",L"/Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c",93) > Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93 These programs work fine in Wine-devel 10.6 and lower tested with Wine-devel 10.7 and 10.8 binary releases from Gcenx (https://github.com/Gcenx/macOS_Wine_builds/releases) on macOS 11.7.10 tested with CPU-Z 2.15 (portable) (cpuz_x64.exe) download: https://download.cpuid.com/cpu-z/cpu-z_2.15-en.zip sha256: c8461d995d77a8fe1e8c5823403e88b04b733165cc151083b26379f1fe4b9501 -- 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 58658] New: IK Multimedia Amplitube 5: GUI rendering periodically hangs.
by WineHQ Bugzilla 03 Sep '25

03 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58658 Bug ID: 58658 Summary: IK Multimedia Amplitube 5: GUI rendering periodically hangs. Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: emmetoneill.pdx(a)gmail.com Distribution: --- Created attachment 79236 --> http://bugs.winehq.org/attachment.cgi?id=79236 Diagram showing GUI drawing lag spike behavior in Amplitube 5 Amplitube 5 (a guitar and bass amp/effect sim program) has a problem via WINE where rendering of the GUI periodically hangs. Here are some things that might help: - These lag spikes DON'T occur in the original version on Windows. - These spikes seem to ONLY affect the drawing of the GUI. (Audio processing is unaffected, and mouse clicks are still registered even when the rendering is hitching.) - The lag spikes are extremely predictable (dare I say metronomic). From what I can tell they happen almost once per second, every second. They also seem to last about half a second, every time. (I've attached a silly diagram to show how it feels like the spikes are happening.) - I use this program very regularly, and I have noticed that this bug has been around for a while, across a few versions of WINE. I can't say whether or not it is a regression from older versions of WINE as a lot of things have changed on my system, but I'm sure that it isn't new to 10.14. - This may be an interesting, unrelated coincidence... But the default metronome setting in Amplitube happens to be 120bpm (2hz), and the timing of the GUI lag spikes is so regular and predictable that if you turn the metronome on and hit play, you will find that they line up exactly with the timing of the beats/clicks. (Where you can count 1,2,3,4 and visually see the program's GUI draw, lag, draw, lag...) When I first noticed this I changed the internal bpm setting to a different value, thinking that it might be connected, but that did not seem to change the frequency of the lag spikes (they continued happening at ~1 spike per second). - I have tested this on a standard WINEPREFIX containing only IK Multimedia application installs. But I have also tested this using DXVK library overrides. I know that bug reports here are for vanilla WINE installs only, but I just want to mention that this behavior seems to be consistent whether in both contexts. - I should also mention that I don't see any output in the terminal when these spikes are happening. To the untrained eye, there's nothing that I can see that is hinting at what might be causing the visual hitching. Aside from these annoying GUI drawing hitches, Amplitube 5 works very nicely in WINE, so I'm hoping that we can figure something out. :) If there is anything else I can share with the team to help diagnose and debug this problem I'd be happy to help! -- 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 58649] New: SimpleTV portable (Qt5/Lua/VLC) – D3D9Ex OSD overlay disappears or crashes after opening dialogs
by WineHQ Bugzilla 03 Sep '25

03 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58649 Bug ID: 58649 Summary: SimpleTV portable (Qt5/Lua/VLC) – D3D9Ex OSD overlay disappears or crashes after opening dialogs Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: riv100a(a)gmail.com Distribution: --- Application tested: SimpleTV (portable fork, Qt5/Lua/VLC) Official download: https://plst.rf.gd/?i=1 Problem: OSD overlay (D3D9Ex child window) disappears or crashes after opening dialogs, depending on backend. Wayland/Xwayland → OSD appears but glitches. Dialogs do not kill it immediately, but resizing the window often makes it vanish. Sometimes restored by “Always on top”. Wine Virtual Desktop → OSD stable until "Options" dialog is opened. Then disappears permanently (never comes back until restart). Xephyr (nested X11) → OSD stable until Options dialog. Opening it crashes Wine completely. Tested on Proton-GE 10-12/13/15 and Wine vanilla. OS: KDE Neon (Ubuntu 22.04 base). GPU: Intel HD630 + Nvidia Quadro M620. DXVK v2.7.x. Expected: OSD overlay should persist after dialogs. Actual: OSD disappears or Wine crashes. This strongly suggests a Wine bug in handling of D3D9Ex child overlay windows. -- 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 58584] New: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup
by WineHQ Bugzilla 03 Sep '25

03 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58584 Bug ID: 58584 Summary: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: waser(a)waser.tech Distribution: --- This report details a consistent, immediate startup crash in `CONCRT140.dll` affecting modern S.T.A.L.K.E.R. engine forks. These engines are based on the open-source **Open X-Ray 1.6**, which itself works flawlessly under Wine. The crash only appears in these newer, more advanced forks which leverage the MSVC concurrency runtime for performance. This strongly indicates the issue lies within Wine's implementation of these APIs, not a bug in the engines themselves. This is effectively a regression, as the baseline engine works while the newer, concurrency-enabled versions do not. **Existing Related Bugs:** This issue appears to be a new, highly reproducible test case for known problems in Wine's concurrency support. We are filing this as a new report due to the unique test case and the specific failure point (constructor vs. destructor), but it is likely caused by the same underlying issues as: - **Bug 52899:** Notes that `CONCRT140.dll` requires `CreateEventExW` from `kernel32`. This is the most likely root cause. - **Bug 41749:** Shows a crash in the destructor for `Concurrency::details::_TaskCollection`. Our crash occurs in the *constructor* of this same object, demonstrating a different failing code path. Our report provides two clear methods to reproduce this crash, including one that is fully free and requires no commercial software. --- ### **Primary Reproduction Steps (IX-Ray on S.T.A.L.K.E.R.: Call of Pripyat)** *(Steps 1-5 as in previous draft)* 6. **Run the Game with Debug Logging:** Launch the game using its main executable with full debug channels enabled. ```bash WINEDEBUG=+all wine Stalker-COP.exe &> stalker_cop_crash_all.log WINEDEBUG=+seh,+loaddll wine Stalker-COP.exe &> stalker_cop_crash_seh.log ``` 7. **Result:** The process will crash immediately. The game's own crash log (in `_appdata_ixray_/logs`) and the attached Wine debug logs will show a fatal error in `CONCRT140.dll`. --- ### **Alternative Reproduction Steps (AOEngine on S.T.A.L.K.E.R. Anomaly)** This method is fully free and requires no commercial game assets. 1. **Download S.T.A.L.K.E.R. Anomaly:** Download the standalone game from its [ModDB page](https://www.moddb.com/mods/stalker-anomaly/downloads). 2. **Download AOEngine:** Download the latest AOEngine release from its [ModDB addons page](https://www.moddb.com/mods/stalker-anomaly/addons/aoengine). 3. **Install AOEngine:** Extract the contents into the Anomaly game's `bin` directory, overwriting `AnomalyDX11.exe`. 4. **Create a Clean Wine Prefix:** ```bash export WINEPREFIX=~/.wine_anomaly rm -rf $WINEPREFIX && wineboot -u ``` 5. **Install Runtimes:** ```bash winetricks -q vcrun2022 d3dcompiler_47 ``` 6. **Run the Game with Debug Logging:** Launch the game using the Anomaly launcher. ```bash WINEDEBUG=+all wine AnomalyLauncher.exe &> anomaly_crash_all.log WINEDEBUG=++seh,+loaddll wine AnomalyLauncher.exe &> anomaly_crash_seh.log ``` (Within the launcher, disable AVX, select DX11, disable the shader cache, and click Play). 7. **Result:** The exact same crash behavior as the IX-Ray method will be observed. The game's crash log will be in `_appdata_/logs` and the full Wine log will be `anomaly_crash_*.log`. --- **Expected Behavior:** The game launcher should appear, and the game should launch to the main menu successfully, as it does on Windows and as the baseline Open X-Ray 1.6 engine does under Wine. **Logs:** Three files will be attached for the primary reproduction case: 1. `stalker_cop_crash_seh.log`: A small log with `+seh,+loaddll` for quick initial review. 2. `stalker_cop_crash_all.log.bz2`: The complete `+all` debug log, compressed with bzip2 due to its large size. 3. `ixray-2025.08.10-02.37.21-waser.log`: The game's own crash log from its `_appdata_ixray_/logs` directory. **References:** - **IX-Ray GitHub (Open Source Engine):** https://github.com/ixray-team/ixray-1.6-stcop - **GE-Proton Issue #197 (Full History):** https://github.com/GloriousEggroll/proton-ge-custom/issues/197 -- 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 24

[Bug 58631] New: WINE 10.13 breaks foobar2000
by WineHQ Bugzilla 02 Sep '25

02 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58631 Bug ID: 58631 Summary: WINE 10.13 breaks foobar2000 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ekopcom(a)gmail.com Distribution: --- After updating to WINE 10.13, foobar2000 no longer opens successfully. The window appears with blank panels and then crashes and closes. Reverting to WINE 10.12 fixes the issue. I've compared both WINE versions in a new WINEPREFIX with a portable installation of foobar2000-x64_v2.24.6. I'm using Arch with an up-to-date system. The terminal output of both runs as well as foobar2000's crash report are shown here: https://pastebin.com/YVbg33Cg -- 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 5

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