wine-bugs

wine-bugs@winehq.org

1 participants
159199 discussions

[Bug 46603] New: Metro 2033 crashes on exit
by wine-bugs＠winehq.org 11 Oct '25

11 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=46603 Bug ID: 46603 Summary: Metro 2033 crashes on exit Product: Wine Version: 4.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 63501 --> https://bugs.winehq.org/attachment.cgi?id=63501 backtrace Game crashes on exit. wine-4.1-85-g957a1f0216 -- 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 2

[Bug 58754] New: Wine 10.15+ fails to detect EGL_KHR_client_get_all_proc_addresses extension despite it being present, breaking 32-bit OpenGL applications
by WineHQ Bugzilla 11 Oct '25

11 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58754 Bug ID: 58754 Summary: Wine 10.15+ fails to detect EGL_KHR_client_get_all_proc_addresses extension despite it being present, breaking 32-bit OpenGL applications 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: scheckley(a)gmail.com Distribution: --- Starting with Wine 10.15, 32-bit Windows applications requiring OpenGL fail to initialize with the error: 0024:err:wgl:egl_init Failed to find required extension EGL_KHR_client_get_all_proc_addresses 0024:err:wgl:X11DRV_WineGL_InitOpenglInfo couldn't initialize OpenGL, expect problems 0024:err:d3d:wined3d_caps_gl_ctx_create Failed to find a suitable pixel format. 0024:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter This occurs despite the EGL extension being present and reported by the system. Steps to Reproduce: - Install Wine 10.15 or 10.16 (32-bit support) - Run any 32-bit Windows OpenGL application (tested: GoG Tower57). - Observe EGL initialization failure. - Application fails to create OpenGL context and cannot render. Expected Result: Wine should detect and use the EGL_KHR_client_get_all_proc_addresses extension, as it did in Wine 10.14. Actual Result: Wine fails to find the extension, OpenGL initialization fails, and applications crash or fail to render with "error creating the renderer: Invalid window" -- 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 7

[Bug 58789] New: Changed behaviour when running a single wine process with valgrind since wine-10.9.
by WineHQ Bugzilla 11 Oct '25

11 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58789 Bug ID: 58789 Summary: Changed behaviour when running a single wine process with valgrind since wine-10.9. Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Before 5e70a4d81b I was able to start the background wine processes by e.g. `wine taskmgr &`. Then start just the target process with valgrind. Since 5e70a4d81b this causes an segv_handler loop starting with this message: vex x86->IR: unhandled instruction bytes: 0xF 0xAE 0x6C 0x24 ==833752== valgrind: Unrecognised instruction at address 0x470ed67. ==833752== at 0x470ED67: __wine_syscall_dispatcher (in dlls/ntdll/ntdll.so) This instruction is the `xrstor 0x40(%esp)` from __wine_syscall_dispatcher, which seems not yet supported by valgrind. If I see it right, before 5e70a4d81b each process did its own lookup of cpu flags, but since 5e70a4d81b this is just done by the first one and then shared via user_shared_data. As a workaround preventing the assignment of `features[PF_XSAVE_ENABLED]` allows me start it with a recent wine git build. I am uncertain if this qualifies as regression as I am uncertain, if this is a valid mode of operation when splitting wine processes that way. -- 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 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 58450] New: Total Annihilation (GOG, demo) – Wayland black screen on startup.
by WineHQ Bugzilla 11 Oct '25

11 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58450 Bug ID: 58450 Summary: Total Annihilation (GOG, demo) – Wayland black screen on startup. Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: karol23145(a)gmail.com Distribution: --- Created attachment 78901 --> http://bugs.winehq.org/attachment.cgi?id=78901 WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`. ### Summary Total Annihilation (GOG version and demo) shows a black screen on native Wayland (Mutter 48.3). On X11 it works perfectly, and on XWayland the game has a minor fullscreen issue (see Bug 57482). ### Steps to reproduce 1. Download the Total Annihilation demo (or use the GOG version). GAME DEMO CAN BE DOWNLOADED FROM: https://archive.org/details/TotalAnnihilation_201405 2. Launch the game executable (`TotalA.exe`) under Wine on a native Wayland session (No XWayland). ### Current behavior The game process starts, sound can be heard, and keyboard input works (buttons can be pressed), but the entire game window is black. The window is also not fullscreen. ### Expected behavior The game's intro videos should play, followed by the main menu, which should be visible and interactive. ### Relevant logs, screenshots, screencasts etc. *Attached are the following files:* 1. `TA.log`: Full Wine debug log captured with `WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`. 2. `system_info.txt`: Output of `inxi -Fxxxza`. ### System Details - **Wine Version:** Custom build from source (also tested with Wine development branch, same result) - **Windowing System:** Mutter 48.3 (Wayland session) - **Distribution:** Fedora 42 - **Graphics Driver:** Mesa 25.0.7 - **Kernel version:** 6.15.4 -- 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 4

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

11 Oct '25

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@0 info: Setting display mode: 1920x1200@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@0 info: Setting display mode: 1920x1200@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 58784] New: Debian's source packages by winehq depend on obsolete libosmesa6-dev
by WineHQ Bugzilla 10 Oct '25

10 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58784 Bug ID: 58784 Summary: Debian's source packages by winehq depend on obsolete libosmesa6-dev Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- I tried to install build dependencies for wine-staging using your Debian repository for forky (Debian testing), and hit such error: sudo apt build-dep wine-staging Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: builddeps:wine-staging : Depends: libosmesa6-dev but it is not installable Error: Unable to correct problems, you have held broken packages. The problem is that libosmesa6-dev package doesn't exist anymore, it used one of Mesa binary packages, but it was removed, as things were simplified: https://tracker.debian.org/pkg/mesa Can you please correct this in your source packages (this affects other ones too, not just wine-staging). -- 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 4

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

10 Oct '25

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

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