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

[Bug 58792] New: Couldn't get first exception for process 0020 = No backtrace available"
by WineHQ Bugzilla Oct. 12, 2025

Oct. 12, 2025

http://bugs.winehq.org/show_bug.cgi?id=58792 Bug ID: 58792 Summary: Couldn't get first exception for process 0020 = No backtrace available" Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gazblin(a)gmail.com Distribution: --- Created attachment 79438 --> http://bugs.winehq.org/attachment.cgi?id=79438 Couldn't get first exception for process 0020 G: - No backtrace available Midi programme won't work. Please see txt report "Couldn't get first exception for process 0020 G:\MidiWorksGM\MidiWorksGM.exe (WOW64). No backtrace available" MidWorks GM is a midi programme designed to adjust paparmeters of midi tracks: volume, imstrument, velocity etc. The MidiWorksGM.exe file is on a dongle which needs to be insered into the pc to allow the programme to run. I have the dongle inserted, as usual, but the programme will not install. Please help - this programme is essential for the work I do, and I want to move from 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 3

[Bug 56941] New: EA app fails to launch game if total size of environment variables exceeds ~32000 characters
by WineHQ Bugzilla Oct. 11, 2025

Oct. 11, 2025

https://bugs.winehq.org/show_bug.cgi?id=56941 Bug ID: 56941 Summary: EA app fails to launch game if total size of environment variables exceeds ~32000 characters Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)gmail.com Distribution: --- ### Steps to reproduce Preparation: - Have the EA app installed: https://origin-a.akamaihd.net/EA-Desktop-Client-Download/installer-releases… - I installed it through Bottles, which installs the following Winetricks dependencies: https://github.com/bottlesdevs/programs/blob/main/Games/eaclient.yml Reproducing: - Set a very long environment variable, before launching the EA app - From the EA app, launch any game - Alternatively, execute the game directly, it will automatically launch the EA app to launch the game - If you don't have any game, "The Sims 4" is free - The game won't launch, an error popup from the EA app will appear (see notes) ### Notes It doesn't matter whether these ~32000 characters are from a single environment variable, or from the combination of many of them. I didn't test on Windows. It may be impossible to test there, since the environment block there has a limit of 32760 characters (which may probably be the reason for this issue in the first place). I say "~32000", because the issue starts occurring a little before 32760 characters. However, my counting method was imprecise (I simply typed `set` in `wine cmd`, then counted the characters), and there's also the fact that the EA app also sets its own environment variables. The issue also occurs with games bought from Steam (thus launched with Proton) that also have to go through the EA app (thanks EA). This issue existed before, and the weird thing is that the error popup from the EA app is different from some time ago (I imagine due to the app being updated). Before it was: "Failed to launch game. An error on our end caused the launch to fail. Try again a little later." Now it's: "The game hasn't released yet" (which is obviously untrue). Is it a stack overflow issue? Logs obtained with `WINEDEBUG=EADesktop.exe:+relay` are too big to attach, even compressed. Let me know what `WINEDEBUG` parameters I should use instead. I can see that the app calls `GetEnvironmentStringsW`, shortly followed by a `WideCharToMultiByte` for each variable (key and value separately). This is done three times. -- 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 12

[Bug 58788] New: Command & Conquer 3 (EA/Origin) no tab on panel. Impossible to switch to game window (Cinnamon, x86)
by WineHQ Bugzilla Oct. 11, 2025

Oct. 11, 2025

http://bugs.winehq.org/show_bug.cgi?id=58788 Bug ID: 58788 Summary: Command & Conquer 3 (EA/Origin) no tab on panel. Impossible to switch to game window (Cinnamon, x86) Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stasvernon(a)gmail.com Distribution: --- Created attachment 79433 --> http://bugs.winehq.org/attachment.cgi?id=79433 Command & Conquer 3 log Hi, Due to EACef/libcef crash reported here (irrelevant to the game I believe): https://bugs.winehq.org/show_bug.cgi?id=32342#c121 I lauch Command & Conquer 3 Tiberium Wars in the same way EA launches it as (EA version): "wine "C:\Program Files\EA Games\Command and Conquer 3 TW and KW\Command Conquer 3 Tiberium Wars\RetailExe\1.10\cnc3game.dat" "C:\Program Files\EA Games\Command and Conquer 3 TW and KW\Command Conquer 3 Tiberium Wars\CNC3.exe" -config "C:\Program Files\EA Games\Command and Conquer 3 TW and KW\Command Conquer 3 Tiberium Wars\CNC3_english_1.10.SkuDef" " Game starts and runs well. It runs full screen and the only way to switch to Cinnamon desktop seems ALT+TAB. After clicking ALT+TAB desktop appears, but there's NO kind of Command & Conquer 3's tab on the panel. There's NO tab nor window to switch back to Command & Conquer 3 window either. The only sign that Command & Conquer 3 is still running is a very small window (w/o ANY buttons on it) in the very upper-left corner (very approximate 20x50 pixels) visible on top on every windows. It looks more like an icon/artifact. The panel is at the bottom, so this Command & Conquer 3 "icon" is more like an artifact. Its possible to click on this very upper-left corner Command & Conquer 3 "artifact" and next only game's sound appears (still no game window opens). Its IMPOSSIBLE to switch to game's window via ALT+TAB, panel. In processes its clear the above wine command is still running and using CPU/RAM. Log is attached. Clicking on the very upper-left corner artifact adds this to console: "info: Device reset info: D3D9DeviceEx::ResetSwapChain: info: Requested Presentation Parameters info: - Width: 1920 info: - Height: 1200 info: - Format: D3D9Format::A8R8G8B8 info: - Auto Depth Stencil: true info: ^ Format: D3D9Format::D24S8 info: - Windowed: false info: - Swap effect: 1 info: Setting display mode: 1920x1200(a)0 info: Setting display mode: 1920x1200(a)0 info: Device reset info: D3D9DeviceEx::ResetSwapChain: info: Requested Presentation Parameters info: - Width: 1920 info: - Height: 1200 info: - Format: D3D9Format::A8R8G8B8 info: - Auto Depth Stencil: true info: ^ Format: D3D9Format::D24S8 info: - Windowed: false info: - Swap effect: 1 info: Setting display mode: 1920x1200(a)0 info: Setting display mode: 1920x1200(a)0" Cinnamon 6.0.4 Ubuntu 24.04. Kernel 6.14.0-33-generic. wine-10.16 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.

1 2

[Bug 58781] New: wine process is not separated correctly when used with firejail
by WineHQ Bugzilla Oct. 10, 2025

Oct. 10, 2025

http://bugs.winehq.org/show_bug.cgi?id=58781 Bug ID: 58781 Summary: wine process is not separated correctly when used with firejail Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: 4gsck44sk0gksc0gw8scc0owcww0wkgw(a)ai.notifier.in Distribution: --- There is "A.exe"(trusted and can use internet) and "B.exe"(not truested so not going to give internet). 1. Run `firejail --noprofile --net=none --dns=0.0.0.0 wine B.exe`, to make sure B cannot use the internet while at the same time, allow using it with Wine. 2. Run `wine A.exe` > EXPECTED RESULT The A.exe can use internet, because it is not firejailed. > ACTUAL RESULT A.exe cannot use the internet at all. > EXPECTED I want wine to separate the wineserver per .exe so this won't happen. Also I want a offline switch, something like "wine --no-internet process_name.exe", to cut off the internet natively, if you cannot combine with firejail. -- 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 57439] New: FL Studio: many 3rd party plugins violently flash in child windows
by WineHQ Bugzilla Oct. 10, 2025

Oct. 10, 2025

https://bugs.winehq.org/show_bug.cgi?id=57439 Bug ID: 57439 Summary: FL Studio: many 3rd party plugins violently flash in child windows Product: Wine Version: 9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lildebil.mgt(a)gmail.com Distribution: ArchLinux Created attachment 77436 --> https://bugs.winehq.org/attachment.cgi?id=77436 terminal log As the title says, In FL Studio, many 3rd party vsts have flashing GUIs that make them unusable and possibly hazardous to a select amount of people with photosensitive epilepsy. This only happens in FL Studio, likely due to how it handles plugin windows. In other DAWs that let the window manager handle the plugin windows this does not happen. Side notes: 1. Most of the plugins with this issues are based on the JUCE framework 2. Whenever there is an option akin to "Disable OpenGL rendering" in the plugin settings, turning it on will usually fix the flashing, but it is almost never available. Steps to reproduce: 1. Set the wineprefix to Windows 7, to avoid bug 57247 2. Download and install FL Studio 2024 Trial - https://install.image-line.com/flstudio/flstudio_win64_24.1.2.4430.exe 3. Download and install one of the plugins with this problem (put .vst3 file into C:\Program Files\Common Files\VST3) - https://github.com/tobanteAudio/modEQ/releases/download/v0.4.0/modEQ-v0.4.0… 4. Scan and open plugin in a mixer track, drag plugin window or start audio playback to see the issue. I am using wine-staging 9.21 and proprietary Nvidia drivers -- 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 54227] New: Altium Designer 20.x - 22.x slowness in 2D schematics editor - possibly GDI font rendering problem
by WineHQ Bugzilla Oct. 10, 2025

Oct. 10, 2025

https://bugs.winehq.org/show_bug.cgi?id=54227 Bug ID: 54227 Summary: Altium Designer 20.x - 22.x slowness in 2D schematics editor - possibly GDI font rendering problem Product: Wine-staging Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kepszlok(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73773 --> https://bugs.winehq.org/attachment.cgi?id=73773 Wine's output This is a problem that affects all Altium Designer versions from 20.x to current, with all wine-staging versions of 7.xx branch. See AD compatibility reports: 20.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=38478 21.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=40170 22.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=40683 All of them shows slowness in the 2D schematics editor, while the 3D PCB editor works fine. Using the schematics editor, this message appears in constantly: 0118:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000001647F70. (the schematics editor itself working fine, just unusably slow) Possible reason: "probably because X2 uses GDI font rendering by default and lacks option to turn it off" -- 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 58782] New: Crash or freeze when draw elliptic regions
by WineHQ Bugzilla Oct. 10, 2025

Oct. 10, 2025

http://bugs.winehq.org/show_bug.cgi?id=58782 Bug ID: 58782 Summary: Crash or freeze when draw elliptic regions Product: Wine Version: 10.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 79427 --> http://bugs.winehq.org/attachment.cgi?id=79427 patch and examples When i'm passing big values to elliptic regions functions or to rounded rects functions, wine is crashing or freezing. Usually we don't need to paint such large shapes, but they can be produced by an application during pan&zoom. Mostly they are out of screen and we don't need to it to draw them properly. But we need to avoid freezing or crash. Following commands reproduce the bug (example c-code in attachment): // freeze on this command (test1.c): CreateEllipticRgn(0, 4, -600000000, 0); // crash on this (test1.c): CreateEllipticRgn(0, 4, -600000000, 0); // freeze too (test2.c): RoundRect(dc, -534431263, -25344, -108065219, -9065, 426366044, 16279); I've learned the wine sources and found several issues: 1. In file dlls/win32u/region.c in function NtGdiCreateRoundRectRgn: There are several possible int and even int64 overflows To make things work properly `ellipse_width` and `ellipse_height` should be restricted by at least 2^19. Also here can be out-of-memory issues, because this function tries to allocate allocates `ellipse_height` rectangles. So, to prevent freezing or memory issues will be better to restrict `ellipse_height` to smaller number. 2. In file dlls/win32u/dibdrv/graphics.c in function dibdrv_RoundRect: There (ellipse_width + ellipse_height)*16 bytes are allocating. So, we need to restrict to restrict values of `ellipse_width` and `ellipse_height`. For example, to 2^19 to be in consistent with NtGdiCreateRoundRectRgn. I've attached a patch-file (round-rect.patch) that solves the 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 0

[Bug 58723] New: [Bisected] Windows Steam client in FreeBSD Wine fails to display a window.
by WineHQ Bugzilla Oct. 9, 2025

Oct. 9, 2025

http://bugs.winehq.org/show_bug.cgi?id=58723 Bug ID: 58723 Summary: [Bisected] Windows Steam client in FreeBSD Wine fails to display a window. Product: Wine Version: unspecified Hardware: x86-64 URL: https://github.com/XaeroVincent/wine-tkg/blob/main/emu lators/wine-tkg-devel/steam-reverts.txt OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: darkvincentdude(a)yahoo.com Sometime during the Wine 10.x lifecycle, the Windows Steam client running in FreeBSD 14.3 Wine-Devel fails to create a window and function properly after two different commits. Each offending commit broke the steam client a separate time. These are the bisected commits: * Commit: 62b3eee965223a2de62daa87c4b81708cd62e6f3 - "user32: Add stub for SetProcessLaunchForegroundPolicy." - May 25th 2025 https://gitlab.winehq.org/wine/wine/-/commit/62b3eee965223a2de62daa87c4b817… * Commit: 9195d892ba24ca312588f2c338d33269b21bf0c8 - "configure: Build PEs with -ffp-exception-behavior=maytrap." - July 1st 2025 https://gitlab.winehq.org/wine/wine/-/commit/9195d892ba24ca312588f2c338d332… With these commits reverted, the Window Steam client functions correctly on Wine 10.15 and older 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 2

[Bug 54906] New: Menu items with icons are drawn with black squares if Wine is running in Vista+ mode
by WineHQ Bugzilla Oct. 9, 2025

Oct. 9, 2025

https://bugs.winehq.org/show_bug.cgi?id=54906 Bug ID: 54906 Summary: Menu items with icons are drawn with black squares if Wine is running in Vista+ mode Product: Wine Version: 8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: george.hazan(a)gmail.com Distribution: --- The following construction fails in the all 8.x versions of Wine (currently I upgraded to version 8.7 devel) and works Ok in Wine 7.1: MENUITEMINFO mii = {}; mii.cbSize = sizeof(mii); mii.fMask = MIIM_STRING | MIIM_STATE; if (pimi->iconId != -1) { mii.fMask |= MIIM_BITMAP; if (IsWinVerVistaPlus() && IsThemeActive()) { if (pimi->hBmp == nullptr) pimi->hBmp = ConvertIconToBitmap(pimi->parent->m_hMenuIcons, pimi->iconId); mii.hbmpItem = pimi->hBmp; } else mii.hbmpItem = HBMMENU_CALLBACK; } InsertMenuItemW(hMenu, uItem, TRUE, &mii); I.e. if I run command 'winecfg -v win2003', then everything is Ok with icons, otherwise I see black squares instead of icons. This code works Ok under all versions of Windows, from XP to Windows 11, the problem is specific to Wine 8.x under Linux (I use Kubuntu 23.04). To see the problem you can download my open source messenger Miranda NG from https://miranda-ng.org/downloads, just download a ZIP, run it and open main or tray icon menu. The full source code is avalable here: https://github.com/miranda-ng/miranda-ng, you need module menu_utils.cpp inside mir_app, InsertMenuItemWithSeparators or BuildRecursiveMenu functions. WMBR, George Hazan. -- 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 50382] New: Lego Star Wars Saga needs native d3dcompiler_47
by WineHQ Bugzilla Oct. 8, 2025

Oct. 8, 2025

https://bugs.winehq.org/show_bug.cgi?id=50382 Bug ID: 50382 Summary: Lego Star Wars Saga needs native d3dcompiler_47 Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: j-r(a)online.de Distribution: --- After installing Lego Star Wars Saga (GOG version) into a fresh 32 bit prefix, the game starts up fine including sound and controls, but with the exception of backgrounds and some effects nothing (logo, menu, in game characters etc) is displayed or replaced by grey boxes. winetricks d3dcompiler_47 fixes that problem. (An older App DB report using wine 3.3 mentions the same problem and fixing it by installing d3d9.) There is no console output indicating a problem in that area (recreating the test with wine 3.3 gives plenty of d3dcompiler error messages; perhaps they have been silenced since then?). Since the other d3dcompiler related bugs I checked all seemed to have d3dcompiler error messages I opened this new report, though it very likely still is a duplicate. Please advise which debug channels to turn on to generate a useful log. -- 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 20