- Wine-bugs - list.winehq.org

[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 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

[Bug 58820] New: Can’t upgrade wine after ubuntu update - name collision with the i386 version and amd64 version
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58820 Bug ID: 58820 Summary: Can’t upgrade wine after ubuntu update - name collision with the i386 version and amd64 version Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: levanchelidze(a)gmail.com Distribution: --- I’m tried to update wine to latest 10.17 so i removed the wine source and the added Questing source. (Reading database ... 213418 files and directories currently installed.) Preparing to unpack .../wine-devel_10.17~questing-1_amd64.deb ... Unpacking wine-devel (10.17~questing-1) ... dpkg: error processing archive /var/cache/apt/archives/wine-devel_10.17~questing-1_amd64.deb (--unpack): trying to overwrite '/opt/wine-devel/lib/wine/i386-windows/acledit.dll', which is also in package wine-deve l-i386:i386 (10.16~plucky-1) dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wine-devel_10.17~questing-1_amd64.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) This is the error i get and levan(a)moon:~$ sudo apt upgrade You might want to run 'apt --fix-broken install' to correct these. Unsatisfied dependencies: winehq-devel : Depends: wine-devel (= 10.17~questing-1) but it is not installed Error: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). levan(a)moon:~$ sudo apt --fix-broken install Correcting dependencies... Done Installing dependencies: wine-devel Summary: Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0 4 not fully installed or removed. Download size: 0 B / 236 MB Space needed: 1,518 MB / 170 GB available Continue? [Y/n] y (Reading database ... 213418 files and directories currently installed.) Preparing to unpack .../wine-devel_10.17~questing-1_amd64.deb ... Unpacking wine-devel (10.17~questing-1) ... dpkg: error processing archive /var/cache/apt/archives/wine-devel_10.17~questing-1_amd64.deb (--unpack): trying to overwrite '/opt/wine-devel/lib/wine/i386-windows/acledit.dll', which is also in package wine-deve l-i386:i386 (10.16~plucky-1) dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wine-devel_10.17~questing-1_amd64.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) -- 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 9

[Bug 58886] New: Uninstallable on Debian Trixie 13.1, depends on unavailable libpcre2-8-0:i386 version
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58886 Bug ID: 58886 Summary: Uninstallable on Debian Trixie 13.1, depends on unavailable libpcre2-8-0:i386 version Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: johannes(a)rohr.org CC: dimesio(a)earthlink.net Distribution: --- root(a)upernavik:~# LANG=C apt install winehq-stable Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: winehq-stable : Depends: wine-stable (= 10.0.0.0~trixie-1) Error: Unable to correct problems, you have held broken packages. Error: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. winehq-stable:amd64=10.0.0.0~trixie-1 is selected for install 2. winehq-stable:amd64=10.0.0.0~trixie-1 Depends wine-stable (= 10.0.0.0~trixie-1) but none of the choices are installable: - wine-stable:amd64=10.0.0.0~trixie-1 Depends wine-stable-i386 (= 10.0.0.0~trixie-1) but none of the choices are installable: - wine-stable-i386:i386=10.0.0.0~trixie-1 Depends libglib2.0-0t64:i386 (>= 2.80.0) but none of the choices are installable: - libglib2.0-0t64:i386 Depends libpcre2-8-0:i386 (>= 10.22) but none of the choices are installable: - libpcre2-8-0:i386 is not selected for install because: 1. grep:amd64 is selected for install 2. grep:amd64 PreDepends libpcre2-8-0 (>= 10.32) 3. libpcre2-8-0:amd64 is available in version 10.46-1~deb13u1 4. libpcre2-8-0:i386 Breaks libpcre2-8-0 (!= 10.45-1) - wine-stable:i386=10.0.0.0~trixie-1 Depends wine-stable-i386:i386 (= 10.0.0.0~trixie-1) but none of the choices are installable: - wine-stable-i386:i386=10.0.0.0~trixie-1 is not selected for install as above root(a)upernavik:~# -- 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 58406] New: libvkd3d-doc: An error occurs during installation: "Field "section" is not allowed in section Format"
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58406 Bug ID: 58406 Summary: libvkd3d-doc: An error occurs during installation: "Field "section" is not allowed in section Format" Product: vkd3d Version: 1.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: mywine(a)schiermeier-it.de Distribution: --- Hello! There is an error while the package is installed: This is the error: --- Trigger für dochelp (0.1.8+b8) werden verarbeitet ... E: /usr/share/doc-base/libvkd3d-doc.vkd3d: Field "section" is not allowed in section Format --- -- 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

[Bug 58999] New: The Whispering Valley (GOG) freezes with out of memory error with vulkan rendere
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58999 Bug ID: 58999 Summary: The Whispering Valley (GOG) freezes with out of memory error with vulkan rendere Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Created attachment 79722 --> http://bugs.winehq.org/attachment.cgi?id=79722 console log The game work fine with the GL renderer and DXVK. Wine 10.19 Nvidia GTX 3070 drive 535.54.03. Ubuntu 22.04 -- 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 58995] New: musl is not working properly with latest versions
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58995 Bug ID: 58995 Summary: musl is not working properly with latest versions 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: --- It does not even copy the right files to bin, and system32 and windows are not properly filled either -- 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 58997] New: Page fault crash in experimental WOW64 mode on ARM64 when running D3D8 game with DXVK
by WineHQ Bugzilla 16 Nov '25

16 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58997 Bug ID: 58997 Summary: Page fault crash in experimental WOW64 mode on ARM64 when running D3D8 game with DXVK Product: Wine-staging Version: 10.18 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: zayedferozkazi(a)proton.me CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79719 --> http://bugs.winehq.org/attachment.cgi?id=79719 the log file when wine wrapgame.exe Environment: - Hardware: Apple M1 Mac Mini (ARM64/aarch64) - OS: Fedora Asahi Remix 43 (Linux kernel 6.16.8-400.asahi.fc43.aarch64+16k) - Wine: wine-staging 10.18 - DXVK: 2.7.1 - Application: Shark Attack (Direct3D 8 game via wrapgame.exe) Issue: Game consistently crashes with page fault at address 7FFFFFF0 immediately after Direct3D device initialization when running in Wine's experimental WOW64 mode on ARM64. Steps to reproduce: 1. Install wine-staging 10.18 on ARM64 system 2. Install DXVK 2.7.1 (winetricks dxvk) 3. Run any Direct3D 8 application Expected behavior: Game should run in WOW64 mode Actual behavior: Unhandled page fault on write access to 7FFFFFF0 Notes: - DXVK successfully initializes and reports "D3D9 interface is now operating in D3D8 compatibility mode" - Device creation completes successfully - Crash occurs right after swapchain creation - Error is consistent across multiple launch attempts - Wine correctly identifies this as experimental WOW64 mode Attachment contains full crash log with debugger output. -- 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