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

[Bug 57927] New: Sony Vegas 13 no longer starts
by WineHQ Bugzilla 19 Dec '25

19 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57927 Bug ID: 57927 Summary: Sony Vegas 13 no longer starts Product: Wine Version: 10.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- Starting from 9e9e894a76582063119f4a9004e8f3a346ad97e8 in 10.0-rc1, Sony Vegas 13 freezes the moment the splash screen appears and doesn't show any loading progress. Additionally, although this is an issue that I couldn't manage to bisect due to how inconsistent it is, is that ever since Wine 9.22, the moment it hits the stage of "Initializing external monitoring..." during loading, Vegas may freeze Wine, causing me to have to SIGKILL every process manually. It may provide an assertion of the following: "Fatal glibc error: pthread_mutex_lock.c:460 (__pthread_mutex_lock_full): assertion failed: robust || (oldval & FUTEX_OWNER_DIED) == 0" Unfortunately, I don't think I can provide good reproduction instructions as Sony Vegas 13 is paid software, although I think the installer may have a trial. -- 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 4

[Bug 58414] New: winedbg from winehq packages in Fedora 42 crashes during attaching to process.
by WineHQ Bugzilla 19 Dec '25

19 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58414 Bug ID: 58414 Summary: winedbg from winehq packages in Fedora 42 crashes during attaching to process. Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 78829 --> http://bugs.winehq.org/attachment.cgi?id=78829 fedora-42-winehq-devel-10.10-windbg-attach-crash.txt While investigating bug #58335 I found me getting a crash from winedbg when I tried to attach to some process like winemine.exe. In function dwarf2_parse_compilation_unit it looks like comp_dir.u.string is allowed to contain NULL because of the assignment in line 3090: 3090 comp_dir.u.string = NULL; Unfortunately a few lines later this comp_dir.u.string is given to function source_build_path: 3100 tmp = source_build_path(comp_dir.u.string, name.u.string); But therefore function source_build_path does an unconditional strlen(NULL), which causes a SIGSEGV: 62 unsigned bsz = strlen(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.

2 6

[Bug 59071] New: Roblox Studio flickering when resizing docked child windows on winex11 and winevulkan driver
by WineHQ Bugzilla 18 Dec '25

18 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59071 Bug ID: 59071 Summary: Roblox Studio flickering when resizing docked child windows on winex11 and winevulkan driver Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: winevulkan Assignee: wine-bugs(a)list.winehq.org Reporter: eff3ctsb0t(a)gmail.com Distribution: --- Created attachment 79856 --> http://bugs.winehq.org/attachment.cgi?id=79856 Wine debugging log when using Studio's native Vulkan renderer When resizing one of the docked child windows inside of Roblox Studio with its renderer set to Vulkan (or using DXVK with the default) and while using the X11 driver, the contents of the parent window appear to flicker rapidly. This only occurs under this combination and does not happen under WineD3D/OpenGL or winewayland. Steps to reproduce: 1. Create an account on roblox.com. 2. Download the installer for Roblox Studio. 3. Create a desktop entry named "Roblox_Studio.desktop" with the following contents. Replace <user> with the name of your user. [Desktop] Name=Roblox Studio (modified) Exec=env "WINEPREFIX=/home/<user>/.wine" wine "C:\\\\users\\\\<user>\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Roblox\\\\Roblox Studio.lnk" %u Type=Application StartupNotify=true Icon=2C11_RobloxStudioBeta.0 StartupWMClass=robloxstudiobeta.exe MimeType=x-scheme-handler/roblox-studio-auth 4. Run the installer through Wine. This should also launch Roblox Studio itself once the installation is complete. If not, run the RobloxStudioBeta.exe executable that is located inside the Wineprefix. 5. Upon launching Roblox Studio, you will be greeted by an error prompting you to login via your browser. Follow its instructions. 6. Once you reached the place templates selection, click on the "File" menu on the top left, then on "Studio Settings" and then on "Rendering" in the newly spawned window, where you should change the "Graphics Mode" from "Automatic" to "Vulkan" (or just leave it as the default and copy the DXVK DLLs into the Wineprefix). After that, relaunch Studio. 7. Load one of the place templates, then try resizing one of the docked child windows (the "Explorer" window for instance). System Information: OS: Arch Linux x86_64 Kernel: Linux 6.17.9-arch1-1 Display Server: Wayland (Niri) GPU: AMD Radeon RX 6650 XT [Discrete] Driver: Mesa 25.2.7-1 -- 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 9

[Bug 58686] New: wine crashes on usb mouse plug or unplug
by WineHQ Bugzilla 18 Dec '25

18 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58686 Bug ID: 58686 Summary: wine crashes on usb mouse plug or unplug Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: wine(a)mi.org.ru Distribution: --- when a usb mouse (and possibly other HID devices, but not keyboard though) is connected or disconnected from pc, all apps' windows opened in wine instantly crash with XI_BadDevice (invalid Device parameter) (Major opcode: 131 (XInputExtension) minor opcode: 3 (X_OpenDevice)). I tested this both on ryzen laptop with gentoo (wine-staging v10.8) and intel laptop with arch (wine 10.13). I will test previous versions later and maybe even will be able to track down the specific commit. -- 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 59113] New: Total War Shogun 2 DX9 mode crashes on init after a d3d call reports an err message.
by WineHQ Bugzilla 18 Dec '25

18 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59113 Bug ID: 59113 Summary: Total War Shogun 2 DX9 mode crashes on init after a d3d call reports an err message. Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Created attachment 79926 --> http://bugs.winehq.org/attachment.cgi?id=79926 64bit Console log from Haswell system with debugstr enabled. In 11.0-rc1 (Used the winehq wine-devel deb package), Total War Shogun 2 (D3D 9 mode) crashes on init with the last messages being err messages from wined3d_texture_load_location and wined3d_texture_invalidate_location. The crash happens in both 32bit and 64bit wine prefixes on all of the systems I've tried it on, one with proprietary nVidia drivers and one with an Intel iGPU. (An old Haswell board.) Logs from a clean 64bit wine prefix on the Haswell machine attached. (Ignore the injector exe in the log. That's for getting the game's log files moved into a user specific folder instead of the game's install dir. Which did work just fine before this crash started happening.) -- 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 59027] New: "Rebased" NTSync is broken: massive performance regression
by WineHQ Bugzilla 18 Dec '25

18 Dec '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.

2 9

[Bug 58087] New: No internet connection in apps
by WineHQ Bugzilla 18 Dec '25

18 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58087 Bug ID: 58087 Summary: No internet connection in apps Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kvradio(a)seznam.cz Distribution: --- In Wine 10.5 and also in Wine-staging 10.5 the internet connection in the application (Swisslog in a dx or LOTW cluster) is without internet connection stopped working. Wine 10.4 without problem. -- 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 3

[Bug 59132] Battle.net Launcher (CrGpuMain) hangs in wine-10.20
by WineHQ Bugzilla 17 Dec '25

17 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59132 --- Comment #12 from Dmytro Bagrii <dimich.dmb(a)gmail.com> --- (In reply to Rémi Bernon from comment #11) > I believe https://gitlab.winehq.org/wine/wine/-/merge_requests/9785 should > fix this. I applied commits from this merge request to wine-11.0-rc2 but the issue still exists: login screen is not properly rendered/updated. However, now after single `killall CrGpuMain` it started to work. -- 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 59132] Battle.net Launcher (CrGpuMain) hangs in wine-10.20
by WineHQ Bugzilla 17 Dec '25

17 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59132 --- Comment #9 from Dmytro Bagrii <dimich.dmb(a)gmail.com> --- With wine-11.0-rc2 main application screen seems work fine, if you are already logged in and login is saved. However, after logout (or with clean wine dir or whatever reason for authentication on Battle.net) login screen is shown partially (https://bugs.winehq.org/attachment.cgi?id=79975) No input fields renderend. Moving cursor over black area of the window causes this message repeated in output: 047c:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters 0022E718. After first `killall CrGpuMain` input field is shown but no input possible (https://bugs.winehq.org/attachment.cgi?id=79976) Key presses are ignored. After second `killall CrGpuMain` input works and login succeeds. Looks like the same issue as with wine-10.20 on main app screen but now on another window. -- 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 57839] New: Black rects appear briefly during window drawing
by WineHQ Bugzilla 16 Dec '25

16 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57839 Bug ID: 57839 Summary: Black rects appear briefly during window drawing Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: msuhoruki(a)gmail.com Distribution: --- I've noticed Wine 9.x started producing a visual artifact when opening dialogs, navigating menus, bringing windows to the foreground. The effect appears like a black area, displayed very briefly just before the actual content is drawn. I think this has started somewhere with 9.x and I don't see this black flash effect in Wine 8.0. It seems every time there is some activity on the window area the affected region is "blanked" out momentarily before the GUI is drawn. Using Wine 10.1 on Xorg with amdgpu and Trinity desktop. Xfce 4.12 shows same problem. Is there some redraw frequency I can tweak to fix this? The effect sounds minor but gets really jarring fast. -- 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