wine-bugs

wine-bugs@winehq.org

1 participants
159450 discussions

[Bug 59001] New: Compiling Wine with -march=znver4 prevents a crash with Deus Ex: Revision [Galaxy Audio]
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59001 Bug ID: 59001 Summary: Compiling Wine with -march=znver4 prevents a crash with Deus Ex: Revision [Galaxy Audio] 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: shtetldik(a)gmail.com Distribution: --- Created attachment 79730 --> http://bugs.winehq.org/attachment.cgi?id=79730 Crash error I found a slightly weird bug. When running Deus Ex: Revision mod using regular WineHQ build (for Debian testing), it crashes during audio initialization [Galaxy Audio]. See attached screenshot. But when I compile Wine myself using this set up with explicit CPU architecture set to znver4: export CXXFLAGS="-march=znver4" export CFLAGS="$CXXFLAGS" export CROSSCFLAGS="$CXXFLAGS" It doesn't crash. My CPU is AMD Ryzen 9 7950X (Zen 4). I don't see anything clear in the log output. What can the issue be? And do you have any suggestions how to get more diagnostic for this? Build environment: gcc: 15.2.0 gcc-mingw-w64: 15.2.0 -- 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 58990] New: wine/tools/install-sh: No such file or directory
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58990 Bug ID: 58990 Summary: wine/tools/install-sh: No such file or directory 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: euloanty(a)live.com Distribution: --- make: /home/cqwrteur/toolchains_build/wine/tools/install-sh: No such file or directory /bin/sh: line 1: /home/cqwrteur/toolchains_build/wine/tools/install-sh: No such file or directory /bin/sh: line 1: /home/cqwrteur/toolchains_build/wine/tools/install-sh: No such file or directory make: *** [Makefile:1891: dlls/activeds.tlb/install-lib] Error 127 make: *** Waiting for unfinished jobs.... make: *** [Makefile:1627: dlls/acledit/install-lib] Error 127 make: *** [Makefile:1828: dlls/aclui/install-lib] Error 127 wine install failure -- 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 58992] New: Launching Need for Speed Underground 2 with a full path breaks KDE X11
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58992 Bug ID: 58992 Summary: Launching Need for Speed Underground 2 with a full path breaks KDE X11 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- I launched the game the same way I launched MW here: https://bugs.winehq.org/show_bug.cgi?id=58797#add_comment Most Wanted creates a window and hangs, you can still close it. Underground 2 on the other hand does something so that the screen goes permanently black. Rebooting the PC does not help. Still searching for a solution. Of course, this is caused by an application bug, but it doesn't leave windows unusable. I think this has to be fixed as soon as possible, as this is a pretty serious issue. (Using the system on wayland now. Maybe it affects wayland too, but don't want to check for now or at least until I find a fix for the x11 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 2

[Bug 58991] New: Launching Need for Speed Underground 2 with a full path breaks KDE X11
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58991 Bug ID: 58991 Summary: Launching Need for Speed Underground 2 with a full path breaks KDE X11 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- I launched the game the same way I launched MW here: https://bugs.winehq.org/show_bug.cgi?id=58797#add_comment Most Wanted creates a window and hangs, you can still close it. Underground 2 on the other hand does something so that the screen goes permanently black. Rebooting the PC does not help. Still searching for a solution. Of course, this is caused by an application bug, but it doesn't leave windows unusable. I think this has to be fixed as soon as possible, as this is a pretty serious issue. (Using the system on wayland now. Maybe it affects wayland too, but don't want to check for now or at least until I find a fix for the x11 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 1

[Bug 58797] New: Need for Speed Most Wanted (2005) crashes if launched with a path with spaces
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58797 Bug ID: 58797 Summary: Need for Speed Most Wanted (2005) crashes if launched with a path with spaces 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: user.pecheniok(a)gmail.com Distribution: --- The path to the game contains the part "EA GAMES/Need for Speed Most Wanted/speed.exe". If I'm launching the game with a path as an argument(wine '~/Downloads/EA GAMES/Need for Speed Most Wanted/speed.exe'), it crashes with wine: Unhandled page fault on read access to 01DF0004 at address 0065AA27(or 2c, it differs) (thread 0144), starting debugger... but it works if I'm in the same folder and just use the exe name. This bug is, from what I observed, app-specific. Other apps I tried that have spaces in their paths do not crash because of that. -- 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 58854] New: HDD health
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58854 Bug ID: 58854 Summary: HDD health 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: lars_martin4(a)hotmail.com Distribution: --- Created attachment 79519 --> http://bugs.winehq.org/attachment.cgi?id=79519 error message. https://hdd-health.software.informer.com/4.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 6

[Bug 59002] New: Videos exported by DJI Studio have corrupted colors
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59002 Bug ID: 59002 Summary: Videos exported by DJI Studio have corrupted colors Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: spam(a)graph-ix.net Distribution: --- Created attachment 79731 --> http://bugs.winehq.org/attachment.cgi?id=79731 Correct video frame from start of exported video Steps to reproduce: * Install DJI Studio for Windows from https://www.dji.com/de/downloads/softwares/dji-studio * Launch the application * Create a new project * Load any MP4 video file with H264 or H265 video stream into the timeline (it doesn't have to be a video from a DJI device) * Optionally cut the video down to a few seconds length to make testing faster * Export the video with any encoding/export settings Actual result: * Color information of exported video is corrupted after a few video frames (typically starting on 4th frame), with all colors either green or pink. Expected result: * Color information does not get corrupted at all Attached are two different frame screenshots from a video stream, one of the first frames that are okay and one later frame that is corrupted. -- 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 58967] New: ConPTY: Child process inherits parent's std handles instead of connecting to the pseudoconsole
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58967 Bug ID: 58967 Summary: ConPTY: Child process inherits parent's std handles instead of connecting to the pseudoconsole Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: unxed(a)mail.ru Distribution: --- Created attachment 79673 --> http://bugs.winehq.org/attachment.cgi?id=79673 conpty_ping_test.c Observed behavior: When a process is created with the PROC_THREAD_ATTRIBUTE_PSEUDOCONSOLE attribute (using the ConPTY API), it incorrectly inherits the standard input/output handles (stdin/stdout/stderr) from its parent process. What is the expected behavior: The child process's standard handles should be connected to the pseudoconsole session provided by CreatePseudoConsole. Its output should be redirected to the ConPTY output pipe, not to the parent's stdout. This is the standard behavior on Windows. Steps to reproduce: 1. Compile the attached C program (conpty_ping_test.c). This program: a. Creates a pseudoconsole using CreatePseudoConsole. b. Creates pipes for the pseudoconsole's I/O. c. Launches a child process (ping.exe) using CreateProcessW with the PROC_THREAD_ATTRIBUTE_PSEUDOCONSOLE attribute set. d. Reads from the ConPTY output pipe and prints the data to its own stdout. 2. Run the compiled program from a terminal: wine conpty_ping_test.exe > conpty_ping_test.log Observed results: The host program's read loop terminates immediately, indicating that the ConPTY output pipe was closed without any data being written to it. Then, the full output of ping.exe is printed directly to the terminal. Example output: Pseudoconsole created successfully. Process 'ping 127.0.0.1 -n 4' started with PID: 1240 --- Start of process output --- [DEBUG] Pipe closed by the child process. Exiting read loop. --- End of process output --- Waiting for the child process to exit... Pinging 127.0.0.1 [127.0.0.1] with 32 bytes of data: PING: transmit failed. General failure. PING: transmit failed. General failure. PING: transmit failed. General failure. PING: transmit failed. General failure. Ping statistics for 127.0.0.1 Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) Process finished with exit code: 0 All resources have been freed. Exiting. This demonstrates that ping.exe's stdout was inherited from the host process (conpty_ping_test.c) rather than being attached to the pseudoconsole. This issue seems to stem from how the C-runtime (CRT) of the child process (ping.exe) initializes its standard handles. On Windows, the CRT detects the ConPTY session via the ConsoleHandle in the process parameters and connects its stdio to it by opening CONIN$ and CONOUT$. In Wine, it appears the CRT initialization code for msvcrt does not correctly handle this case and falls back to inheriting the parent's file handles. This is different from Wine's own conhost/tests/tty.c test, which works because the child process explicitly calls CreateFile("CONOUT$"), bypassing the problematic CRT initialization logic. The attached test case reproduces the scenario of a standard, unmodified console application like ping.exe. This bug makes the ConPTY API unusable for its primary purpose: capturing the I/O of external console applications. -- 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 57342] New: wine 9.20 is not available for several Debian/Ubuntu distributions in the WineHQ repositories
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57342 Bug ID: 57342 Summary: wine 9.20 is not available for several Debian/Ubuntu distributions in the WineHQ repositories 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: memax(a)gmx.fr CC: dimesio(a)earthlink.net Distribution: --- Hello wine 9.20 is still not available in the WineHQ repositories for : - Ubuntu 24.04 (noble) - Ubuntu 22.04 (jammy) - Debian Testing (trixie) - Debian 12 (bookworm) However, it is available for: - Ubuntu 24.10 (oracular) - Ubuntu 20.04 (focal) - Debian 11 (bullseye) Any information on why? Thanks Regards -- 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 57304] New: so like there is a bug when i download wine it says the following packages have unmet dependencies and i tried all way but never came down the solution pleasevremove the bug
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57304 Bug ID: 57304 Summary: so like there is a bug when i download wine it says the following packages have unmet dependencies and i tried all way but never came down the solution pleasevremove the bug Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: packager Assignee: wine-bugs(a)winehq.org Reporter: mdboys3171(a)gmail.com Distribution: --- like i cant even download games please solve the following packages have unmet dependencies -- 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

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