wine-bugs

wine-bugs@winehq.org

1 participants
159134 discussions

[Bug 41024] New: Failure to install
by wine-bugs＠winehq.org 30 Sep '25

30 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=41024 Bug ID: 41024 Summary: Failure to install Product: Wine Version: 1.8.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: leo_one(a)telus.net Distribution: --- Created attachment 55190 --> https://bugs.winehq.org/attachment.cgi?id=55190 config.log shows compilation failure Attempts to install wine-1.8.3 fail to compile. config.log attached. -- 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 4

[Bug 58142] New: Teraterm 5.4.0 / Serial communication not functional
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58142 Bug ID: 58142 Summary: Teraterm 5.4.0 / Serial communication not functional Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janne.kekkonen(a)gmail.com Distribution: --- tested with wine 10.5-staging When data is sent to serial port that is opened with TeraTerm, GUI becomes very sluggish and data received is not shown on the terminal. When data sending is stopped. Received data is shown and GUI responsivenes becomes normal. This behavior seems very similar that is described in bug(s): 57246 and 50591. Download link: https://github.com/TeraTermProject/teraterm/releases Side note: Wine registry do not have serial port friendly name information. Teraterm needs to be started with command line parameter which defines port: wine ttermpro.exe /C=2 -- 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 57537] New: Steuersparerklärung 2024 fails to install
by WineHQ Bugzilla 30 Sep '25

30 Sep '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 11

[Bug 57691] New: wine-mono: ASan gets triggered in mono_path_canonicalize with strcpy-param-overlap.
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57691 Bug ID: 57691 Summary: wine-mono: ASan gets triggered in mono_path_canonicalize with strcpy-param-overlap. Product: Wine Version: 10.0-rc6 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 77881 --> https://bugs.winehq.org/attachment.cgi?id=77881 asan_2025-01-18_17-11-19_.1748 Hello, I tried getting wine being built with ASan (PE side) enabled. [1] And tried running on this build the wine conformance tests. One place where ASan gets triggered is in mono\mono\utils\mono-path.c [2]: 90 if (dest != lastpos) strcpy (dest, lastpos); ERROR: AddressSanitizer: strcpy-param-overlap A few lines above (line 74) there is the possibility of the strings overlapping mentioned and a memmove used. Attached file contains the full output of one ASan event. Would it be valuable to replace the `strcpy (dest, lastpos);` by a `memmove (dest, lastpos, strlen(lastpos) + 1)`? [1] https://gitlab.winehq.org/bernhardu/wine/-/blob/asan-pe_2024-12-29/README.md [2] https://gitlab.winehq.org/mono/mono/-/blame/main/mono/utils/mono-path.c#L90 -- 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 58744] New: Missing Type on get_type within dlls/msi/suminfo.c
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58744 Bug ID: 58744 Summary: Missing Type on get_type within dlls/msi/suminfo.c Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: matgrioni(a)gmail.com Distribution: --- For a certain use case I wanted to run Microsoft Keyboard Layout Creator (MSKLC) on a serverless function and therefore was trying to get it to run on Wine. The application takes a keyboard layout definition and then has functionality to create a MSI which contains the DLL for the created keyboard. When running this compilation step, the MSI creation was failing and I was able to identify that the MSI creation process with MSKLC was calling MsiSummaryInfoSetPropertyW with property PID_EDITTIME which is missing from /dlls/msi/suminfo.c:get_type and should have type VT_FILETIME according to this documentation: https://learn.microsoft.com/en-us/windows/win32/msi/summaryinfo-summaryinfo. By adding PID_EDITTIME to the function, I was able to unblock this part. Overall it's a trivial problem and fix, I figure in part it hasn't been run into is that the use case of *creating* an MSI (rather than running it), is quite small, and it seems the EDITTIME property may not be read from on installation. I created a bug for it, since I was having issues creating a fork and the problem is quite trivial, and my ability to contribute to wine will probably not extend much beyond this issue :) -- 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 58742] New: winedbg: Internal crash at 00006FFFFF8CB5E5 (pe_load_msc_debug_info)
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58742 Bug ID: 58742 Summary: winedbg: Internal crash at 00006FFFFF8CB5E5 (pe_load_msc_debug_info) Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: zowie+wine(a)vandillen.io Distribution: --- Platform: Linux Mint 21.3 Cinnamon Linux Kernel: 5.15.0-156-generic Platform 2: Linux Mint 22.2 Cinnamon Linux Kernel 2: 6.8.0-83-generic When I build Wine myself and run the command `$WINE winedbg explorer` with it, it leads to a crash. This does not happen with the official builds of Wine, so I'm guessing there's some package version difference or something along those lines that makes this occur. Log from a custom build of 10.15: ``` user@pc:~/wine/test$ $WINE winedbg explorer WineDbg starting on pid 0184 0180:fixme:dbghelp:elf_search_auxv can't find symbol in module 0180:fixme:dbghelp:elf_search_auxv can't find symbol in module winedbg: Internal crash at 00006FFFFF8CB5E5 user@pc:~/wine/test$ ``` Log from the official build of 10.15: ``` user@pc:~/wine/test$ wine winedbg explorer WineDbg starting on pid 01b4 01b0:fixme:dbghelp:elf_search_auxv can't find symbol in module 01b0:fixme:dbghelp:elf_search_auxv can't find symbol in module 0x006fffffc00c3d ntdll+0x10c3d: retq Wine-dbg> ``` The crash occurs in pe_load_msc_debug_info from pe_module.c, in the branch with `/* Debug info is stripped to .DBG file */`. The variable `dbg` is null, so it crashes when trying to dereference it. Here's a quick fix I made for it. It fixes the crash but it doesn't really solve the underlying issue. As a result the debugger is missing so much debug information that it's not actually that helpful. ``` /* Read in debug directory */ dbg = RtlImageDirectoryEntryToData( mapping, FALSE, IMAGE_DIRECTORY_ENTRY_DEBUG, &nDbg ); nDbg = dbg ? nDbg / sizeof(IMAGE_DEBUG_DIRECTORY) : 0; /* NEW */ if (!dbg) { pe_unmap_full(fmap); return ret; } /* END */ /* Parse debug directory */ ``` It's a bit annoying but for the time being I'll probably use the official build for debugging, or maybe I'll try to build Wine using the Docker set-up from the Gitlab CI. -- 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 58730] New: Images in iTunes have a white background (see picture)
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58730 Bug ID: 58730 Summary: Images in iTunes have a white background (see picture) Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: usr_40476(a)icloud.com Distribution: --- Created attachment 79347 --> http://bugs.winehq.org/attachment.cgi?id=79347 bruh um not quite sure how to further explain it so i guess heres a screenshot -- 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 58158] New: Regression: Sacred Gold 2.28 ASE crashes when initialising multiplayer
by WineHQ Bugzilla 30 Sep '25

30 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58158 Bug ID: 58158 Summary: Regression: Sacred Gold 2.28 ASE crashes when initialising multiplayer Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zergling.man42(a)gmail.com Distribution: --- Created attachment 78442 --> http://bugs.winehq.org/attachment.cgi?id=78442 git diff 3aa18cc5d01028bda126624ba5f5bfb11ebc4f77 8714eb2fef7182a9c73b9963493935decca89fdc Can be triggered by running Sacred.exe and navigating multiplayer -> any of the three options (local network, closed internet, open internet), or by running GameServer.exe. Causes an unhandled page fault on read access, probably in tincat2.dll. After two bisects, I believe it's caused by 3aa18cc5d01028bda126624ba5f5bfb11ebc4f77, but reverting it doesn't fix it. It's definitely somewhere between 7.2 and 7.3. -- 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 35648] New: Anthem Room Correction 2 v1.0.1: crash when connecting to A/V receiver in auto mode
by wine-bugs＠winehq.org 29 Sep '25

29 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=35648 Bug ID: 35648 Summary: Anthem Room Correction 2 v1.0.1: crash when connecting to A/V receiver in auto mode Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tristan.schmelcher(a)gmail.com Created attachment 47607 --> http://bugs.winehq.org/attachment.cgi?id=47607 Console output The application Anthem Room Correction 2 v1.0.1 crashes when trying to connect to an A/V receiver if run in automatic mode (with "/Auto" specified on the command line). The application also fails in manual mode at the same spot, but it doesn't crash; instead it hangs with 100% CPU usage. The console output with stack trace from the crash in automatic mode is attached. The application can be downloaded at http://anthemav.com/downloads/ARC-2%20Setup.zip, but you must have an Anthem A/V receiver in order to get this far in it. I am happy to carry out suggested testing/debugging. 74dc2107ca936dddbd0fc6abbb2baf74e387c163 ARC-2 Setup.zip -- 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 7

[Bug 58737] New: Download of large file via WinHTTP fails with WSATIMEDOUT
by WineHQ Bugzilla 29 Sep '25

29 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58737 Bug ID: 58737 Summary: Download of large file via WinHTTP fails with WSATIMEDOUT Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: felixhaedicke(a)web.de Distribution: --- Created attachment 79362 --> http://bugs.winehq.org/attachment.cgi?id=79362 Source code: Download a file (without acutally storing it) via HTTPS via WinHTTP See attached sample code: For particular (large) files, downloads using wine's WinHTTP implementations can fail reproducibly with a WSATIMEDOUT. This happens when running the installer of Condor 3 (https://www.condorsoaring.com), which is obviously built with "Inno Setup". The installer downloads a 14 GB archive from https://downloads3.condorsoaring.com/V3/Landscapes1.zip during installation. Unfortunately, when the actual download is finished, the installer fails with a code 10060 (WSATIMEDOUT) error message. Using the attached sample code, I could reproduce this problem. The file is downloaded, but the last WinHttpQueryDataAvailable() call fails with WSATIMEDOUT (instead of detecting EOF): winhttpdownload.exe "downloads3.condorsoaring.com" "/V3/Landscapes1.zip" It seems to work fine for most other downloads, even for files which are larger than 4GB (4294967295 bytes, DWORD max value). The sample code works fine on Windows 11. -- 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 58733] New: widl gives a segmentation fault.
by WineHQ Bugzilla 29 Sep '25

29 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58733 Bug ID: 58733 Summary: widl gives a segmentation fault. Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian I tried this command: ~/wine/tools/widl/widl -I ~/wine/include/ -L ~/wine/dlls/stdole2.tlb/ ~/wine/include/msinkaut.idl Result: Segmentation fault This command works for other idl files like wbemdisp.idl I found a hack to work around the crash is to make the 4 methods in msinkaut that contain IDataObject static; might be a pointer to the cause of the bug? diff --git a/include/msinkaut.idl b/include/msinkaut.idl index 743dec82a40..0bc6d5c79d5 100644 --- a/include/msinkaut.idl +++ b/include/msinkaut.idl @@ -656,20 +656,20 @@ cpp_quote("#endif /* _WINGDI_ */") [in] VARIANT PacketData, [in] VARIANT PacketDescription, [out, retval] IInkStrokeDisp **Stroke); - HRESULT ClipboardCopyWithRectangle( + static HRESULT ClipboardCopyWithRectangle( [in] IInkRectangle *Rectangle, [in] InkClipboardFormats ClipboardFormats, [in] InkClipboardModes ClipboardModes, [out, retval] IDataObject **DataObject); - HRESULT ClipboardCopy( + static HRESULT ClipboardCopy( [in] IInkStrokes *strokes, [in] InkClipboardFormats ClipboardFormats, [in] InkClipboardModes ClipboardModes, [out, retval] IDataObject **DataObject); - HRESULT CanPaste( + static HRESULT CanPaste( [in] IDataObject *DataObject, [out, retval] VARIANT_BOOL *CanPaste); - HRESULT ClipboardPaste( + static HRESULT ClipboardPaste( [in] long x, [in] long y, [in, unique] IDataObject *DataObject, -- 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 58735] New: Wine 10.15 crash (c0000005) on Arch Linux with nvidia drivers
by WineHQ Bugzilla 29 Sep '25

29 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58735 Bug ID: 58735 Summary: Wine 10.15 crash (c0000005) on Arch Linux with nvidia drivers Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ilya.laguxa(a)gmail.com Distribution: --- Created attachment 79357 --> http://bugs.winehq.org/attachment.cgi?id=79357 Debug log output of wineboot -u System Information: - Arch Linux x86_64 - Kernel: Linux 6.16.8-arch3-1 - Window Manager: Openbox 3.6.1 (X11) - Laptop: HP Omen 15, Ryzen 7 4800H, NVIDIA RTX 2060M - Bumblebee for hybrid graphics Launching wineboot -u (or any other wine command) on a fresh prefix (~/.wine) hangs indefinitely. Ctrl+C does not interrupt. Removing NVIDIA drivers and using amdgpu allows Wine to run correctly. With NVIDIA drivers installed, Wine immediately crashes with access violation (c0000005). I can only terminate wineboot by running: wineserver -k Steps Taken: Verified 32-bit libraries installed (lib32-nvidia-utils, Vulkan working) LANG=C, clean user, WINEARCH=win64 Tested on fresh prefix Tested on an old kernel, same result glxinfo shows NVIDIA RTX 2060 nvidia-smi works correctly nvidia and amdgpu modules are loaded I have no custom xorg.conf Other Wine builds such as staging or AUR and proton don't work with same behavior -- 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 55981] New: Dragon Age Origins: Runs slowly when using the experimental wow64 mode
by WineHQ Bugzilla 29 Sep '25

29 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=55981 Bug ID: 55981 Summary: Dragon Age Origins: Runs slowly when using the experimental wow64 mode Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 75572 --> https://bugs.winehq.org/attachment.cgi?id=75572 Dragon Age : Origins main menu with new wow64 + OpenGL renderer Dragon Age : Origins works with the new wow64 experimental mode but it's very slowly and unplayable. This bug affect "Beyond Good & Evil" too. Use DXVK fix this issue so something wrong with new wow64 + opengl renderer ? -- 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 26

[Bug 58743] New: Saitek Joystick has a twist stick for rudder. Registry is configured for Rz but 'wine control' shows Rx.
by WineHQ Bugzilla 29 Sep '25

29 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58743 Bug ID: 58743 Summary: Saitek Joystick has a twist stick for rudder. Registry is configured for Rz but 'wine control' shows Rx. Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: bgoodwin91006(a)charter.net Distribution: --- I am using the current stable version of Linux Mint 22.1 Wine; wine-9.0 (Ubuntu 9.0~repack-4build3) My 'Saitek ST290 Pro' joystick has a twist stick to act as rudder or steering control in addition to the usual X,Y,and Z(throttle) inputs. I need the twist axis to be mapped to the Rz axis so I configured a wine registry entry for this setup. When I run 'wine control', It shows x,y,and z working correctly but the stick twist shows up as Rx. The twist does not work in the game 'FA-18 PSF' as proof that the stick is not mapped to Rz. It has worked in the past (several years ago) on this game. My registry setting is HKCU-Software-Wine-DirectInput-Saitek-Saitek Pro 290 "=" X,Y,Z,Rz,POV1 I have tried pointing the generic 'joysticks-default' entry to saitek, I have tried various variations of the comma separated x,y,z.etc entries for my joystick (spaces,no spaces), I tried deleting the generic joysticks entry making my Saitek entry the only joystick entry under DirectInput. I tried making the Saitek entry as a sub entry under the generic joysticks entry. It appears that wine is ignoring my registry entry. -- 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 58741] New: Maintainer requests should only be submittable once
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58741 Bug ID: 58741 Summary: Maintainer requests should only be submittable once Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php?sClass=main tainer&sState=queued&sTitle=Maintainer%20Queue OS: Linux Status: NEW Keywords: download, source Severity: minor Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: --- Created attachment 79371 --> http://bugs.winehq.org/attachment.cgi?id=79371 Screenshot A user can currently submit as many requests to maintain an application as they want, effectively spamming the queue. There's no reason for there to ever be more than one request per user per application (or version). -- 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 58726] New: version 10.15 Regression: "Roon" music player only shows a blank white screen but buttons (that aren't displayed) technically work
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58726 Bug ID: 58726 Summary: version 10.15 Regression: "Roon" music player only shows a blank white screen but buttons (that aren't displayed) technically work Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joni.hilger(a)yahoo.de Distribution: --- Created attachment 79334 --> http://bugs.winehq.org/attachment.cgi?id=79334 Screenshot of the bug happening on wine-staging 10.15 - the window is completely blank/white When launching the Roon music player application, only a blank white window is rendered. The buttons technically work when clicking on the space where they are usually located so it seems to be a rendering issue. Additionally the window is "hard to interact with" when maximizing it I can't grab the top bar anymore (I mean the KDE provided one) and the close/minimize buttons in the top right wont work anymore. This bug only happens in 10.15 Downgrading to any version prior to 10.15 (e.g. 10.14) makes the application display correctly again. Confirmed not working: 10.15 [joni@linuxjoni04 bin]$ wine --version wine-10.15 (Staging) Confirmed working: [joni@linuxjoni04 bin]$ wine --version wine-10.14 (Staging) DAZ Studio, which is another wine application I have installed, does not experience this issue and renders correctly. To reproduce this issue you can quickly install roon via the script here: https://github.com/RoPieee/roon-on-wine After installing and opening the program you will immediately see the blank white window as seen in the screenshot. (alternatively you can get the exe file here and manually install it, but you need a few dependencies so the above script is way easier https://download.roonlabs.net/builds/RoonInstaller64.exe ) My system: Operating System: Arch Linux KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 24 × 13th Gen Intel® Core™ i7-13700K Memory: 64 GiB of RAM (62.5 GiB usable) Graphics Processor: NVIDIA GeForce RTX 3090 Ti -- 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 6254] riched32: Various Programms need EM_FORMATRANGE (Installer infinite loop from richtext error / wordpad: Printed Page is only white / Also affected: Half-Life, Endnote X5 Demo, ZMud, MukClient )
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=6254 --- Comment #94 from Alban Browaeys <prahal(a)yahoo.com> --- (In reply to James McKenzie from comment #71) > This bug has not been forgotten, but AJ wanted this function implemented in > a different way that is correct. First EM_DISPLAYBAND must be implemented > and then EM_FORMATRANGE. This is being investigated. Hi James. Are there more details about what AJ envisioned that you could share so as not to get lost? Or is implementing EM_DISPLAYBAND first, then EM_FORMATRANGE, all there is to it? (In reply to James McKenzie from comment #67) > Also, I have been instructed by AJ to let this lie for a little while and come > back to it. The code is NOT correct to fix the problem. > Mr. Smith has a .plan to implement a lot of the functionality within Richedit. Do you know if these plans have been abandoned since? -- 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 52959] New: Some games are rendered in square instead fullscreen
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=52959 Bug ID: 52959 Summary: Some games are rendered in square instead fullscreen Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: slawek(a)lach.art.pl Distribution: --- Some games (like Empire Earth: Gold, Commandos: Behind Enemy Lines) do not render property. It renders only in top-left square (full game frame). Rest of screen is black. -- 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 15

[Bug 58706] New: Blood Fresh Supply / Doom 64 (KEX engine games) fail to start when OpenGl API is selected (EGL backend)
by WineHQ Bugzilla 28 Sep '25

28 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58706 Bug ID: 58706 Summary: Blood Fresh Supply / Doom 64 (KEX engine games) fail to start when OpenGl API is selected (EGL backend) Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Distribution: --- Those games using the Kex Engine that support the Opengl renderer API fail to start when the new experimental EGL opengl backend is used. Such games are: Blood - Fresh Supply Doom 64 System Shock: Enhanced Edition The error message that is shown on start: kexPlatformApp::InitVideo: Failed to create window (No matching GL pixel format available). Other available renderers in those games (Vulkan and D3d11) work properly with the new EGL backend. wine-10.15-28-g7d26649f637 NVIDIA 580.82.09 X.Org X Server 1.21.1.18 -- 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 58731] New: Using newer versions of dgVoodoo2 to play older games fail to initialize.
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58731 Bug ID: 58731 Summary: Using newer versions of dgVoodoo2 to play older games fail to initialize. Product: Wine-staging Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nosferatu.arucard.1983(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- This is a year old bug around the Steam and later Lutris gaming community when notice the dgVoodoo2 wrapper after version 2.80 fail to work on Wine, either Proton or Proton-GE or any forks. Since Proton always uses DXVK for Direc3D 11 rendering (the dgVoodoo2 output), it was common to combine dgVoodoo2 with DXVK to wrap old DirectX and 3dfx Glide code to Direct3D 11, leaving DXVK to translate to Vulkan. As the time goes around, Dege was wary the fact that the last version of this own creation is now 2.86.2 at the time of writing and Lutris never update beyond 2.80 or a modded version called 2.8.2 After some testing and a rare game called Montezuma's Return which have a 3dfx version, I discovery that using dgVoodoo2 over Wine's vanilla DirectX 11 implementation also had the same problems like Proton or Wine-GE (modded versions) with DXVK. This old Glide game works with the lastest dgVoodoo2 without problems, while DirectDraw games like Omikron or Carmageddon TDR2000 fail to work using the lastest dgVoodoo2, but older versions worked fine. But the latter games had GPU diagnose tools and a pattern was found. If the dgVoodoo2 wrapper works, then the virtual dgVoodoo DirectX wrapper appears on devices list. If not, it displays the Wine's safe mode software renderer (DirectDraw HAL). Forcing playing the game, makes them crash or running at slowest speeds. After all testing, the issue happens either using DXVK or Wine's DirectX implementation, meaning that the problem should be found on Wine's code. Computers with Mesa drivers at certain games could start dgVoodoo2 2.86.2 on games like Omikron, which means that this open-source drivers code had an unintended workaround to force dgVoodoo2 to work, but this is rare and not always work. The test with Montezuma Return shows that the emulation code from Glide to DirectX works on Wine, along the DirectDraw emulation that work on certain cases. However the real issue is the initialization routine (that was changed) caused this huge regression, and it is not be handled by Wine. -- 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 58740] New: Alt keys not recognized on macOS
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58740 Bug ID: 58740 Summary: Alt keys not recognized on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com the Alt keys are not recognized on macOS. There is no input registered with either Alt key. The Mac Cmd (https://en.wikipedia.org/wiki/Command_key) keys instead register as Alt Using KeyboardStateView (Windows keyboard on-screen viewer utility): the left Cmd key registers as both: * Left MENU key (key code 164) * ALT key (key code 18) the right Cmd key registers as both: * Right MENU key (key code 165) * ALT key (key code 18) KeyboardStateView v1.00 homepage: https://www.nirsoft.net/utils/keyboard_state_view.html download: https://www.nirsoft.net/utils/keyboardstateview.zip sha256: b8ea99128e5ec854f3ce2596177687538f8d2b802943f35a223795d9452a0cd5 my system: macOS 11 tested with: Wine-stable 9.0, 10.0, Wine-devel 10.14 -- 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 58729] New: various bugs in Jedi Knight - Dark Forces II Demo (macOS)
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58729 Bug ID: 58729 Summary: various bugs in Jedi Knight - Dark Forces II Demo (macOS) Product: Wine Version: 10.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com This is a new bug report following my previous bug report (bug# 58156). In the previous bug report, the game Jedi Knight - Dark Forces II Demo could not launch at all on macOS, with the following error: > "err:module:loader_init "smackw32.DLL" failed to initialize, aborting" As of Wine-devel 10.14, this game is now playabale again but only with workaround and caveats. (comments cross-posted as well in bug# 58156) my system: macOS 11 game demo download page (choose Download this File > Agree > Jedi Knight Demo.zip): https://community.pcgamingwiki.com/files/file/1308-jedi-knight-dark-forces-… sha256: 7bc013918cf79879a086a10c27306f2f3511852726f4b4a9fec09668ed221d18 ---- To play the game, you have to launch the JEDI.EXE launcher app (not the JKDEMO.EXE game app) and click "Play Jedi Knight Demo"... After clicking "Play Jedi Knight Demo": 1. the game app will be launched to an all-black fullscreen and tries to change the screen resolution 2. the game app will minimize itself to the macOS Dock after 1 to 3 seconds 3. the same error pop-up as in my first post will show up: > Unable to start the Jedi Knight Demo game program. Try running JK.EXE where you installed the Demo directly. Also make sure you have the latest DirectX drivers installed on your system. Clicking the minimized game app from the macOS Dock (grayscale Jedi icon) will return the game app to fullscreen, with an all-black fullscreen and the intro video music playing in the background. Pressing Esc will skip the all-black intro video and correctly load the main menu and the game is playable! Press the equals key to increase the game viewport to fill the screen. ### NOTES: 1. if you choose "Cutscenes" from the main menu and press OK to play the Splash movie (intro movie), it will now play correctly 2. if you switch out of (Cmd-Tab) and return to the game from: * the all-black intro video (before pressing Esc to skip): the game correclty returns to the all-black intro video * the main menu: the main menu will now be all black, but the sounds still play when clicking your mouse and pressing Esc * the correctly-playing intro video from the Cutscenes menu: the game returns to an all-black intro video, but if you skip it (Esc), the main menu will display correctly * gameplay: the game viewport will be all the way off-screen to the top of the screen, meaning only the bottom 20% of the game can be seen (press the equals key to increase the in-game viewport). If you press Esc the pause menu still appears correctly * the pause menu, activated for the first time from gameplay: the game returns to an all-black pause menu, and pressing Esc returns the game viewport being off-screen to the top as before * the pause menu, activated for a second time from gameplay: the pause menu correctly reappears, but after returning to gameplay, the game viewport is still off to the top of the screen 3. if you close all macOS Terminal windows (which normally exits all wine processes), the game app will still be running, but the error pop-up will be killed. The game can be exited by force-quitting the wine processes in macOS Activity Monitor or Force Quit dialog I also bisected this with Wine-devel 10.12 and 10.13, and they both give the same error as in my first post: > "smackw32.DLL" failed to initialize, aborting so this was fixed in Wine-devel 10.14 I am using the official WineHQ/Gcenx binary from Homebrew/GitHub: https://formulae.brew.sh/cask/wine@devel https://github.com/Gcenx/macOS_Wine_builds/releases/download/10.14/wine-dev… -- 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 8

[Bug 58727] New: foobar2000 crash
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58727 Bug ID: 58727 Summary: foobar2000 crash Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: anezaki.yasuhiro(a)gmail.com Distribution: --- Created attachment 79336 --> http://bugs.winehq.org/attachment.cgi?id=79336 foobar2000 crash reports foobar2000 crash -- 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 58739] New: Game (Geometry Dash) crashed in wine 10.0
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58739 Bug ID: 58739 Summary: Game (Geometry Dash) crashed in wine 10.0 Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chinatty0326(a)outlook.com Distribution: --- Created attachment 79365 --> http://bugs.winehq.org/attachment.cgi?id=79365 backtrace I met this bug the instant I run Geometry Dash in wine 10.0(precompiled) The backtrace was shown before the game window popped up. But in wine 6.0 and wine 10.14 it is OK to run. Anyone can help? -- 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 58723] New: [Bisected] Windows Steam client in FreeBSD Wine fails to display a window.
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

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 1

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