wine-bugs February 2025

wine-bugs@winehq.org

1 participants
1624 discussions

[Bug 55076] New: Steam fills terminal output with "ResizeObserver loop limit exceeded" messages.
by WineHQ Bugzilla 13 Oct '25

13 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=55076 Bug ID: 55076 Summary: Steam fills terminal output with "ResizeObserver loop limit exceeded" messages. Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 74626 --> https://bugs.winehq.org/attachment.cgi?id=74626 Steam default terminal output wine 8.9 Hello, This started after a Steam update sometimes ago I don't remember. > [0617/144308.788:INFO:CONSOLE(1)] "ResizeObserver loop limit exceeded", source: https://steamloopback.host/index.html?IN_CLIENT=true&LOCAL_HOSTNAME=piezo1&… (1) Searching the quoted string on the web shows that it's related to Chrome [1], thus Chrome Embedded Framework too (libCEF). The constant flow of messages fills the HD with several MB after a few hours. It may be an application bug, but I can't compare to Windows because there is no output at all when running steam from the Windows command prompt. Regards. [1] https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exce… -- 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

[Bug 57537] New: Steuersparerklärung 2024 fails to install
by WineHQ Bugzilla 12 Oct '25

12 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57537 Bug ID: 57537 Summary: Steuersparerklärung 2024 fails to install Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Found while testing a report from the forums: https://forum.winehq.org/viewtopic.php?t=39775 Ran in a clean WINEPREFIX, used trial version and express installation. It gives a messagebox with > Die Installation von >>Steuersparerklärung 2024<< konnte nicht durchgeführt werden! Prüfen Sie bitte, ob die notwendigen Installationsvoraussetzungen erfüllt sind Translated: The installation of >>Steuersparerklärung 2024<< could not be completed! Please check whether the necessary installation requirements are met -- 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 56941] New: EA app fails to launch game if total size of environment variables exceeds ~32000 characters
by WineHQ Bugzilla 11 Oct '25

11 Oct '25

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 57439] New: FL Studio: many 3rd party plugins violently flash in child windows
by WineHQ Bugzilla 10 Oct '25

10 Oct '25

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 10 Oct '25

10 Oct '25

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 54906] New: Menu items with icons are drawn with black squares if Wine is running in Vista+ mode
by WineHQ Bugzilla 09 Oct '25

09 Oct '25

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 08 Oct '25

08 Oct '25

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

[Bug 57175] New: Multiple issues with Audacity after upgrading to Wine 9.17
by WineHQ Bugzilla 08 Oct '25

08 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57175 Bug ID: 57175 Summary: Multiple issues with Audacity after upgrading to Wine 9.17 Product: Wine Version: 9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 77073 --> https://bugs.winehq.org/attachment.cgi?id=77073 Audacity 3.6.3 in Wine 9.17 with DPI=144 and classic Windows theme After I upgraded Wine from version 9.10 to 9.17, Audacity has become horrible to use and look at. I've always been using DPI=144 because I have a High DPI 14" monitor. So, * Fonts in Audacity have become much smaller than they were before * Fonts now look very blurry A screenshot will be attached. On the outside of Audacity you can see IrfanView which continues to scale properly and fonts are rendered just fine. -- 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 47

[Bug 57866] New: Missing pages tree
by WineHQ Bugzilla 08 Oct '25

08 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57866 Bug ID: 57866 Summary: Missing pages tree Product: Wine-gecko Version: unspecified Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: tomislav.budor(a)lovatoelectric.hr Created attachment 78089 --> https://bugs.winehq.org/attachment.cgi?id=78089 Missing pages tree in .chm viewer Missing pages tree in .chm viewer -- 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 19153] New: DX3 game does not recognize graphics capabilities
by wine-bugs＠winehq.org 07 Oct '25

07 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=19153 Summary: DX3 game does not recognize graphics capabilities Product: Wine Version: 1.1.24 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=versi on&iId=9396 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: bobbyg(a)gmx.net Resident Evil 1 does not start giving the error "Failed to initialize the Graphics Hardware Device.(3)". It's a DirectX 3 game using immediate mode. After some debugging I found that it relies on 3 (three) entries returned by EnumDevices whereas wine returns only the Direct3D HAL entry in this case (d3dversion == 1). Removing the if-clause in ddraw/direct3d.c and duplicating the HAL entry solves the problem and the game actually runs almost perfectly (Garbage -> Platinum). I checked a Windows installation which returns "HAL", "RGB Emulation" and "Ramp Emulation" but the comments in the file suggest that not all games are happy about that. So how to fix this properly? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 51

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