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

[Bug 27641] New: an editor should use the indic font when indic typing is being done
by wine-bugs＠winehq.org April 7, 2026

April 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=27641 Summary: an editor should use the indic font when indic typing is being done Product: Wine Version: 1.3.23 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usp10 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fast.rizwaan(a)gmail.com Created an attachment (id=35341) --> (http://bugs.winehq.org/attachment.cgi?id=35341) the hindi characters are shown as boxes When typing hindi in wine apps, only boxes are shown, it would be nice if wine could 'use' automatically the language related font (available fonts) and font substitution from ~/.fonts.conf, at least mangal or arial unicode ms or their substituion font should be used. It is better than empty boxes. :) likewise, some indic language fonts only have part of latin characters like numbers and symbols but not ABCDEFGHIJKLMNOPQRSTUVWXYZ characters, wine should try to use default font for latin if there are not glyphs avaialble for a language. Thanks. Please see the video and attachment hindi_font_boxes.rtf http://www.youtube.com/watch?v=uMtwEHp6gvw -- 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 7

[Bug 15458] New: The "Add Languages" Dialog is empty in inetcpl.cpl (IMultiLanguage)
by wine-bugs＠winehq.org April 7, 2026

April 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=15458 Summary: The "Add Languages" Dialog is empty in inetcpl.cpl (IMultiLanguage) Product: Wine Version: 1.1.5 Platform: PC URL: http://www.mirrorservice.org/sites/browsers.evolt.org/br owsers/ie/32bit/standalone/ie55sp2_nt.zip OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: -unknown AssignedTo: aric(a)codeweavers.com ReportedBy: wine.dev(a)web.de CC: wine-bugs(a)winehq.org Created an attachment (id=16350) --> (http://bugs.winehq.org/attachment.cgi?id=16350) +mlang,+ole 1. Download ie5.5 from browsers.evolt.org ( I used http://www.mirrorservice.org/sites/browsers.evolt.org/browsers/ie/32bit/sta…) 2. unzip 3. Apply this Patch for "URLRegSubQueryA" to avoid a crash: http://www.winehq.org/pipermail/wine-patches/2008-September/061943.html 4. wine control INETCPL.CPL 5. Press "Languages": Listbox is empty (bug 15457) 6. Press "Add": Listbox in the new Dialog is empty (works with native mlang.dll 275c23e2-3747-11d0-9fea-00aa003f8646 is IMultiLanguage) (Assign to Aric, as requested) -- By by ... Detlef -- 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 5

[Bug 46959] New: Notepad ++ crashes on startup
by wine-bugs＠winehq.org April 7, 2026

April 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=46959 Bug ID: 46959 Summary: Notepad ++ crashes on startup Product: Wine Version: 4.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: internet(a)ivohuisjes.nl Distribution: --- I have been running and upgrading wine from version 3.16 all the way to 4.2.x while using notepad ++ (under wine) without a problem, but ever since I upgraded to 4.3 or 4.5, notepad++ crashes on startup with a stack overflow and "fixme:heap:HeapSetInformation" My system: Linux 64 bit (arch based) Kernel 4.19 (LTS) To reproduce: - Install wine 4.2 or older - Install notepad++ - (Optional) start notepad++ (success!) - Upgrade to wine 4.5 - Start notepad++ -- 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 54315] New: The program described as per bug report failed to run
by WineHQ Bugzilla April 7, 2026

April 7, 2026

https://bugs.winehq.org/show_bug.cgi?id=54315 Bug ID: 54315 Summary: The program described as per bug report failed to run Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: giamas956(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- Created attachment 73877 --> https://bugs.winehq.org/attachment.cgi?id=73877 unable to run Gihosoft\Gihosoft RePicvid\RePicvid.exe as bug report above Unable to launch the program Gihosoft RePicvid as reported -- 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 5

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