wine-bugs July 2025

wine-bugs@winehq.org

1 participants
555 discussions

[Bug 57811] New: wikis/Building-Wine contains broken/obsolete link
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=57811 Bug ID: 57811 Summary: wikis/Building-Wine contains broken/obsolete link Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- As per instruction on the 404 website "If you followed a link from a WineHQ.org page and reached this page in error, please report it to the WineHQ.org Bugzilla.": The link on the Wine Wiki https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html is broken resulting in 404. -- 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 58451] New: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer when implemented'
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58451 Bug ID: 58451 Summary: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer when implemented' Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: winehq-bugs_serge_180716(a)gautherie.fr Distribution: --- wine-1.1.18 https://gitlab.winehq.org/wine/wine/-/commit/5f6ae94ad0163341c2cd79a89f29b2… added { /* FIXME: should use CreateTimerQueueTimer when implemented */ thread = CreateThread(NULL, 0, rpcrt4_http_timer_thread, timer_data, 0, NULL); } although CreateTimerQueueTimer() was already implemented, by wine-1.1.2 https://gitlab.winehq.org/wine/wine/-/commit/d343f2baf76413eb690cbc44a0d56e… { NTSTATUS status = RtlCreateTimer(phNewTimer, TimerQueue, Callback, Parameter, DueTime, Period, Flags); } Check and fix that FIXME. -- 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 58450] New: Total Annihilation (GOG, demo) – Wayland black screen on startup.
by WineHQ Bugzilla 04 Jul '25

04 Jul '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 2

[Bug 52999] New: Redout fails to detect visual c++ runtimes
by WineHQ Bugzilla 04 Jul '25

04 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=52999 Bug ID: 52999 Summary: Redout fails to detect visual c++ runtimes Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 72366 --> https://bugs.winehq.org/attachment.cgi?id=72366 Logfile When i try to run Redout, it says you need to install the c++ runtime. The log does not indicate anything going wrong: 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.8 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0118:fixme:imm:ImeSetActiveContext (0000000000CDB7F0, 1): stub 0118:fixme:imm:ImmReleaseContext (000000000001006C, 0000000000CDB7F0): stub 007c:fixme:imm:ImeSetActiveContext (0000000000356C10, 0): stub 007c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000356C10): stub 0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 0000000000B9FD70 -- 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 56761] New: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=56761 Bug ID: 56761 Summary: So when I install Blizzard.net setup exe its crashes and gives me the backtrace log Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adampigeons(a)gmail.com Distribution: --- Created attachment 76555 --> https://bugs.winehq.org/attachment.cgi?id=76555 the log of the error i launch battlenet exe setup then the window becomes unusable then i get the backtrace log -- 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 55979] New: Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

https://bugs.winehq.org/show_bug.cgi?id=55979 Bug ID: 55979 Summary: Blizzard Battle.net Launcher: New Version Released On 11/30/2023 Hangs During Installation Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crashdance(a)charter.net Distribution: --- Created attachment 75569 --> https://bugs.winehq.org/attachment.cgi?id=75569 Terminal output when running the Battle.net client installer in a clean Wine prefix When attempting to install Battle.net in a clean 64-bit prefix on a clean install of Linux Mint 21.2 with all needed dependencies, I get the attached terminal output and the progress hangs at 45%. Also, I know the maintainers of Bugzilla encourage reporting only one problem per bug. That being said, the exact same time this started happening, my existing Wine prefix for Battle.net (and my Battle.net games) caused thread crashes when opening Battle.net after installing yesterday's update. The update was installed from within the Battle.net client by clicking the green icon to install the update. Prior to this update released yesterday on November 30, 2023, Battle.net and the games were running flawlessly. Because I can only add a single attachment, the Pastebin links below will give more detail on the related issue of thread crashes described above: Existing prefix terminal output when the thread crash occurs: https://pastebin.com/4UwxTsEP Here is my system information: https://pastebin.com/v3MVemgg Was able to save a crash report for the thread crash issue: https://pastebin.com/mYX68NrX -- 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 28

[Bug 58446] New: Shift + Click to draw straight line using tablet pen not working in CLIP STUDIO PAINT version 2
by WineHQ Bugzilla 03 Jul '25

03 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58446 Bug ID: 58446 Summary: Shift + Click to draw straight line using tablet pen not working in CLIP STUDIO PAINT version 2 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: kas23997(a)gmail.com Distribution: --- I am using a Wacom Intuous PT S2, for reference. I've tried to toggle mouse mode in CSP's settings, but neither works. The pen will just draw separate dots instead of making a straight line. It works if using a mouse, however. Nothing appeared in the Terminal after the wine command, so let me know if there's any other info I should provide. -- 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 58440] New: Dance eJay 6 and dance eJay 7 crash with advapi32 error
by WineHQ Bugzilla 02 Jul '25

02 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58440 Bug ID: 58440 Summary: Dance eJay 6 and dance eJay 7 crash with advapi32 error Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: rave002(a)o2.pl Distribution: --- Created attachment 78891 --> http://bugs.winehq.org/attachment.cgi?id=78891 Dance ejay 6 Reloaded crash log Both applications used to run fine on the older versions of wine. I'm attaching the logs for Dance eJay 6.0, but the one for Dance 7 is pretty much the same. Tried winetricks to maybe install a "proper" version of advapi32, however winetricks doesn't provide it. I will try to add Dance eJay 7.0 crash log in a following comment if I'm able to. -- 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 58358] New: Dungeons & Dragons Online: No suitable graphics device was found. [122]
by WineHQ Bugzilla 02 Jul '25

02 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58358 Bug ID: 58358 Summary: Dungeons & Dragons Online: No suitable graphics device was found. [122] Product: Wine Version: 10.9 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ccooksey(a)mindspring.com Created attachment 78747 --> http://bugs.winehq.org/attachment.cgi?id=78747 Logs showing the video driver failures in Wine 10.0_1 and higher On macOS Sequoia, using Apple Silicon on a MacBook Pro, running Dungeons and Dragons online and entering the game world on any version of Wine *after* 10.0 will stop with a message: "No suitable graphics device was found. Are you running through a remote session or a VM? If not, please check your video hardware capabilities. [122]" The game terminates and cannot be played. Note that the Game Launcher works fine. It is the game client that fails -the bit that uses DX9 and above. If the original Wine 10.0 is installed (prior to 10.0_1), it works fine. To recreate: Working case (Wine 10.0): - Register a free account at: https://www.ddo.com/register - Download the game installer here: https://www.ddo.com/download - Install wine 10.0, (not wine-stable - see instructions below). - Install the game to a standard wine prefix. - Run "C:/Program Files (x86)/StandingStoneGames/Dungeons & Dragons Online/DNDLauncher.exe" to enter the launcher. Use your free account. - Enter the world "Orien". - Observe that the character creation screen in the game client appears. Non working case (Wine 10.0_1 and higher): - Install any higher version of Wine, i.e. wine-stable (10.0_2), wine@staging or wine@devel. - Install the game to a standard wine prefix (if you didn't already). - Run "C:/Program Files (x86)/StandingStoneGames/Dungeons & Dragons Online/DNDLauncher.exe" to enter the launcher. Use your free account. - Enter the world "Orien". - The game client will stop with error [122] as it tries to connect to DX9. My observation: 10.0 uses: [mvk-info] MoltenVK version 1.2.10, supporting Vulkan version 1.2.290. 10.0_1 and higher all use: [mvk-info] MoltenVK version 1.3.0, supporting Vulkan version 1.3.313. There are literally no code changes in Wine from 10.0 to 10.0_1. But these graphics libs did change and now there appears to be no video driver. I have been using brew to install. Here is a speedy way to get the original Wine 10.0 installed on a machine: brew uninstall wine-stable # or wine@staging or wine@devel, as needed curl -o wine-stable.rb https://raw.githubusercontent.com/Homebrew/homebrew-cask/3b6f8acd9c1f8aad56… sed -i '' 's/wine64/msidb/g' wine-stable.rb # Implements an important change from the 10.0_1 brew cask. brew install --no-quarantine wine-stable.rb # Note the '.rb' suffix. # If you are on Apple Silicon, install Apple's x86 emulator. Ignore any errors. /usr/sbin/softwareupdate --install-rosetta --agree-to-license For the breaking case, you can just "brew install --no-quarantine [wine-stable | wine@staging | wine@devel]". No need to use older casks. Note that the current gstreamer is not compatible with wine-stable. Optionally add these commands to prevent gstreamer from being noisy and slowing things down: export GST_PLUGIN_PATH=/dev/null export GST_PLUGIN_SYSTEM_PATH=/dev/null I have attached logs from 10.0 (working) and 10.9 (not working). I used WINEDEBUG="+seh,+tid,+d3d,+vulkan,+dxvk,+d3d12". Please let me know if you need any additional info from me. Thanks, Chris. -- 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 20

[Bug 58417] New: Failure to compile: Undeclared KW_ object
by WineHQ Bugzilla 01 Jul '25

01 Jul '25

http://bugs.winehq.org/show_bug.cgi?id=58417 Bug ID: 58417 Summary: Failure to compile: Undeclared KW_ object Product: vkd3d Version: 1.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: johngodman006(a)gmail.com Distribution: --- Created attachment 78834 --> http://bugs.winehq.org/attachment.cgi?id=78834 Compilation log I am trying to compile wine in shared WoW64 mode, and ran into the attached error during compilation of the 64 bit binary. I have to imagine, given the compilation error is an undeclared identifier, that I am missing some headers. However, I'm not sure what exactly I am missing. I have packages spirv-headers-devel, vulkan-headers, and libvkd3d-devel installed at their latest versions from Fedora. For reference, I'm on Fedora 42 kernel 6.15.3. I must be making a simple mistake, right? If someone could give me a hand, I'd greatly appreciate 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 3

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