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

[Bug 59044] New: lldb.exe: After breakpoint got hit and next character is entered, cursor jumps a few lines upwards
by WineHQ Bugzilla Nov. 26, 2025

Nov. 26, 2025

http://bugs.winehq.org/show_bug.cgi?id=59044 Bug ID: 59044 Summary: lldb.exe: After breakpoint got hit and next character is entered, cursor jumps a few lines upwards Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)list.winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 79811 --> http://bugs.winehq.org/attachment.cgi?id=79811 steps to reproduce, and a workaround-patch I tried using lldb.exe from the llvm-mingw-nightly package. It kind of works, can attach to process, create breakpoints, stops at breakpoints, shows source. But one thing I noticed is when hitting a breakpoint and when entering the first character of the next command, the cursor jumps a few lines upwards. By that the output of the next command gets mixed into the previous output. This happens in both, plain kde-plasma konsole and wineconsole. >From my debugging attempts it looks like in update_read_output the edit_line's home_y got not updated by lldb.exe printing some lines. Attached file contains my steps to reproduce it with a debian trixie and with winehq packages. At the end there is a workaround I found working well for my purposes. I selected the component programs, because it looks to be about conhost.exe. -- 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 59040] New: acdsee-photo-studio-ultimate-2025-win-de crashes after Start
by WineHQ Bugzilla Nov. 26, 2025

Nov. 26, 2025

http://bugs.winehq.org/show_bug.cgi?id=59040 Bug ID: 59040 Summary: acdsee-photo-studio-ultimate-2025-win-de crashes after Start 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: m(a)ck-m.de Distribution: --- Created attachment 79806 --> http://bugs.winehq.org/attachment.cgi?id=79806 log Program-window starts, then it crashs (ist auf Betriebsfehler gestoßen und wird jetzt geschlossen) ... Sorry, cant speak/write english good ... -- 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 57838] New: it just wont load the app
by WineHQ Bugzilla Nov. 26, 2025

Nov. 26, 2025

https://bugs.winehq.org/show_bug.cgi?id=57838 Bug ID: 57838 Summary: it just wont load the app Product: Wine Version: unspecified Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sifato6092(a)owlny.com Created attachment 78053 --> https://bugs.winehq.org/attachment.cgi?id=78053 backtrace it just wont load the app i useing -- 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 54352] New: Performance tanks when looking at occluded part of the level
by WineHQ Bugzilla Nov. 25, 2025

Nov. 25, 2025

https://bugs.winehq.org/show_bug.cgi?id=54352 Bug ID: 54352 Summary: Performance tanks when looking at occluded part of the level Product: Wine Version: 8.0-rc4 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: mirh(a)protonmail.ch https://github.com/doitsujin/dxvk/issues/1845 This is basically the equivalent of the missed optimization I had already reported to dxvk (except wined3d had like half the framerate to begin with). With the native nvidia d3d9 driver, you barely can spot a difference in the Mass Effect comm room between looking at the emptiest wall in human history, or the closed door behind that gives access to the rest of the ship. With wined3d, I go from like 220fps to ~70. Btw there's an apitrace in the thread above, if it can help. -- 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 53819] New: some versions of Unity engine need GetWindowTheme implemented to properly display crash dialog
by WineHQ Bugzilla Nov. 25, 2025

Nov. 25, 2025

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 59033] New: OpenGL applications fail to start under EGL backend
by WineHQ Bugzilla Nov. 24, 2025

Nov. 24, 2025

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 Nov. 24, 2025

Nov. 24, 2025

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 Nov. 24, 2025

Nov. 24, 2025

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 Nov. 24, 2025

Nov. 24, 2025

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 Nov. 23, 2025

Nov. 23, 2025

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