wine-bugs

wine-bugs@winehq.org

1 participants
159448 discussions

[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 25 Nov '25

25 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 59040] New: acdsee-photo-studio-ultimate-2025-win-de crashes after Start
by WineHQ Bugzilla 25 Nov '25

25 Nov '25

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 1

[Bug 59039] New: mountmgr.sys thread-stalls and prevents apps opening if prefix/dosdevices is readonly
by WineHQ Bugzilla 25 Nov '25

25 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 59027] New: "Rebased" NTSync is broken: massive performance regression
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59027 Bug ID: 59027 Summary: "Rebased" NTSync is broken: massive performance regression Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: virtuousfox(a)gmail.com Distribution: --- Last time I had good performance in wine it was wine-staging-1.10 with the original NTSync patch (MR 7226). But after it was "rebased" in smaller chunks and officially adopted, it as if performance is even worse than before it existed (possibly due to losing esync too). Is it still not fully merged or something, being broken in half-state? This is evident in the biggest offender I've found: https://bugs.winehq.org/show_bug.cgi?id=54693 - Freedom Planet 2 (and its demo) is back to 20 fps (it should have no problem to get 200 even with CPU-only rendering, like vulkan:llvmpipe). I also see that in Dishonored 2 fps is often stuck at also around 20-40 (previously: 50-75) while GPU is underloaded at 50-75% and 12-core CPU - <10%. At least it's not eating up 70% of all CPU cores, like it did before (or was it only esync's thing?). But /dev/ntsync is with 666 permissions and I don't see any obvious errors and warnings. Perhaps, it's silently ignored at all or there is other massive regression. Tested recently with dxvk+app-emulation/vkd3d-proton using DXVK_HUD="devinfo,fps,frametimes,submissions,drawcalls,pipelines,memory,gpuload,api,scale=1.2" but wine's native rendering with mesa's overlay should show the same, last time I've checked. Mesa overlay can be used via: VK_INSTANCE_LAYERS="VK_LAYER_MESA_overlay" VK_LOADER_LAYERS_ENABLE+=",VK_LAYER_MESA_overlay" VK_LAYER_MESA_OVERLAY_CONFIG="fps_sampling_period=80,width=480,position=top-left,submit,draw,pipeline_graphics,vert_invocations,geom_invocations,clip_invocations,frag_invocations,tess_eval_invocations,compute_invocations" If everything work well, either your fps will be capped at maximum or you should see either CPU/GPU compute load or RAM/VRAM usage at near-100%, being a bottleneck. Otherwise, system is underutilized due to bad timing of something. It this timing is particularly bad. -- 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 59017] New: Synchronization barrier cannot be entered multiple times
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59017 Bug ID: 59017 Summary: Synchronization barrier cannot be entered multiple times Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: m101010a(a)gmail.com Distribution: --- Created attachment 79756 --> http://bugs.winehq.org/attachment.cgi?id=79756 Sample program from The Old New Thing When running the sample program at https://devblogs.microsoft.com/oldnewthing/20151123-00/?p=92161 (also attached as sample.c), the second call to EnterSynchronizationBarrier does not work properly. Instead of returning false and blocking for the first 3 threads and then returning true for the last thread, it returns true and does not block all 4 times, causing the program to print "Locking the door" 4 times instead of only once, and causing the threads to not synchronize between printing "Leaving the room" and "Saying good-bye and going home". -- 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 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@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@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 58911] New: doaxvv(DMM) occasionally crashes (WMV playback bug)
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58911 Bug ID: 58911 Summary: doaxvv(DMM) occasionally crashes (WMV playback bug) Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: axis6404(a)proton.me Distribution: --- Created attachment 79591 --> http://bugs.winehq.org/attachment.cgi?id=79591 backtrace.txt DOAXVV crashed when I pulled the gacha. I'm attaching the backtrace.txt file. The crash occurred at https://github.com/wine-mirror/wine/blame/1e998672cff00f8ff7628aaf9cda60263…. Crashes do not occur in Wine 10.17. Crashes occur starting from Wine 10.18. -- 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 6

[Bug 55915] New: Shader Compiler Issues
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=55915 Bug ID: 55915 Summary: Shader Compiler Issues Product: Wine Version: 8.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 75465 --> https://bugs.winehq.org/attachment.cgi?id=75465 Shader Compiler Errors Found When attempting to play StarCraft II using a custom map (StarCraft Mass Recall latest version to be precise), I noticed the attached in the log when starting. Nothing on either side of this trace seemed out of the ordinary. As a side note (don't know if it's related but I'll note it anyway), Map 5 of Loomings ("Extermination") does seem to have the same graphics crash previously reported when I build a Machine Shop off the Factory or try to attack the first base. -- 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 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs