wine-bugs

wine-bugs@winehq.org

1 participants
159442 discussions

[Bug 58811] New: Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58811 Bug ID: 58811 Summary: Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive. Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 2a2cc34db71a86899b69bf3ee1da52793c342019 Distribution: Gentoo Created attachment 79466 --> http://bugs.winehq.org/attachment.cgi?id=79466 terminal After 2a2cc34db71 [1], Steam appears to launch, showing its notification area icon, but no window will appear. After a while from clicking said icon, the "Steamwebhelper is not responding" window [2] will appear, with a few different options to restart things with, of which none do any better. I believe the src\vgui2\vgui_surfacelib\Win32Font.cpp (963) : Couldn't get string length line shows up only when this problem can be seen, which could be a sort of a hint at least. Building before the mentioned commit, or reverting it, and efce37afd70 due to conflicts, on current 'git master' will make it work again. Hacking on it a bit, removing the 'wcsupr(refkey->name);' line also makes it work, though maybe that is obvious in this case, and might more or less nullify the point of the uppercasing intended. (Did not try a fresh prefix and clean install of Steam yet due to the cumbersome log-in process, but hopefully that is not necessary here.) Last tested at 'wine-10.17'. Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/2a2cc34db71a86899b69bf3ee1da52… 2. https://help.steampowered.com/en/faqs/view/6C3E-9504-CC20-AF49 -- 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 58983] New: Wow64 applications crash when initializing WinMM
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58983 Bug ID: 58983 Summary: Wow64 applications crash when initializing WinMM Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)list.winehq.org Reporter: matthewm.hinson(a)gmail.com Distribution: --- Created attachment 79705 --> http://bugs.winehq.org/attachment.cgi?id=79705 Stacktrace If a Wow64 application initializes WinMM by (for example) calling waveOutGetNumDevs(), it will crash with an access violation. The reason is that the structure "is_format_supported_params" has a different definition in mmdevapi.dll than it does in winealsa.drv: https://gitlab.winehq.org/wine/wine/-/blob/18ce7964203b486c8236f2c16a370ae2… https://gitlab.winehq.org/wine/wine/-/blob/18ce7964203b486c8236f2c16a370ae2… winealsa.drv has an extra field "fmt_out" which shifts the field "result" down by 4 bytes. As a result, winealsa ends up writing the result outside of the DLL-allocated buffer, clobbering a stack-saved register which then later causes the crash. To reproduce, simply compile the following as a 32-bit .exe: #include <windows.h> int main() { waveOutGetNumDevs(); return 0; } Then run on a 64-bit Wine prefix. -- 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 56790] New: wine binds my application to "lo" adapter
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56790 Bug ID: 56790 Summary: wine binds my application to "lo" adapter Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: contact(a)msteinbusch.nl Distribution: ArchLinux Created attachment 76596 --> https://bugs.winehq.org/attachment.cgi?id=76596 A full wine trace Issue: Farming Simulator 2022 dedicated webserver binds application to "lo" adapter Wine doesn't run my program the same way as Windows does, for some reason it binds to the "lo" adapter. I suspect the application is selecting the first interface. Sadly there is no way to override this. I included a full trace, keywords to look trough are winsock, 127.0.0.1, winsock:bind socket etc. Any help is welcome and if more info is needed let me know. Wine: 9.10-1 and < Archlinux, Kernel 6.9.3. X68_64 A VNC instance where the issue can be reproduced is available on request. A license key for Farming Simulator 2022 can be provided by me on request. The download of the game/server can be found at: https://eshop.giants-software.com/downloads.php This docker container is using nginx to get around the issue: https://github.com/wine-gameservers/arch-wine-fs22 Screenshot and logs included in 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.

1 29

[Bug 14543] New: Worms World Party crashes on attempting to run
by wine-bugs＠winehq.org 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=14543 Summary: Worms World Party crashes on attempting to run Product: Wine Version: 1.1.1 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: trivial Priority: P2 Component: quartz AssignedTo: wine-bugs(a)winehq.org ReportedBy: Rincebrain(a)gmail.com Created an attachment (id=14883) --> (http://bugs.winehq.org/attachment.cgi?id=14883) Wine 1.1.1 output log (including BT) Worms World Party crashed when I attempted to run it - WWP fullscreened and rendered a black screen atop everything else, then Wine crashed, and sat at a backtrace until I killed wineserver. Wine output, including backtrace, attached. -- 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 48

[Bug 58998] New: cmd broken, 'echo|set /p=%LOCALAPPDATA%' returns empty string
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58998 Bug ID: 58998 Summary: cmd broken, 'echo|set /p=%LOCALAPPDATA%' returns empty string Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: axet(a)me.com Distribution: --- Hello! cmd /c 'echo|set /p=%LOCALAPPDATA%' returns empty string with recent wine-staging 10.19. Last working wine 10.16. Issue get broken/resolved automatically depend on release number. Happened before, then got fixed with next release. Now it happened again with 4 releases in a row. I guess not going to be auto fixed this time. Using prebuild from winehq Debian Forky. -- 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 58973] New: Many games crash at start with new WoW64 wine-10.19 and discrete Nvidia GPU
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58973 Bug ID: 58973 Summary: Many games crash at start with new WoW64 wine-10.19 and discrete Nvidia GPU Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: memax(a)gmx.fr Distribution: --- Created attachment 79683 --> http://bugs.winehq.org/attachment.cgi?id=79683 "Syberia 2" terminal output System Information: OS: Ubuntu 24.04.3 LTS 64-bit Kernel: Linux 6.14.0-35-generic Windowing System: X11 Graphics: Discrete GPU: NVIDIA NVIDIA Driver Version: 535.274.02 Wine Version: Development version New WoW64 wine-10.19 (built by me) Description: All the 32-bit games I have tested so far crash on launch with new WoW64 wine-10.19 and discrete Nvidia GPU. Switching to the integrated Intel GPU allows to work around the problem. This bug does not affect old WoW64 (wine-10.19 from WineHQ Binary Packages). -- 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 59003] New: StarCraft: assertion failed
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59003 Bug ID: 59003 Summary: StarCraft: assertion failed Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: dimich.dmb(a)gmail.com Distribution: --- Created attachment 79733 --> http://bugs.winehq.org/attachment.cgi?id=79733 full wine output StarCraft fails to start with wine-10.19. Probable relevant error message: StarCraft.exe: ../wine/dlls/winex11.drv/xrandr.c:1573: xrandr14_set_current_mode: Assertion `sizeof(*full_mode) == sizeof(full_mode->mode) + full_mode->mode.dmDriverExtra' failed. (full log attached). The issue occures also with wine-staging-10.19. The issue doesn't occur with wine-10.18. OS: Arch Linux Xorg server version 21.1.20 xorg-xrandr 1.5.3 Nvidia driver 580.105.08 egl-x11 1.0.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 4

[Bug 57109] New: Ableton Live 12: Max for Live fails to start
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57109 Bug ID: 57109 Summary: Ableton Live 12: Max for Live fails to start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pedrodarch15b(a)gmail.com Distribution: --- Created attachment 76997 --> https://bugs.winehq.org/attachment.cgi?id=76997 wine output Ableton Live 12 (both Suite and Trial versions) won't start Max for Live. It gets stuck on "Starting Max...", and renaming the Max folder to something else (this tricks Ableton into thinking that Max is not installed) makes the program start just fine. The cause of this issue seems to be a regression in ucrtbase (Max for Live was working just fine before Wine 9.12 if I recall correctly). By installing the program multiple times I have noticed that Max does start upon launching Ableton just after installing, but not on subsequent runs. I have tested the program on a clean prefix (mostly, I did set wined3d renderer to vulkan using winetricks), using a fresh build of latest git wine, compiled locally with GCC 14 on Arch Linux. -- 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 58846] New: Geneforge 1 - Mutagen (Geneforge 2 - Infestation): black screen issue
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58846 Bug ID: 58846 Summary: Geneforge 1 - Mutagen (Geneforge 2 - Infestation): black screen issue Product: Wine Version: 10.11 Hardware: x86-64 URL: https://www.spiderwebsoftware.com/geneforge/downloadWi n.html OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 79eb50683f56e55a1ce485f3d288983ed33f1c34 Distribution: ArchLinux The last two games released in the Geneforge saga display only a black screen while running. Occasionally the game screen flashes for a fraction of a second otherwise nothing is visible on the screen. Reproduced with NVIDIA 580.95.05 binary drivers and with NVK/Zink/Mesa-25.2.5. The problem is present since commit 79eb50683f56e55a1ce485f3d288983ed33f1c34 win32u: Keep a reference to the GL drawables in the windows. With the previous commit the games work properly. wine-10.17-115-gff187dc851c 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 1

[Bug 58800] New: tlReader 10.1.0.2004 toolbar has broken rendering
by WineHQ Bugzilla 18 Nov '25

18 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58800 Bug ID: 58800 Summary: tlReader 10.1.0.2004 toolbar has broken rendering Product: Wine Version: unspecified Hardware: x86-64 URL: https://web.archive.org/web/20251013233829/https://tsh wanedje.com/builds/2004/tlReader_10.1.0.2004.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: arethusa26(a)gmail.com CC: zzhang(a)codeweavers.com Regression SHA1: 541d9be5ecda1bc0c8fce22f1318bf5d72572327 Distribution: --- Created attachment 79445 --> http://bugs.winehq.org/attachment.cgi?id=79445 Broken toolbar rendering With the latest master (wine-10.16-212-g6124fea1dde), when loading the Manx-English dictionary (available from https://tshwanedje.com/downloads/files/Manx_English_Phil_Kelly_Dec2014.zip), the toolbar at the top of the tlReader application appears to have some rendering defects. Specifically, the background color of the toolbar has a darker color, and there is a stray horizontal line that is visible and appears to intersect the tops of the toolbar icons. Additionally, hovering the cursor over the icons results in a blue box that is drawn around a hovered icon but is not cleared when the cursor leaves the icon. With wine-10.16, the rendering of the toolbar seems to be more correct. The background color apparently resembles the color on Windows 10, no stray horizontal line is visible on the toolbar, and hovering over the toolbar icons with the cursor results in a blue box being drawn around a hovered icon that is cleared when the cursor leaves the icon. These behaviors are consistent with what is seen on Windows 10. Regression testing identified commit 541d9be5ecda1bc0c8fce22f1318bf5d72572327, which implemented the final modifications needed for comctl32 separation, as the change that introduced the broken toolbar rendering. However, it's not clear if the toolbar rendering issue is a new introduced problem or if it was previously hidden and now exposed with the comctl32 separation. -- 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 10

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