September 2025 - Wine-bugs - list.winehq.org

[Bug 58547] New: Roblox Studio has a strange window behavior on winewayland driver
by WineHQ Bugzilla 15 Oct '25

15 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58547 Bug ID: 58547 Summary: Roblox Studio has a strange window behavior on winewayland driver Product: Wine Version: 10.12 Hardware: x86-64 URL: https://setup.rbxcdn.com/RobloxStudioInstaller.exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: wilsontulus5(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: c756ea4e801d7eae32bc8a00efa26fc0f0f47819 Distribution: ArchLinux Created attachment 79047 --> http://bugs.winehq.org/attachment.cgi?id=79047 Terminal logs without reverting the guilty commit. Almost no difference on the post-revert version. Wine version 10.11 had introduced a new update to winewayland driver that makes Roblox Studio on Wayland more usable, sometimes more than it's X11 counterpart due to lesser microstutters and almost non-existent flickering (most likely due to buggy implementation of the Vulkan child windowing system). Ever since the patch introduced in c756ea4e801d7eae32bc8a00efa26fc0f0f47819, Studio on winewayland is broken again like <=10.10 (e.g. invisible home screen, out-of-place teamcreate/contribute button, 3D workspace layer overriding GUIs including the script viewer, etc). Since the issue is only viewable after logging in, it's recommended to use Vinegar (from Flathub or by source: https://github.com/vinegarhq/vinegar - the launcher does allow specifying a custom wineroot), but the official installer can also be used if the EdgeWebView2 installer payload returns success to the official 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.

1 6

[Bug 57958] New: Caps lock issue when holding Caps lock with other key and Caps lock state was already on
by WineHQ Bugzilla 14 Oct '25

14 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57958 Bug ID: 57958 Summary: Caps lock issue when holding Caps lock with other key and Caps lock state was already on Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: daniel.gaba(a)protonmail.com Distribution: --- Hello, most of the time when holding Caps lock with another button game will register double click first on CAPS LOCK. In "Arma 3" and in "Arma: Reforger" CapsLock is used as push to talk button for radio and you are often holding it alongside other buttons. How to reproduce: 1. Caps lock state need to be on. 2. Hold other key, for example W for walking forward 3. Hold CAPS LOCK 4. In Arma 3 it will start broadcasting for ms and stop and after 1s it will start broadcasting again. In Arma: Reforger this will toggle between Squad <-> Platoon radio instead because it detected double click on Caps Lock. Game will ignore you are still holding caps lock. There is small chance that bug will not trigger. There is also possibility that game may mistakenly detect that you are still holding the Caps Lock key after releasing it, causing it to continue broadcasting until you press it again. I don't know how to reproduce this one. This is very common issue for Arma players on Linux. OS: Opensuse Tumbleweed Kernel version: 6.13.6-1-default KDE plasma Version: 6.3.2 Wayland Wine 10.3 but issue also happens on Proton 7,8 and 9 I tested it also with wayland driver and I was not able to reproduce it. -- 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 58667] New: Multi-touch gestures not passed through on CSP
by WineHQ Bugzilla 13 Oct '25

13 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58667 Bug ID: 58667 Summary: Multi-touch gestures not passed through on CSP Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: despair.chick(a)proton.me Distribution: --- On clip studio paint and other windows art based applications traditional touch operations are recognized but gestures are not. *Pinch-to-zoom *Rotation *Three-finger-operations -- 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 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 58371] New: Battlefield 2 Caps Lock menu annoying pop ups
by WineHQ Bugzilla 12 Oct '25

12 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58371 Bug ID: 58371 Summary: Battlefield 2 Caps Lock menu annoying pop ups Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: totibuluduj(a)punkproof.com Distribution: --- Enter a BF2 match, press Caps lock, run around, the kit/squads menu pops up 4 times, then press Caps lock again to close it, it pops up 4 more times. Then it finally stops popping up randomly, until the next time you press Caps lock, then repeat above. Fast team play in infantry maps is impossible because of this infuriating bug. -- 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 11

[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 58433] New: entering sub-menus makes entire menu vanish behind main window in FL Studio (virtual desktop mode)
by WineHQ Bugzilla 10 Oct '25

10 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58433 Bug ID: 58433 Summary: entering sub-menus makes entire menu vanish behind main window in FL Studio (virtual desktop mode) Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: cyrus.valkonen(a)gmail.com Distribution: --- When any menu is opened, such as "File ...", and then a nested sub-menu with more menu options such as "New from template ..." is hovered (not clicked) with the mouse to open it, the entire menu with sub-menu is suddenly rendered behind the main window (z-index issue?). Consequently the user can no longer open files and can no longer access a lot of important menus in a lot of the DAWs functions, such as music sheet editor, pattern editor, etc. In Wine 8.1 this bug does not occur, and must have been introduced somewhen after (my guess is version 9). Please note that this issue does NOT relate to X11, because it happens with "Emulate a virtual desktop" checked. I tried many things to work around it, including monkey-patching Wine 10.11 source, but everything is unsuccessful. Please note due to issues with VSTs, FL Studio needs very specific combos of NOT using DXVK, and not overriding d3dcompiler_47 or dxgi with winetricks. But even if used it makes no difference. There are NO OPTIONS in FL Studio that prevent this bug (such as unchecking ultrasmooth mode or disabling window animations). Only regressing to 8.1 fixes the bug. In the logs you will see two "TQuickPopupMenuWindow" being opened. The first is the menu, the second is the sub-menu. Many versions of FL Studio and Wine are affected by this. At least since FL 20 and Wine 9. Sadly because of changes in Juce (used by many VSTs), a lot of new and critical VST plugins now do require a very recent Wine version. Thus falling back to Wine 8.1 is no longer viable. -- 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 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