April 2026 - Wine-Bugs - list.winehq.org

[Bug 58769] New: dgVoodoo does not work with WineD3D
by WineHQ Bugzilla April 6, 2026

April 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=58769 Bug ID: 58769 Summary: dgVoodoo does not work with WineD3D Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- When using dgVoodoo with the OpenGL backend, the game (anything on dx8 or 9 really) either never starts and just stays at a black screen; or starts, but renders a black screen; or crashes. Works with the Vulkan backend and with dxvk. The console output doesn't differ between the 2 backends, so which flags should I use to get the logs? -- 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.

3 10

[Bug 59625] New: shcore: Set/GetCurrentProcessExplicitAppUserModelID are stubs
by WineHQ Bugzilla April 6, 2026

April 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59625 Bug ID: 59625 Summary: shcore: Set/GetCurrentProcessExplicitAppUserModelID are stubs Product: Wine Version: 11.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)list.winehq.org Reporter: Robert-Gerigk(a)online.de Distribution: --- SetCurrentProcessExplicitAppUserModelID in shcore.dll returns S_OK but discards the value. GetCurrentProcessExplicitAppUserModelID always returns NULL with E_NOTIMPL. This causes .NET WPF applications that call SetCurrentProcessExplicitAppUserModelID during startup and later retrieve it via GetCurrentProcessExplicitAppUserModelID to crash with "String argument cannot be null or empty" (ArgumentException). Steps to reproduce: 1. Call SetCurrentProcessExplicitAppUserModelID(L"MyApp.Id") 2. Call GetCurrentProcessExplicitAppUserModelID(&id) 3. id is NULL instead of L"MyApp.Id" Expected: id == L"MyApp.Id", hr == S_OK Actual: id == NULL, hr == E_NOTIMPL A fix with tests is ready. -- 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 43670] New: MsPaint from Win7 does not start
by wine-bugs＠winehq.org April 6, 2026

April 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=43670 Bug ID: 43670 Summary: MsPaint from Win7 does not start Product: Wine Version: 2.16 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- First you need a 32bit copy of mspaint from a win7 machine. You'll also need "winetricks mfc42". Program fails with a messagebox: "Failed to create empty document" -- 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.

3 21

[Bug 45624] New: Anno 1404 shows black screen in DirectX 10 mode.
by wine-bugs＠winehq.org April 6, 2026

April 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=45624 Bug ID: 45624 Summary: Anno 1404 shows black screen in DirectX 10 mode. Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yurishish(a)gmail.com Distribution: --- Created attachment 62053 --> https://bugs.winehq.org/attachment.cgi?id=62053 terminal output Anno 1404 fails to display content, it shows a black screen if it is launched in DX10 mode. Game is still functional, it is possible to navigate main menu, start new game or load savestate. PC specs: OS: openSUSE Tumbleweed x86_64 (Linux 4.17.13). wine 3.13 vanilla. GPU: Nvidia GTX 660 with proprietary driver v.396.51. CPU: Intel Core i5-3570k Terminal output is attached below. -- 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.

3 6

[Bug 59593] New: d3d12_desc_mark_as_modified silently drops dirty descriptors and races with flush
by WineHQ Bugzilla April 6, 2026

April 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59593 Bug ID: 59593 Summary: d3d12_desc_mark_as_modified silently drops dirty descriptors and races with flush Product: vkd3d Version: 1.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)list.winehq.org Reporter: progamercloud2(a)gmail.com Distribution: --- Hi team, I was exploring the vkd3d descriptor management code and found what appear to be correctness issues in d3d12_desc_mark_as_modified. I wanted to bring them to your attention. Bug #1: Silent Descriptor Drops In d3d12_desc_mark_as_modified: ```c if (!vkd3d_atomic_compare_exchange_u32(&dst->next, 0, (head << 1) | 1)) return; // Descriptor dirty but not added to list ``` If the CAS fails because dst->next is already non-zero (descriptor already dirty), the function returns without adding the descriptor to the dirty list. However, the descriptor needs to be flushed. This can result in stale Vulkan descriptors and visual corruption. Bug #2: Race Between Mark and Flush During flush, d3d12_desc_flush_vk_heap_updates_locked sets dirty_list_head = UINT_MAX. Marking threads may read this value and compute: ```c vkd3d_atomic_store_u32(&dst->next, (head << 1) | 1); // head = UINT_MAX ``` This creates corrupted next pointers, leading to lost descriptors or crashes. Bug #3: Memory Leak When Bug #1 occurs, the object reference obtained via d3d12_desc_get_object_ref during the copy is never released, causing reference count leaks and gradual memory exhaustion. Hope this will be helpful... -- 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 56650] New: Report on SELinux 'execheap' Issues with wine-preloader
by WineHQ Bugzilla April 6, 2026

April 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=56650 Bug ID: 56650 Summary: Report on SELinux 'execheap' Issues with wine-preloader Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chplee(a)gmail.com Distribution: --- This report was prepared by ChatGPT. I'm sorry that my own ability is not enough to support such a large amount of code analysis, so I have to turn to ChatGPT. I'm filing this report because a lot of people are suffering from this problem. Please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=2247299 ### Report on SELinux 'execheap' Issues with `wine-preloader` #### Introduction The `wine-preloader` program is a crucial part of the Wine software, which allows Windows applications to run on Unix-like operating systems. An issue has been identified where SELinux prevents `wine-preloader` from executing code in writable memory regions, raising security alerts related to 'execheap' accesses. This report identifies potential sources of the issue in the program and provides recommendations for modifications. #### Potential Issues Identified 1. **Memory Mapping and Protection Setup**: In `wine-preloader`, memory mapping is handled with protections set that could potentially include both write and execute permissions. This is particularly evident in the function calls to `wld_mmap`, where memory protection flags are set based on the segment flags parsed from ELF headers. ```c wld_mmap((void *)(l->l_addr + c->mapstart), c->mapend - c->mapstart, c->prot, MAP_FIXED | MAP_COPY | MAP_FILE, fd, c->mapoff); ``` Here, the `c->prot` can contain combinations of `PROT_READ`, `PROT_WRITE`, and `PROT_EXEC` based on the segment's flags. 2. **Dynamic Code Generation**: Dynamic generation or modification of code could potentially occur, though not explicitly shown in the code snippets provided, it could be inferred from the overall functionality where executable code may be modified or generated on-the-fly. 3. **Modifying Memory Protection Attributes**: The use of `wld_mprotect` to change the protection attributes of memory pages could lead to states where pages are both writable and executable. ```c wld_mprotect((caddr_t) (zero & ~page_mask), page_size, c->prot|PROT_WRITE); ``` Although this snippet aims to make pages writable temporarily, if combined inappropriately with executable flags elsewhere, it could trigger SELinux policies. #### Recommendations - **Restricting Memory Permissions**: Enforce strict separations between writable and executable pages. Modify the logic that sets memory protections to ensure that no memory page is both writable and executable at the same time. This can be achieved by adjusting the ELF segment loading routines to separate code and data segments clearly. - **Use of Memory Protection Changes**: Implement a clear two-step process for handling memory that needs to be executable: - Initially, set memory to writable to modify or generate code. - Once modifications are complete, change the memory protection to executable only (removing write permissions). - **Code Audit and Testing**: Conduct a thorough audit of the places where memory permissions are set. Test under a SELinux-enforced environment to ensure that the adjustments meet security policies without hindering functionality. - **SELinux Policy Adjustments**: If `wine-preloader` inherently requires certain operations that SELinux policies restrict, consider creating custom SELinux policy modules that allow specific actions while maintaining overall security. This should be done cautiously to avoid creating unnecessary security holes. #### Conclusion Adjustments to `wine-preloader` should focus on ensuring that memory regions are either writable or executable but never both. By adhering to security best practices and possibly adjusting SELinux policies, `wine-preloader` can function effectively without triggering security violations in SELinux environments. -- 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 11

[Bug 59626] New: Stratego (1997) doesn't play videos
by WineHQ Bugzilla April 6, 2026

April 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59626 Bug ID: 59626 Summary: Stratego (1997) doesn't play videos Product: Wine Version: 11.6 Hardware: x86-64 URL: https://archive.org/details/STRATEGO OS: MacOS Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tobbi.bugs(a)googlemail.com CC: jeremielapuree(a)yahoo.fr, z.figura12(a)gmail.com Created attachment 80694 --> http://bugs.winehq.org/attachment.cgi?id=80694 normal log +++ This bug was initially created as a clone of Bug #59572 +++ Stratego now works almost fine on my setup. Unfortunately, the videos that are set to play at the beginning of the game and during a win / lose condition don't play. % ./wine --version wine-11.6 % openssl sha256 STRATEGO.iso SHA2-256(STRATEGO.iso)= e82340b5e23554618dfe406c102ca2a793b34e49723e921e5cc6a5911a9867e1 I'm trying to install Stratego from here: https://archive.org/details/STRATEGO Steps to reproduce: 1. Download the ISO and mount it on your system. 2. Change the configuration options of Wine to map E: to the path where the ISO image was mounted, as well as the Operating System to Windows XP (or Windows 98 - shouldn't matter) 3. Install Stratego by running the SETUP.EXE file with wine. 4. Start Stratego by running the Stratego.exe in C:/Program Files (x86)/Hasbro Interactive/Stratego/Stratego.exe Expected Result: Stratego videos play Actual result: Stratego videos get skipped silently. I can see this in the normal log, not sure if it's related: ``` 0154:err:quartz:autoplug Failed to create filter for L"MPEG-I Stream Splitter", hr 0x80040154. 0168:err:ole:com_get_class_object class {272bfbfb-50d0-4078-b600-1e959c301337} not registered 0168:err:ole:com_get_class_object no class object {272bfbfb-50d0-4078-b600-1e959c301337} could be created for context 0x1 0168:fixme:ole:CoCreateInstanceEx no instance created for interface {00000000-0000-0000-c000-000000000046} of class {1b544c20-fd0b-11ce-8c63-00aa0044b51e}, hr 0x80040154. 0154:err:quartz:autoplug Failed to create filter for L"AVI Splitter", hr 0x80040154. ``` -- 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 59247] New: Hikvision WebComponents: window flickering on WoW64
by WineHQ Bugzilla April 6, 2026

April 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59247 Bug ID: 59247 Summary: Hikvision WebComponents: window flickering on WoW64 Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: felipecassiors(a)gmail.com Distribution: --- Created attachment 80160 --> http://bugs.winehq.org/attachment.cgi?id=80160 Screencapture showing the window flickering on Wine WoW64 It's hard to describe the issue, but here's my attempt: The whole window flickers when interacting with a browser loaded with Hikvision WebComponents. In my case, I have Wine with Firefox 31.7.0esr (https://ftp.mozilla.org/pub/firefox/releases/31.7.0esr/win32/en-US/Firefox%…) and Hikvision WebComponents installed for my old NVR. Unfortunately this is hard to reproduce by other people, since you need access to some Hikvision NVR that uses such WebComponents. I'm using Debian 13 Trixie, and when using regular winehq-staging, everything works smooth. However, when using any Wine version with WoW64, this issue happens. I have been trying ever since Wine 10.18, but decided to report it now that WoW64 is considered stable. I already tried a clean prefix, but the issue can be reproduced just fine. To install Wine WoW64 in Debian Trixie, I used Ubuntu 25.10 APT sources. However, the exact same issue happens when using the Wine builds from https://github.com/Kron4ek/Wine-Builds (and also I can confirm the issue does NOT happen when using that same build without WoW64). -- 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 54897] New: Font size and style in the title bars of windows have been changed
by WineHQ Bugzilla April 6, 2026

April 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=54897 Bug ID: 54897 Summary: Font size and style in the title bars of windows have been changed Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: zzhang(a)codeweavers.com Distribution: --- Created attachment 74398 --> https://bugs.winehq.org/attachment.cgi?id=74398 example Since 81976e5c3f4773d0035e729b27c7e274a6b9c5d1. Is this was expected to be as it now? Either way, font used values from 'CaptionFont', but it doesn't look bold? -- 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 1

[Bug 54840] New: Stack overflow in setup of "Sunday... That One Day", a 16-bit children's religious educational game
by WineHQ Bugzilla April 6, 2026

April 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=54840 Bug ID: 54840 Summary: Stack overflow in setup of "Sunday... That One Day", a 16-bit children's religious educational game Product: Wine Version: 8.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 74343 --> https://bugs.winehq.org/attachment.cgi?id=74343 Terminal output The crash happens when running SETUP.EXE. The game can be started directly from the CD by running SUNDAY.EXE, but even so it can't get past the title screen. $ sha256sum 'Andrea and Alexander - Sunday... that One Day.iso' ac9b745e9aad776b5c05bf3488955c33de2a8d97e0561718f31149af425256de -- 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 14