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

[Bug 56470] New: Wined3d has windows always sitting in background
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56470 Bug ID: 56470 Summary: Wined3d has windows always sitting in background Product: Wine Version: 9.5 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: mirh(a)protonmail.ch So.. as I always do every few month, I try to see if wined3d finally holds a candle for helping with games in Windows. This time I was surprised by a constant 30FPS lock, despite the fact both my game of choice settings and the external tools profiles for its executable didn't have one (indeed if I removed wine's dlls, native d3d9 could easily get almost 10 times as much framerate) Long story short, after some time banging my head I figured this was happening because "Background Application Max Frame Rate" was enabled in the nvidia control panel. Problem being of course that a foreground fullscreen window definitively isn't supposed to be affected by that. This does not happen with normal opengl games (even after I renamed their exe, just to be extra safe about whitelisting and whatnot) so it seems something on your side of things. -- 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 44021] New: LiveMaker engine fails to find font despite overrides set up
by wine-bugs＠winehq.org 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=44021 Bug ID: 44021 Summary: LiveMaker engine fails to find font despite overrides set up Product: Wine Version: 2.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Going by https://github.com/xupefei/Locale-Emulator/issues/80, doesn't access the font in question (MS Gothic) directly, yet despite its overrides being set up correctly (HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes: both English and Japanese names), the engine crashes unless that font is actually present in drive_c/windows/Fonts. It might be that this can't be done as font matching/replacing takes place at much later stage, yet would be nice if someone could verify one way or the other. Perhaps those names should simply hardcoded to be returned in Japanese locale, regardless of the fonts being actually present ? Cause before Windows 10 (which has a different Japanese font), they couldn't not be there after a proper Japanese Windows install. -- 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 2

[Bug 53819] New: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=53819 Bug ID: 53819 Summary: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- So, I've stumbled upon a Unity engine game that crashes every now and then due to what seems to be virtual mapping space exhaustion. Not sure about the crash itself - it's more likely to be graphics related that winegstreamer, but that's just a guess. Anyway, once the crash happens, console is flooded by: 03b0:err:module:DelayLoadFailureHook failed to delay load uxtheme.dll.GetWindowTheme wine: Call from 7B0123C6 to unimplemented function uxtheme.dll.GetWindowTheme, aborting 03b0:err:seh:KiUserCallbackDispatcher ignoring exception and the Unity crash dialog doesn't display properly. -- 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 59042] New: winevdm is incompatible with Rosetta 2
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59042 Bug ID: 59042 Summary: winevdm is incompatible with Rosetta 2 Product: Wine Version: 10.19 Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: dos Assignee: wine-bugs(a)list.winehq.org Reporter: computers57(a)hotmail.com Attempting to run a win16 game on Apple Silicon via Rosetta results in a failure for Rosetta 2: rosetta error: LDT 0xf33f0488323f not supported This has been tested against chip's challenge and SkiFree. I think this is a problem with Rosetta 2 that can't be resolved except via emulating a 16-bit Intel CPU as Rosetta 2 lacks the needed 16-bit call emulation. One possible solution would be to do what MS does for running 32-bit Intel software under 64-bit ARM CPUs, but work would need to be done on the Mac side for that to happen. -- 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 59033] New: OpenGL applications fail to start under EGL backend
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59033 Bug ID: 59033 Summary: OpenGL applications fail to start under EGL backend Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)list.winehq.org Reporter: sin-ack(a)protonmail.com Distribution: --- Tested with Touhou Fuujinroku (Mountain of Faith), running via THCRAP and with vpatch. Also tested with Bejeweled 3. Games run fine when the EGL backend is disabled via UseEGL=0 in the registry, but OpenGL initialization completely fails when enabled (the default since 10.17). Curiously, the error happens to be different every time; sometimes context creation fails completely and the entire process hangs until wineserver -k, sometimes the X11 error is shown and the application exits immediately, sometimes getting pixel formats fails but the process can resume. I hacked on the code a bit to get some more information, and I get an NT_ACCESS_VIOLATION from the first UNIX_CALL `get_pixel_format` on the PE side. Attached are logs with WINEDEBUG=trace+opengl. System information: OS: Gentoo Linux amd64 Kernel version: 6.17.7-gentoo Wine version: wine-10.19 Wine backend: X11 Mesa version: 25.3.0 Graphics card: AMD Radeon RX 6700 XT Desktop environment: Hyprland 0.51.1 + xwayland 24.1.9 -- 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 59039] New: mountmgr.sys thread-stalls and prevents apps opening if prefix/dosdevices is readonly
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59039 Bug ID: 59039 Summary: mountmgr.sys thread-stalls and prevents apps opening if prefix/dosdevices is readonly Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)list.winehq.org Reporter: triffid.hunter(a)gmail.com Distribution: --- $ chmod -w ~/.wine/dosdevices $ wine /path/to/exe … 0058:err:sync:RtlpWaitForCriticalSection section 00006FFFFE69B040 "/var/tmp/portage/app-emulation/wine-vanilla-10.18/work/wine-10.18/dlls/mountmgr.sys/device.c: device_section" wait timed out in thread 0058, blocked by 0060, retrying (60 sec) 0058:err:sync:RtlpWaitForCriticalSection section 00006FFFFE69B040 "/var/tmp/portage/app-emulation/wine-vanilla-10.18/work/wine-10.18/dlls/mountmgr.sys/device.c: device_section" wait timed out in thread 0058, blocked by 0060, retrying (60 sec) … ^C $ wineserver -k $ chmod u+w ~/.wine/dosdevices $ wine /path/to/exe «everything works normally» Curiously this doesn't affect built-in wine apps like notepad straight away, but does cause it to deadlock if I file→open. I want dosdevices to be readonly because wine fills it with tons of random cruft I don't want there (way more serial ports than I actually have, a bevy of ephemeral removable drives and/or network mounts) every time it starts up. Making dosdevices readonly worked fine in older versions, 8.x or 9.x series perhaps, although https://forum.winehq.org/viewtopic.php?t=27922 reports a similar issue in 2016 If this is considered not-a-bug, how can I manually manage the drives available within wine instead of having a bunch of pseudorandom nonsense auto-filled every time I start wine? -- 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 59019] New: Unable to Start UFile 2024 using WINE and Winetracks
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59019 Bug ID: 59019 Summary: Unable to Start UFile 2024 using WINE and Winetracks 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: paul_flynn(a)gmx.com Distribution: --- Created attachment 79758 --> http://bugs.winehq.org/attachment.cgi?id=79758 Back trace from trying to launch the UFile 2024 Windows application. I have installed the latest WINE and Winetracks. I am trying to get UFile2024 to run in this environment. I have the application desktop icon to launch, however, the initial screen flashes then disappears. I have attached the back trace file. -- 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 59032] New: extreme pinball for ms dos 5 or higher
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59032 Bug ID: 59032 Summary: extreme pinball for ms dos 5 or higher 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: lars_martin4(a)hotmail.com Distribution: --- https://archive.org/details/msdos_Extreme_Pinball_1995 larsmartinhambro(a)Pc2:/media/larsmartinhambro/Extreme Pinball$ wine extreme.exe 002c:fixme:winediag:loader_init wine-staging 10.19 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0070:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented! 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 00ac:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys" 00ac:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys" 00ac:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys" 00a8:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 0024:fixme:winediag:loader_init wine-staging 10.19 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. winevdm: D:\extreme.exe is a DOS application, you need to install DOSBox. larsmartinhambro(a)Pc2:/media/larsmartinhambro/Extreme Pinball$ 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0174:fixme:winediag:loader_init wine-staging 10.19 is a testing version containing experimental patches. 0174:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. -- 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 56447] New: PlayOnline Viewer: The "splash screen" is blank/grey without its image.
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56447 Bug ID: 56447 Summary: PlayOnline Viewer: The "splash screen" is blank/grey without its image. Product: Wine Version: 9.4 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Distribution: Gentoo This is a very old one, but as far as I can tell, not reported until now (aside from some side-mentions). PlayOnline Viewer, which is used to launch Final Fantasy XI Online, has a blank/grey window for its "splash screen". It has been working in Wine Staging for some time. Not sure if related, but comparing the logging between runs, each of these show up twice with Vanilla but only once with Staging: err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x1, ret 0x4. err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x2, ret 0x4. -- 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 59035] New: Wrong default printer with lpoptions set
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59035 Bug ID: 59035 Summary: Wrong default printer with lpoptions set Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: dpat(a)syn-net.org Distribution: --- Created attachment 79791 --> http://bugs.winehq.org/attachment.cgi?id=79791 Wine Log with lpoptions set (wrong default printer) I am running Linux Mint Debian Edition 6 (LMDE6 based on Debian/bookworm) with a Cinnamon DE and have the following printers configured: user(a)LMDE6 ~ % groups user users % lpstat -v device for Brother_MFC_9332CDW: implicitclass://Brother_MFC_9332CDW/ device for HP_OfficeJet_Pro_7740_series_5940AF: implicitclass://HP_OfficeJet_Pro_7740_series_5940AF/ device for Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511: implicitclass://Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511/ A server default printer is set: % lpstat -d system default destination: Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511 And I have the following `~/.cups/lpoptions` file: % cat .cups/lpoptions Dest Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511 When calling notepad with Wine, the wrong default printer is shown (preselected) (in my case the Brother_MFC_9332CDW) in the print options (File: Print...): % WINEDEBUG=+winspool,+tid,+pid,+process,+commdlg wine notepad 2>&1 | tee wine-lpoptions-set.log If I delete the `~/.cups/lpoptions` file, the correct default printer is shown (preselected) (Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511): % WINEDEBUG=+winspool,+tid,+pid,+process,+commdlg wine notepad 2>&1 | tee wine-lpoptions-unset.log I could not figure out who, what or why did create and set the option in `~/.cups/lpoptions`, but I know the Samsung printer was replaced and CUPS automatically detected the new printer and switched the default printer (to the Brother) at some time before. I assume the user did try to change the default printer withing the GUI, but maybe ended up changing the lpoptions file? I later changed the system default printer (from Brother to Samsung) and noticed this problem with Wine. I am not a CUPS expert, but as far I could research ``Dest Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511`` itself looks like an invalid or at least incomplete option. Nevertheless, this should not have an effect on an application in Wine. I am on Wine version wine-9.19 and can not upgrade to a new version as this version is the latest version I was able to run Access Runtime 2010 (where I actually need the correct default printer to be set). P.s. I only can add one attachment (wine-lpoptions-set.log), if you need wine-lpoptions-unset.log for comparison, I can upload it separately as well. The most striking change I could identify is: 0118:011c:trace:winspool:SetDefaultPrinterW (L"Brother_MFC_9332CDW") vs 0118:011c:trace:winspool:SetDefaultPrinterW (L"Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511") I can not see why the other printer was chosen. -- 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