September 2025 - Wine-bugs - list.winehq.org

[Bug 58592] New: Font substitution partially broken - regression
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58592 Bug ID: 58592 Summary: Font substitution partially broken - regression Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zdenek.koprivik(a)post.cz Distribution: --- While trying to replace "Tahoma" with "Noto Sans Regular" (the default Plasma desktop font), I've encountered an issue, where the font replacement does not work in some cases. Since I'm migrating from a very old system with Wine 1.6.2, I know that the font replacement used to work for the exact same binary and the same UI elements. I've set the following registry keys: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Tahoma"="Noto Sans Regular" "Segoe UI"="Noto Sans Regular" "MS Shell Dlg"="Noto Sans Regular" "MS Shell Dlg 2"="Noto Sans Regular" The issue can be reproduced by opening the file dialog in the built-in registry editor. Running the built-in registry editor I've got the main font changed to "Noto Sans Regular" as expected, but in the file open dialog for import, there is still "Tahoma". When I'm browsing for directories, the font changes to "Noto Sans Regular", but when an item is selected, the font changes back to "Tahoma". Here is a short video showing the issue: https://imgur.com/a/l0BhsB8 This is only one example of the non-working substitution. The "Tahoma" is also rendered on the buttons and almost everywhere around in the dialog. I'm using the substitution mostly for MikroTik network equipment management apps (WinBox and The Dude) to improve the readability. It is working fine when running the exact same binaries on the old PC with Wine 1.6.2, but I can't get it to work with the newest Wine. The system is KDE neon User, Plasma 6.4.4, Wine 10.12 from the WineHQ PPA. -- 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 8

[Bug 49780] New: wineconsole reports VT sequence support when it does not
by WineHQ Bugzilla 27 Sep '25

27 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=49780 Bug ID: 49780 Summary: wineconsole reports VT sequence support when it does not Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: magiblot(a)hotmail.com Distribution: --- Created attachment 68092 --> https://bugs.winehq.org/attachment.cgi?id=68092 Demo application to reproduce the issue Wineconsole does not support applications writing Virtual Terminal sequences through the Console API. That's fine. However, when enabling the console ENABLE_VIRTUAL_TERMINAL_PROCESSING mode on stdout with SetConsoleMode, no error is returned, so the application has no way to detect whether VT sequences are supported or not. This is documented in https://docs.microsoft.com/en-us/windows/console/setconsolemode. The port of Turbo Vision at https://github.com/magiblot/tvision is affected by this. When using the Console API, Turbo Vision prefers VT sequences over SetConsoleCursorPosition/SetConsoleTextAttribute for code reusability and performance. Nevertheless, it can fall back to the latter method when SetConsoleMode fails to enable either ENABLE_VIRTUAL_TERMINAL_PROCESSING or DISABLE_NEWLINE_AUTO_RETURN. Since SetConsoleMode does not return error on wineconsole, garbage is shown instead of a colorful interface. STEPS TO REPRODUCE To reproduce the issue on Turbo Vision: (A) - Using the attached 'tvdemo.exe' 1. Run the application on wineconsole. You should see a black-and-white background and escape sequences drawn on the console. 2. Press Alt+F, then D. You should see the command prompt, and the message "VT enabled" at the top, which demonstrates the issue in SetConsoleMode. (B) - Compiling from source code (requires up-to-date CMake and MSVC). 1. Insert the following code after line 63 in source/linux/win32con.cpp (https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63…) ``` if (supportsVT) cerr << "VT enabled" << endl; else cerr << "VT not enabled: " << GetLastError() << endl; ``` 2. Follow the build instructions at https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63… 3. Follow the steps in (A). EXPECTED BEHAVIOUR On Windows, support for VT sequences can be disabled by turning on the "Legacy Console" mode. If tvdemo.exe is ran in these conditions, the interface is displayed properly. If entering the command prompt by pressing Alt+F, then D, the message "VT not enabled: 87" is displayed (error 87 stands for ERROR_INVALID_PARAMETER), which is what should be shown on wineconsole as well, since it clearly does not support VT sequences. Thank you! -- 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 13

[Bug 51230] New: winecfg: Graphics tab - Per application settings don't work
by WineHQ Bugzilla 26 Sep '25

26 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=51230 Bug ID: 51230 Summary: winecfg: Graphics tab - Per application settings don't work Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jkfloris(a)dds.nl Distribution: --- "Wine can mimic different Windows versions for each application. This tab is linked to the Libraries and Graphics tabs to allow you to change system-wide or per-application settings in those tabs as well." >From this I understand that it should also be possible to also set the DPI or a virtual desktop per application. Unfortunately, this does not work. For example: winecfg Applications tab -> Add application -> "notepad.exe" (select notepad.exe) Graphics tab -> Select "Emulate a virtual desktop" (click "Apply" and "OK") wine notepad.exe Now I expect notepad to run in a virtual desktop. -- 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 19

[Bug 43747] New: Yermom demoscene demo shows only a blackscreen
by wine-bugs＠winehq.org 25 Sep '25

25 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=43747 Bug ID: 43747 Summary: Yermom demoscene demo shows only a blackscreen Product: Wine Version: 2.17 Hardware: x86 URL: http://www.pouet.net/prod.php?which=71570 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Depends on: 43638 Distribution: --- The program needs "winetricks gmdls", and currently only works with wine-staging due to bug 43638. However, the screen is completely white, only the music plays. You're advised to use "emulate a virtual desktop" if you want to test the hack, then you can quit the fullscreen with ESC. -- 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 47135] New: Onenote fails to start: Desktop Experience feature is not installed ( lacking Win32_ServerFeature class from wbemprox)
by wine-bugs＠winehq.org 24 Sep '25

24 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=47135 Bug ID: 47135 Summary: Onenote fails to start: Desktop Experience feature is not installed (lacking Win32_ServerFeature class from wbemprox) Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 64360 --> https://bugs.winehq.org/attachment.cgi?id=64360 hack to start Onenote The relaylog below *** made with ONENOTE (MSOffice 2010) shows problem apparently seems to be in wbemprox, missing Win32_ServerFeature class The attached crappy hack allowed me to start Onenote, and also Onenote from Office365 starts with it. Crappy hack is only to show where the problem is and problably contains several errors, hopefully someone can fix this in proper way (hint at Hans;)). Sidenote: reverting the hack makes Onenote from Office365 run into the bug again, but Onenote from office 2010 now continues happily to start; maybe it sets some registry key once started and the patch is not needed anymore? No idea. 008c:Call KERNEL32.lstrlenA(2e09825c "SELECT Name FROM Win32_ServerFeature") ret=2e0e8fd1 008c:Ret KERNEL32.lstrlenA() retval=00000024 ret=2e0e8fd1 008c:Call KERNEL32.MultiByteToWideChar(00000000,00000000,2e09825c "SELECT Name FROM Win32_ServerFeature",00000025,00000000,00000000) ret=2e0e8fe7 008c:Ret KERNEL32.MultiByteToWideChar() retval=00000025 ret=2e0e8fe7 008c:Call KERNEL32.MultiByteToWideChar(00000000,00000000,2e09825c "SELECT Name FROM Win32_ServerFeature",00000025,0033f9f0,00000025) ret=2e0e9085 008c:Ret KERNEL32.MultiByteToWideChar() retval=00000025 ret=2e0e9085 008c:Call oleaut32.SysAllocString(0033f9f0 L"SELECT Name FROM Win32_ServerFeature") ret=2e0e90bb . . . . 008c:Call user32.MessageBoxW(00000000,0033f6b2 L"OneNote cannot start because the Desktop Experience feature is not installed. Install it in the Windows Control Panel > Prog rams and Features > Turn Windows features on or off.",39835ba4 L"Microsoft Office",00000030) ret=39bb2183 -- 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 12

[Bug 58538] New: d2d_device_context_DrawGeometry Ignoring stroke style => No Circles, only Lines
by WineHQ Bugzilla 24 Sep '25

24 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58538 Bug ID: 58538 Summary: d2d_device_context_DrawGeometry Ignoring stroke style => No Circles, only Lines Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: d.astra(a)yopmail.com Distribution: --- Created attachment 79028 --> http://bugs.winehq.org/attachment.cgi?id=79028 WINEDEBUG=+d2d, Rainmeter 4.5.23 I'm using Rainmeter 4.5.23 with Wine 10.12-staging and everything, which should be round or a circle, is either not drawn at all or more of a hexagonal shape. Main error output in the console: 013c:fixme:d2d:d2d_geometry_sink_AddArc iface 0000000002E13CF8, arc 000000000011EC80 stub! 013c:fixme:d2d:d2d_geometry_sink_AddArc iface 0000000002E13CF8, arc 000000000011EC80 stub! 013c:fixme:d2d:d2d_path_geometry_GetWidenedBounds iface 0000000002E13BE0, stroke_width 0.00000000e+00, stroke_style 0000000000000000, transform 0000000000000000, tolerance 2.50000000e-01, bounds 000000000011EA40 stub! Further output with WINEDEBUG=+d2d as attachement -- 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 58732] New: Bel Atout: when opening a file linked with a file type, Bel Atout is not brought to top
by WineHQ Bugzilla 23 Sep '25

23 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58732 Bug ID: 58732 Summary: Bel Atout: when opening a file linked with a file type, Bel Atout is not brought to top Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vincent.brevart3526(a)outlook.fr Distribution: --- Created attachment 79348 --> http://bugs.winehq.org/attachment.cgi?id=79348 A .bel file that can be opened by Bel Atout from the file explorer In Bel Atout (card game), .bel files can be opened by a double click from the file explorer. On Ubuntu 22.04, with Wine 10.0, if Bel Atout is not yet running, opening a .bel file works fine, with Bel Atout brought to top. Now, if Bel Atout is already running, a file can be opened in the same window, without opening a new instance. It works fine on Ubuntu. But if I click on the Bel Atout window, just once, anywhere, even if it has no action, the next time I open a file by a double click, the file explorer window will be brought to top, above the Bel Atout window. This doesn't happen on Windows. As I am the programmer of Bel Atout, I tried many Windows functions like SetForegroundWindow, BringWindowToTop, SetWindowPos, SetActiveWindow, ShowWindow and so on. But no way to avoid the file explorer window to be brought to top. You can download Bel Atout (free card game) from the page: https://vincent-brevart.fr/en/lin/card-games-for-linux.html I am attaching a .bel file that you can open from the file explorer. Not very annoying, but if the .bel file is a "prepared game" with a dialog box that opens before playing the deal, the file explorer windows appears twice: the first time when the file is opened, and a second time when clicking the "Play the prepared game" button and closing the dialog box. I don't understand why. You can test the opening of the prepared games on my page: https://vincent-brevart.fr/en/pre/belote/prepared-games-belote-beginner1.ht… But it may be a problem coming from my own way of programming, sorry if it does. Thanks for your great work. Vincent -- 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 48049] New: Basemark GPU crashes when using D3D12
by WineHQ Bugzilla 22 Sep '25

22 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=48049 Bug ID: 48049 Summary: Basemark GPU crashes when using D3D12 Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no Distribution: --- Created attachment 65589 --> https://bugs.winehq.org/attachment.cgi?id=65589 Debug log of Basemark Basemark GPU - https://www.basemark.com/benchmarks/basemark-gpu/ - crashes when selecting D3D12. Vulkan and OpenGL works. Ran D3D12 test with logging: VKD3D_DEBUG=trace VKD3D_CONFIG=vk_debug VK_INSTANCE_LAYERS=VK_LAYER_LUNARG_standard_validation Let me know if there are other logging options needed. PS. The benchmark is free to download. -- 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 57975] New: screen shaders don't work in BigPEmu.exe
by WineHQ Bugzilla 22 Sep '25

22 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57975 Bug ID: 57975 Summary: screen shaders don't work in BigPEmu.exe Product: Wine Version: 10.0 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com BigPEmu is an Atari Jaguar emulator, it runs Atari Jaguar games fine under Wine Stable 10.0 on macOS 11. The problem is there is a "screen effects" feature (which are like screen shaders in RetroArch, used to emulate old CRTs, etc) which doesn't work. By default, BigPEmu uses OpenGL (BigPEmu main menu > Video > Video Plugin > BigPEmu_Video_OpenGL) but can also be changed to use D3D12 which will cause it crash at startup on macOS 11. Steps to reproduce: 1. launch BigPEmu 1.18 with the following options (also opens a console): wine ~/BigPEmu_v118/BigPEmu.exe * -conout 2. use backspace/enter to navigate backward/forward in BigPEmu, go back to the main menu, then Video > Screen Effect > choose any screen effect 3. an error message pops up: "Failed to set the selected screen effect. It may be incompatible with your hardware or video plugin. You can enable logging and check the log for more details." 4. check the console which shows this error: "[1;31mError: Graphics hardware isn't equipped to run screen effects. If this error occurs with SM5.0-compatible hardware, try updating your graphics drivers." tested with BigPEmu 1.18 for Windows x64 download link: https://www.richwhitehouse.com/jaguar/builds/BigPEmu_v118.zip SHA-256: 9863390fca342e7c6bff0d7dc7d70d181bdff92796aa8d262d91e8fc909104b2 tested on macOS 11.7.10 Intel CPU (Haswell), integrated Intel GPU (HD Graphics 5000) Wine Stable 10.0 with GStreamer 1.24.12 from homebrew -- 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 23

[Bug 58264] New: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93"
by WineHQ Bugzilla 22 Sep '25

22 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58264 Bug ID: 58264 Summary: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevu lkan/loader_thunks.c, line 93" Product: Wine Version: 10.7 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78605 --> http://bugs.winehq.org/attachment.cgi?id=78605 macOS Terminal log, wine-devel 10.8 running cpuz_x64.exe On macOS, there is a regression in multiple Windows programs since Wine-devel 10.7 (including 10.8) releases by Gcenx, with the final lines of the terminal output reading: > -[MTLHeapDescriptorInternal validateWithDevice:]:327: failed assertion `Heap Descriptor Validation > Placement heap type is not supported. > ' > 01a0:err:msvcrt:_wassert (L"!status && \"vkAllocateMemory\"",L"/Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c",93) > Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93 These programs work fine in Wine-devel 10.6 and lower tested with Wine-devel 10.7 and 10.8 binary releases from Gcenx (https://github.com/Gcenx/macOS_Wine_builds/releases) on macOS 11.7.10 tested with CPU-Z 2.15 (portable) (cpuz_x64.exe) download: https://download.cpuid.com/cpu-z/cpu-z_2.15-en.zip sha256: c8461d995d77a8fe1e8c5823403e88b04b733165cc151083b26379f1fe4b9501 -- 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 16