wine-bugs

wine-bugs@winehq.org

1 participants
159325 discussions

[Bug 58769] New: dgVoodoo does not work with WineD3D
by WineHQ Bugzilla 12 Oct '25

12 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58769 Bug ID: 58769 Summary: dgVoodoo does not work with WineD3D Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- When using dgVoodoo with the OpenGL backend, the game (anything on dx8 or 9 really) either never starts and just stays at a black screen; or starts, but renders a black screen; or crashes. Works with the Vulkan backend and with dxvk. The console output doesn't differ between the 2 backends, so which flags should I use to get the logs? -- 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 58768] New: [Damavand] Need for Speed (2005) crashes
by WineHQ Bugzilla 12 Oct '25

12 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58768 Bug ID: 58768 Summary: [Damavand] Need for Speed (2005) crashes Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- Created attachment 79413 --> http://bugs.winehq.org/attachment.cgi?id=79413 Full log Need for Speed (2005) crashes with the vulkan renderer. Using dgVoodoo does not help with the crash, which might mean that the problem is not specific to dx9. -- 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 58792] New: Couldn't get first exception for process 0020 = No backtrace available"
by WineHQ Bugzilla 12 Oct '25

12 Oct '25

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 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 57954] New: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device
by WineHQ Bugzilla 11 Oct '25

11 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=57954 Bug ID: 57954 Summary: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- Created attachment 78201 --> https://bugs.winehq.org/attachment.cgi?id=78201 wd-winedbg 10.2 seems to work fine, 10.3 gives an error about rawinput and the splash screen that should have the main character and game title is a black box and hangs using wow64 build, other 32bit games seem to work fine. running with WINEDBEUG ends in multiple varying lines of `0158:warn:rawinput:add_device Failed to open device file L"\\??\\HID#some-device-name#{hex-hash-id}", status 0xc0000034.` -- 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 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 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